Real Soroban measurements
Fee and CPU costs were captured at each step of the flow, giving a concrete performance baseline for confidential transfers on Soroban rather than a theoretical estimate.
A capability-led path that moves from a working confidential-transfer proof-of-concept to an audit-gated mainnet launch, delivered as an open-source public good for the Stellar ecosystem.
A functional proof-of-concept already demonstrates the complete confidential-settlement flow end to end on Stellar testnet. The sequence below is not a plan — it is a run that has been executed and measured.
An account is created and its auditor viewing key is escrowed at registration, enforced on-chain by a zero-knowledge proof so compliance visibility is a precondition, not an afterthought.
Public USDC is moved into a confidential balance, wrapping real USDC through Stellar's Asset Contract pattern with no dependency on issuer cooperation.
Value moves with the amount and both balances kept hidden on-chain, each transfer verified by a zero-knowledge proof before it settles.
The recipient decrypts the incoming amount with their own key and reconciles it against their confidential balance.
An authorized reviewer selectively decrypts that one transaction through the auditor viewing key, without exposing any unrelated activity.
The confidential balance settles back out to public USDC, closing the loop between on-chain confidentiality and the regulated fiat last mile.
Fee and CPU costs were captured at each step of the flow, giving a concrete performance baseline for confidential transfers on Soroban rather than a theoretical estimate.
The sponsored-transaction model was confirmed in practice: fee-bump and sponsored reserves cover costs so senders and recipients never need to hold or manage XLM.
The grant funds capability, not speculation. Every deliverable is released as an open-source public good that any regulated operator can inspect, reuse and extend.
The Admin (operator), Banking / Partner and Auditor / Compliance dashboards, released open source as reference control surfaces.
A Partner API with REST, webhooks and a sandbox, plus a Compliance API for screening hooks, selective-disclosure endpoints and audit-trail queries.
A client SDK and a proving service so integrators can construct valid confidential transfers without building bespoke cryptography.
A relayer that applies fee-bump and sponsored reserves so end users transact fee-free and never hold XLM — no asset gate on participation.
A published zero-knowledge cost and performance benchmark for confidential transfers on Soroban, contributed back to the ecosystem.
The roadmap advances by capability rather than by calendar. Each phase adds a layer of the system, and the final phase is unlocked only once the security gate is cleared.
Stand up the confidential-transfer layer for USDC and the foundations users touch — a testnet MVP that proves the core mechanics.
Build the regulated operating layer around the core, still on testnet, so the system behaves like production infrastructure.
Harden the system, pass the independent security gate, and only then deploy to mainnet. Mainnet is explicitly conditional on the audit outcome.
| Phase | Focus | Key capabilities | Environment |
|---|---|---|---|
| 01 | Confidential core & foundation | Confidential USDC transfers, sponsored fees, wallet access, operator console | Testnet MVP |
| 02 | Bank-grade system, dashboards & compliance | Three dashboards, Partner & Compliance APIs, selective disclosure, regulated-payout link, published cost report | Testnet |
| 03 | Production hardening & launch | Independent security review, RBAC, versioned APIs & SDKs, operational runbook, final documentation | Audit-gated mainnet |
The confidential-transfer stack is an unaudited ecosystem preview today. It reaches mainnet only after an independent security review clears — a gate, not a date.
Before any mainnet deployment, the stack is submitted for an independent security review. The result — not a target date — determines whether launch proceeds.
Mainnet launch is not scheduled ahead of the review. It is unlocked only when the review outcome is cleared, keeping delivery honest about what has actually been verified.
Until the gate clears, everything runs on testnet with no real value in motion. The path to production is deliberate, reviewable and reversible.
The output is not a private product moat. It is a reusable reference implementation that any regulated operator can build confidential payments on Stellar with.
Regulated remittance operators, partner banks and PSPs can adopt the same dashboards, APIs, SDK and relayer to launch confidential USDC settlement without rebuilding the cryptography.
Remi contributes the software, compliance and operations layer that makes Stellar's confidential-transfer capability usable — not a new asset and not a financial instrument.
The work exercises Stellar's Protocol 25/26 zero-knowledge host functions and the emerging confidential-transfer contract standard, feeding real-world learnings back to the ecosystem.
Dashboards, APIs, the client SDK, the relayer and the Soroban benchmark are all published for the community to inspect, reuse and extend.