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.
MIST gives payment protocols a private way to move assets across networks. Partners can set their own transaction rules and provide evidence to authorized reviewers without putting sensitive details on a public ledger.
Protocol showcase
MIST is infrastructure first. Operators and integrators compose these capabilities into their own products.
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.
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.
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.
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.
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
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.
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.
Partner controls
Middleware is where a partner adds business rules such as limits, approvals, eligibility checks, and release conditions.
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
Benchmarks and milestones that show what the system can do.
Produced on Starknet in July 2024, via a Garaga implementation.
Measured privacy-check generation on an iPhone; a benchmark, not a guarantee for every deployment.
Current product cost benchmark, heading toward a <2¢ target.
MIST can combine payment validity and partner rules into one check for settlement, with the final proving work handled by the selected deployment model.
Current product scope is cross-network USDC over CCTP-supported networks; each payment still uses one asset and one Reserve policy.
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
Cross-network USDC, clear policy boundaries, and partner-defined compliance. MIST combines these priorities without hiding the operational trade-offs.
| Capability | MIST | Privacy pools | Privacy coins | On-chain privacy proofs | FHE |
|---|---|---|---|---|---|
| Cross-chain | |||||
| Single-asset transaction accounting | Unspecified | Unspecified | Unspecified | Unspecified | |
| Native programmable compliance | |||||
| Settlement finality | |||||
| Who can be grouped together | Shared private payments; separate policy pools | Variable | Global | Variable | Variable |
Trade-offs are real. MIST keeps each payment tied to one asset and one policy pool, while cross-network movement is handled separately. The important question for a partner is who can review what, under which policy, and at what point in the payment flow.
Blog
Signal
Independent takes on the protocol, from the people building in the space.
Speaking
The protocol is shaped in public: explaining the systems, proving the trade-offs, and building privacy infrastructure that can be examined.


Integrate private settlement into any protocol. The docs specify the full operator and integrator path.