Private transfers
MIST verifies that a transfer is funded, authorized, and balanced without publishing the underlying payment details.
Partners can move value between private balances without exposing their full payment position on-chain.
Pilot program open
Privacy infrastructure by your rules.
MIST gives payment providers a private settlement rail where your own screening and compliance rules run inside your own pool. Funds under different policies never mix, and authorized reviewers get evidence for a specific payment without sensitive details reaching a public ledger.
- Your pool
- your screening, your rules
- ~1s
- privacy check on a phone
- <2¢
- target cost per transfer
- ZK
- privacy by mathematics
Protocol showcase
Built for protocols.
MIST is infrastructure first. Operators and integrators compose these capabilities into their own products.
Your rules, in the payment flow
Operators can add limits, approval requirements, and release conditions to transfers and withdrawals.
Your policy stays part of the transaction rather than becoming a manual review after the fact.
Compliance with controlled disclosure
A transaction can carry evidence of KYC status, jurisdiction, audit approval, or amount limits without publishing the underlying record.
Authorized reviewers can receive the evidence for a specific transaction instead of getting unrestricted access to the whole flow.
Clear asset boundaries
Each transfer accounts for one asset within one Chamber and Reserve combination.
Funds governed by different policies remain separated, making ownership and compliance responsibilities easier to define.
Built for integration
Withdrawals can carry instructions for the receiving contract, with the transaction binding those instructions before settlement.
Partners can connect private payments to their existing products without giving a relayer room to change the requested action.
Architecture
A private record, your controls, separate funds.
MIST separates the payment record from partner controls and asset custody. Chamber tracks ownership; Middleware applies business rules; Reserves hold funds under a defined policy.
Chamber
Payment record
Chamber keeps the private record of who owns what and confirms that each payment follows the protocol rules. It never holds the funds.
Middleware
Partner controls
Middleware is where a partner adds business rules such as limits, approvals, eligibility checks, and release conditions.
Reserve
Separate funds and policies
A Reserve holds the assets and applies one defined set of entry, payment, and withdrawal requirements.
When funds enter MIST, the Chamber records the private balance and a Reserve holds the assets. Internal payments update private balances without moving funds on-chain. When funds leave, the Chamber checks the payment and the Reserve sends them to the stated destination.
Each payment uses one asset and one Reserve policy. Hidemi currently supports USDC across CCTP networks. Broader cross-network movement is a separate product layer, and USDT via usdt0 is planned.
What is measured
Evidence, not adjectives.
Benchmarks and milestones that show what the system can do.
First privacy proof
Produced on Starknet in July 2024; implemented in Garaga in the weeks that followed.
~1s
Measured privacy-check generation on an iPhone; a benchmark, not a guarantee for every deployment.
~5¢
Current product cost benchmark, heading toward a <2¢ target.
Chamber + Reserve
The Chamber holds the private payment record; each Reserve holds funds under one policy. Funds under different policies never mix.
Your screening
Each partner defines the KYC, jurisdiction, approval and amount rules for their own Reserve; the payment flow enforces them without publishing the customer record.
Controlled disclosure
A reviewer can receive evidence for a specific transaction without receiving unrestricted access to the full payment flow.
Benchmarks, targets, current product scope, and planned capabilities are labeled separately so partners can tell what is available today.
Why MIST
Your screening, your own pool, disclosure you can prove.
Compliance products either impose one rulebook on everyone or hand the work to whoever builds on top. MIST gives each provider their own pool and their own rules, with evidence a reviewer can check.
| Capability | MIST | Railgun | 0xbow | Zcash | Aztec | Panther | Zama |
|---|---|---|---|---|---|---|---|
| Who sets the compliance rules | Each provider, for their own pool | Protocol (PCP screening) | Protocol (ASP screening) | Optional and uniform (viewing keys) | Builder, DIY | One licensed manager per zone | Builder, DIY |
| Who shares a pool | One pool per policy; different rules never mix | Per-chain deployment | One Ethereum pool | Global shielded pool | Per contract | Per licensed zone | No default pool |
| Screening you control | KYC, jurisdiction, approval and amount rules, set per Reserve | Fixed, protocol-level screening | Deposits screened before entry | Viewing keys for disclosure | Not provided | Defined by the zone manager | Not provided |
| Asset scope | Any tokens, one policy per Reserve | Multi-asset, per chain | Ethereum assets | ZEC | Any (build anything) | zAssets, multi-asset | Any (encrypted compute) |
| Cross-chain | Hidemi consumer app today; B2B rail on the roadmap | Separate pool per chain | Ethereum only | Its own L1 only | Ethereum L2, own chain | One chain live today | Chain-agnostic (any EVM, Solana) |
Competitor positions researched July 2026 from each protocol's public materials, and they move quickly. The MIST column describes the protocol design: each Reserve binds any number of tokens to one compliance policy. Current product scope is USDC, with cross-chain support live in the Hidemi consumer app and on the roadmap for the B2B rail.
Blog
Latest from the protocol.
Signal
In the wild.
What builders are saying about the protocol, alongside updates from the MIST team.
Congrats @shrameetweets! In addition having a cool UX it also employs very nice SNARK optimizations.
Try Hidemi: hidemi.mist.cash → Generate a private payment link → Receive funds anonymously → Spend without linking back
I haven’t met a builder yet with as innovative and workable an approach to private payments as @shrameetweets has with @_mistcash Worth checking out
Try Hidemi: hidemi.mist.cash → Generate a private payment link → Receive funds anonymously → Spend without linking back
The need for a layer of privacy in some use cases is unlocking adoption and solving the core problems of transactions that need privacy. Check out @_mistcash last release of the app and have privacy on chain! Proud to have this amazing team on our CH4 @FS_Build
Try Hidemi: hidemi.mist.cash → Generate a private payment link → Receive funds anonymously → Spend without linking back
got something that you need some crazy optimisations, call @shrameetweets
New 🔥 4.3x faster 🔥 Poseidon implementation in Cairo! Old impl: 2,017,424 gas New impl: 475,930 gas Sweet leap towards faster and cheaper ZK proofs on MIST.cash 💵
real life privacy payment on starknet via mist cash protocol, today, on mainnet. private p2p cash gud. starknet will soon be the post quantum scalable and private layer
Talking about MIST, we say we always are building the privacy payments that you can use to pay for your coffee. The vision "solidified" at @StarknetFndn @StarkWareLtd StarkConnect, when we sold coffee grounds/beans fully privately with MIST. ❤️ @CofiBlocks ❤️ @jonatanChaverri ❤️
This is proof that you can integrate privacy into your app in less than 24 hours with Mist Cash 🔥 thanks bro @shrameetweets
No better way to understand what @shrameetweets has been working on with @_mistcash that this integration with @CofiBlocks that literally happened overnight. Coffee bean producers are now safer thanks to private payments
Talking about MIST, we say we always are building the privacy payments that you can use to pay for your coffee. The vision "solidified" at @StarknetFndn @StarkWareLtd StarkConnect, when we sold coffee grounds/beans fully privately with MIST. ❤️ @CofiBlocks ❤️ @jonatanChaverri ❤️
Speaking
In the field.
Pitching the case for private money movement on stage: founder decks and demo rooms up to the Starknet main stage in Buenos Aires.
Build with MIST.
Integrate private settlement into any protocol. The docs specify the full operator and integrator path.