This module is in active research and not finalized. Implementation details are subject to change.
Plasma is developing a compliant confidentiality-preserving transfer system for USD₮. The goal is to support confidential payments without introducing custom tokens, new wallets, or changes to core EVM behavior.This is not a full privacy chain. It is a lightweight, opt-in module designed to shield sensitive transfer data while remaining composable and auditable.
Stablecoins are used for real-world financial activity: payroll, business transactions, settlements, and cross-border flows. But every onchain transfer is fully public, exposing balances, counterparties, and transaction details.This limits adoption in scenarios where confidentiality is essential or even required.Plasma’s confidential transfer system aims to enable:
Hidden transfer amounts and recipient addresses
Encrypted memos for reference data
Private balances that can be received or sent without exposure
Selective disclosures using verifiable proofs when needed
While the architecture is still under design, we are evaluating a pragmatic and modular approach built directly on Ethereum standards:
Stealth Address TransfersTransfers are sent to one-time stealth addresses derived from the recipient’s public key, shielding the destination from public view. Only the intended recipient can detect and claim the funds.
Encrypted MemosOptional encrypted metadata can be attached to each transfer. Only wallets with the correct viewing key can decrypt it.
Private ↔ Public TransfersUsers can move USD₮ in and out of private flows using a native mechanism. No new tokens, wrappers, or bridges required.
Selective DisclosuresFor auditability or compliance, users may choose to disclose specific transactions using verifiable proofs. These are optional, scoped, and controlled by the user.
We are still evaluating technical tradeoffs across stealth address generation, indexing methods, encryption schemes, and proof mechanisms.The final design will prioritize pragmatic privacy, low integration burden, and future upgrade paths without overengineering or breaking compatibility.More technical detail will follow as the spec evolves.