Sui has launched the public beta of Confidential Transfers on Devnet, giving developers and issuers a way to test private token flows before any production rollout. The feature is designed to hide transfer amounts and account balances on-chain while keeping senders, receivers and auditability visible under controlled access rules.
The release addresses a core limitation of public blockchains: every payment value is normally visible to anyone monitoring the ledger. Sui’s model changes that by keeping the amount inside a sealed layer, while still allowing approved parties such as issuers, exchanges, analytics providers or regulators to access sensitive information when required. The goal is privacy without removing compliance visibility.
Confidentiality Comes With Issuer Controls
Confidential Transfers use encryption and zero-knowledge proofs to verify that transactions are valid without exposing the underlying values. Mysten Labs’ public repository describes the system as using Twisted ElGamal homomorphic encryption and zero-knowledge proofs so balances and transfer amounts remain hidden while the network still validates correctness. The protocol is built to prevent overdrafts and hidden inflation without revealing transaction amounts.
The design is not equivalent to a fully anonymous privacy coin. Sender and receiver addresses, token type and timing remain visible, while the confidential data is only accessible through scoped and auditable permissions. Asset issuers can attach auditor keys, define compliance policies and maintain controls such as freezing or pausing confidential-token activity. That makes the feature aimed at financial workflows that require both confidentiality and oversight.
The repository also outlines practical workflow limits. Public-to-confidential wrapping and confidential-to-public unwrapping still touch the public coin layer, meaning those boundary operations reveal the amount and counterparties like normal Sui coin transactions. Privacy applies inside the confidential domain, not automatically across every step of the asset lifecycle.
Devnet Beta Remains a Testing Environment
The current beta includes open-source code, documentation, SDK components and example integrations, including a prototype wallet. The TypeScript SDK supports developer workflows such as merge-then-spend, where pending balances are folded into an active encrypted balance before a user spends. That reduces technical friction for builders testing confidential payment flows.
The implementation is still early. Mysten Labs’ repository explicitly says the code is a work in progress, has not been audited and should not be used in production. Known gaps include unfinished cryptography, a client SDK not yet designed for wallets and example apps that still store user secrets in browser local storage. That keeps the release firmly in developer-testing territory.
Sui said a Testnet launch is targeted later this year, but it has not provided a mainnet timeline. That means Confidential Transfers are not yet available as production infrastructure for live financial activity. The beta is intended to gather feedback from issuers, developers, exchanges and compliance partners before broader deployment.
The launch also comes as privacy features are becoming more important for institutional blockchain use cases. Payments, treasury flows and commercial transfers often require confidentiality, but regulated entities still need audit trails and access controls. Sui is positioning Confidential Transfers as a middle ground between full transparency and full anonymity.
For now, the clean takeaway is that Sui has opened Confidential Transfers for public beta testing on Devnet, giving developers a first look at private balances, hidden transfer amounts and controlled audit access. Until the system is audited and moved beyond Devnet, the feature should be treated as a promising privacy infrastructure test, not a production-ready mainnet release.
