Sui has begun testing confidential transactions on its developer network (devnet), marking a step in the layer-1 blockchain’s push to introduce privacy-preserving features for on-chain activity.
Confidential Transactions Move to Devnet
The devnet rollout allows builders to experiment with private value transfers in a controlled environment before any broader release. Devnets are pre-production networks used to validate functionality, performance, and security with developer feedback. The testing phase will help assess how confidential transfers integrate with Sui’s object-centric architecture and Move-based smart contracts.
What Confidential Transactions Aim to Achieve
Confidential transactions are designed to obscure sensitive details of a transfer—such as amounts and, in some designs, counterparties—while still enabling the network to verify the transaction’s validity. Implementations commonly rely on advanced cryptography, including zero-knowledge proofs and cryptographic commitments, to keep data private without sacrificing the integrity of the ledger.
For users and developers, the capability can enhance privacy for peer-to-peer payments and DeFi workflows, offer optional selective disclosure for audits, and reduce data leakage that can arise from fully transparent public ledgers. Networks exploring such features typically balance privacy with compliance, performance, and interoperability considerations.
Why It Matters for Sui
Sui is a high-throughput layer-1 blockchain developed by Mysten Labs and launched in 2023. By advancing confidential transactions to devnet, the project signals ongoing work to broaden its feature set for applications that require stronger privacy guarantees while maintaining programmability and speed. The results of devnet testing will inform potential next steps toward wider testing and, if validated, a future production release.
Next Steps
Developers can begin evaluating confidential transfer workflows on devnet, provide feedback, and surface any issues ahead of further testing. Timelines for broader availability typically depend on the outcomes of security reviews, performance testing, and community input.