Introducing the Mirage Design Partnership
Picture an employer running monthly payroll in native USDC. Every employee's wallet address, exact salary, and total payroll volume are permanently public. Colleagues can compare each other's earnings. Competitors can observe vendor relationships and treasury positions. High-earning employees can become identifiable targets for crime. This is the current default behavior of every public blockchain, and it is the single biggest reason stablecoin treasuries and payments have not gone mainstream despite the underlying rails being ready.
Today we're opening applications for the Mirage Design Partnership: a nine-week engagement to build and co-publish a working end-to-end reference journey and the integrations behind it for private stablecoin payroll. Applications close May 31, 2026. The full Design Partnership Brief covers the architecture, partner roles, timeline, and terms in detail.
Why a Design Partnership, and why now
Stablecoin payroll has moved from a crypto-native experiment to a category that mainstream payroll platforms are actively adopting as their payment rail. At the same time, the regulatory picture has gotten clearer: FINMA's stablecoin guidance, MiCA's stablecoin regime, and the shifting US posture all reward compliant designs and penalize the alternative. Tornado Cash's pool-based privacy made it clear that mixing or pooling funds is not the reference architecture that stablecoin-powered FinTechs want to rely on.
Existing approaches each give up something essential. Mixers and pools co-mingle funds and carry sanctions exposure. Privacy-first L1s and L2s solve the cryptography but require migration off the chains where stablecoins and ecosystems actually live. Wrapped and synthetic privacy tokens lose the native-asset status and introduce a whole new set of trust assumptions.
We think the right answer is to keep the stablecoin native, keep the chain familiar, avoid pooling entirely, and integrate privacy into the tools businesses already use. That answer is not a single product but requires integrations into wallets and payroll platforms, a wallet screening service that doesn't negatively flag the privacy-conscious users, and legal clarity that employers and partners require at scale. None of us can ship it alone, which is why we're proposing to build it together.
What we're building together
The engagement runs a real payroll journey through a complete stack. An employer pays salaries in native USDC. The employer's wallet is screened for compliance before any funds enter Mirage. The privacy module is embedded inside the payroll platform or the wallet, depending on where the funds sit. Private transfers settle in under six seconds on faster EVM networks. Employees off-ramp to fiat through an exchange or top up their stablecoin credit card, each of which accepts a Mirage-issued receipt for source-of-funds checks.
Circle anchors the stablecoin layer. Our legal partner is producing the legal opinion under Swiss law with EU and US commentary. We're recruiting partners for the remaining roles: self-custodial wallet, payroll platform, wallet screening, off-ramp exchange, and an independent research institute to observe and co-author the report.
What each partner provides, and what we provide
Each partner contributes the piece they already ship: an API surface, an account, technical documentation, and a maximum of two hours of Q&A per week during integration. Mirage handles the integration engineering, the architecture documentation, and the drafting of the co-published report. Partners review and co-sign the result.
The timeline is nine weeks across five phases: application by May 31, letter of intent by June 5 with parallel integration through June, end-to-end testing in July with live salary runs, partner review through early August, and a joint public release at the end of August.
Why participate
The architecture for private stablecoin payroll is being defined over the next few quarters, and the teams that contribute to the definition will be named in the resulting reference. A shared legal opinion across the full stack is significantly cheaper than each partner producing one alone. And each partner exits with a real, working integration into a complete payroll flow.
If this is the kind of work you're already doing, we'd like to do it with you. The Design Partnership Brief has the full details; the application itself is a short reply to partners@mirageprivacy.com with your role interest, a technical reference, and a contact for the integration window.
Apply by May 31, 2026.