Sui Tests Confidential Transactions on Devnet as Privacy Push Advances
Key Takeaways
- •Sui began testing confidential transactions on its devnet on June 8, 2026.
- •The feature is designed to hide transaction amounts and balances while keeping sender and recipient addresses visible.
- •Sui is positioning the upgrade as selective confidentiality rather than full anonymity.
- •The feature is not live on mainnet and may depend on testing results, security review, developer input, and ecosystem readiness.
- •Potential applications include enterprise activity, payments, tokenized assets, treasury tools, payroll systems, private payments, and institutional settlement workflows.

Sui has begun testing confidential transactions on its devnet, moving a key privacy-focused upgrade from concept into a live developer environment. According to Sui's official update, devnet testing commenced on June 8, 2026.
The feature is designed to keep transaction amounts and balances private while leaving sender and recipient addresses visible for auditability. Sui is not presenting this as full anonymity. Instead, the network is aiming for selective confidentiality that could serve enterprise and financial applications where transaction-level privacy matters without eliminating audit trails.
Confidential transactions are not yet live on mainnet. The feature remains in a testing stage, and the final mainnet implementation may depend on performance metrics, security review, developer feedback, and broader ecosystem readiness.
Why Confidential Transactions Matter
Public blockchains are transparent by default. That transparency is useful for audits, verification, and trust, allowing anyone to inspect balances, transactions, contracts, and fund flows. However, it also creates challenges for certain categories of users.
Businesses may not want competitors to see balances or payment amounts. Institutions may need privacy for commercial activity. Individual users may not want every transaction detail permanently visible. Financial applications may require confidentiality without becoming fully opaque.
By hiding amounts and balances while keeping addresses visible, Sui is exploring a middle ground. The network could support greater privacy without making activity impossible to audit. That approach could be particularly relevant for enterprise use cases, payments, tokenized assets, and applications where transaction-level confidentiality is a priority.
Privacy Without Full Anonymity
The distinction between confidentiality and anonymity is central to Sui's approach. A fully anonymous system can hide both participants and values, which may appeal to some users but can create compliance and regulatory concerns. Networks such as Monero and Zcash have demonstrated strong privacy protections, but some privacy-oriented assets have faced exchange delistings and regulatory scrutiny in various jurisdictions. A selective confidentiality model keeps some information visible while protecting sensitive financial details.
Sui's design follows that second model. Sender and recipient addresses remain visible, while amounts and balances can be shielded. That structure may make the feature more acceptable for businesses and regulated entities that need audit trails but do not want to expose all commercial details.
The approach also aligns with a broader market trend. Crypto privacy is becoming increasingly nuanced. Projects including Aztec and Secret Network have pursued encrypted or privacy-preserving transaction models, and the question is no longer simply whether transactions are public or private, but rather what information should be visible, to whom, and under what conditions. Networks capable of offering flexible privacy may gain an advantage as blockchain applications move beyond speculative trading.
Devnet Testing as a Stage for Scrutiny
Privacy upgrades require careful testing. Any cryptographic feature that changes what users can see or prove introduces risk. Developers need to evaluate performance, wallet compatibility, edge cases, transaction costs, and security assumptions. Auditors need time to review the implementation.
Devnet provides a controlled environment for that work. It gives developers a place to experiment before users rely on the feature with real value on mainnet. Feedback from the testing phase can shape the final implementation and determine whether changes are needed before a broader rollout.
For Sui, the devnet phase also gives ecosystem builders an opportunity to consider potential applications. Confidential transactions are infrastructure, and their value depends on what developers construct with them.
Sui's Enterprise Positioning
Sui, developed by Mysten Labs, has frequently positioned itself around high-performance applications, object-based architecture, and developer-friendly tooling. The network's Move programming language has roots in Meta's discontinued Diem project, and the protocol has emphasized throughput and low latency as differentiators. Privacy features could reinforce that positioning.
Enterprise users may be more willing to explore public-chain applications if they can protect sensitive financial data. The addition of selective confidentiality gives the network another technical capability to highlight.
The same logic extends to decentralized finance and payments. If users can move assets without exposing exact amounts to the entire market, new product designs become feasible. Treasury tools, payroll systems, private payments, and institutional settlement workflows could all benefit from selective confidentiality.
The challenge remains adoption. A devnet feature becomes meaningful only if it reaches mainnet safely and is subsequently adopted by real applications.
For now, Sui's confidential transaction work represents a notable infrastructure step. It signals that the network is addressing privacy while avoiding the position that all activity must be fully hidden. That middle ground may grow increasingly relevant as blockchain technology moves closer to mainstream financial use.
This article was written by the News Desk and edited by Samuel Rae. This report is based on information released in disclosures at primary source documentation.