Sui Says ‘Private Transactions’ Are Coming in 2026—Here’s What Builders Should Assume
Mysten has been signaling protocol-level private transactions for 2026. Until specs drop, builders should treat this as: privacy as a product primitive, not an…
Mysten Labs has publicly committed to shipping protocol-level private transactions on Sui by 2026, with the announcement led by Adeniyi Abiodun and echoed across official channels and Adeniyi’s Twitter. The framing is clear: privacy will be treated as a protocol primitive, not an afterthought or bolt-on feature. For builders, this means privacy assumptions should be foundational in product and contract design, even before technical specs are finalized.
The stated goal is default confidentiality at the protocol layer. Mysten Labs has emphasized that privacy will not be opt-in or limited to specific dApps, but rather embedded in Sui’s core transaction flow. This is a marked shift from the current state, where all Sui objects and transactions are public by default. Builders should plan for a future where user and object data may be shielded unless explicitly disclosed.
Selective disclosure and audit hooks are expected to be part of the design, allowing for granular compliance integration. Mysten’s messaging references regulatory frameworks like FATF and MiCA, suggesting that KYC/AML requirements will be addressable via protocol-native mechanisms. For developers, this means thinking about how to expose or prove transaction details to auditors or counterparties without breaking confidentiality for everyone else.
Sui’s object-centric model adds unique complexity to privacy at the object level. Unlike account-based chains, Sui’s parallel execution and object-level privacy granularity will require new patterns for managing confidential state transitions. Builders should anticipate changes in how object ownership, transfers, and state updates are handled, especially when privacy intersects with composability.
Performance is a recurring concern. Protocol-level privacy, especially if it leverages zero-knowledge proofs (ZK-SNARKs) or other unknown cryptographic primitives, will likely introduce a gas cost premium and impact throughput. The Sui team has referenced Mysticeti v2 as a key upgrade to maintain high TPS despite privacy overheads, but real-world benchmarks are not yet public. Builders should assume that transaction latency and block capacity could fluctuate during rollout and early mainnet phases.
Wallet and bridge compatibility will be a gating factor for adoption. Sui Wallet and Ethos have both signaled intent to support private transactions, but the details—especially around UX for private key management and selective disclosure—remain unannounced. Bridge compatibility is even less clear; cross-chain transfers involving private Sui objects will likely require new standards and relayer logic.
The biggest unknown is the cryptographic backbone. While zero-knowledge proofs (ZK-SNARKs) are the likely candidate, Mysten Labs has not committed to any specific primitive or library. This uncertainty makes it risky to pre-build privacy features that assume a particular ZK stack. Builders should modularize privacy-related code and avoid hard dependencies until the official cryptography is confirmed.
Gas cost premium is inevitable. Even with protocol optimizations, private transactions will be more expensive to execute and verify than public ones. This will affect UX and may create new economic incentives for transaction batching or off-chain privacy proofs. Developers should model for higher average gas fees in their unit economics.
The developer/testnet rollout timeline is still vague. Mysten Labs has only committed to 2026 for mainnet, with no public testnet dates or SDK previews. Builders should monitor Sui’s blog and Natsai for updates, and be prepared to participate in early testnets once announced.
For Sui, default confidentiality is not just a technical upgrade but a shift in the developer contract. Object-level privacy granularity, when combined with Sui’s parallel execution, means builders will need to rethink how data flows between objects and contracts, especially where selective disclosure or compliance integration is required.
Mysticeti v2 is positioned as the performance safeguard, but until benchmarks are released, developers should budget for potential TPS drops and increased latency during the privacy rollout. This is especially relevant for high-throughput applications that depend on Sui’s current performance profile.
Sui Wallet and Ethos wallet compatibility are essential for user adoption, but wallet UX for managing private keys and handling selective disclosure remains an open question. Developers should avoid assuming wallet-side support for advanced privacy features until more details are published.
Bridge compatibility will likely lag protocol-level privacy, given the added complexity of transferring private Sui objects across chains. Builders working on interoperability should anticipate new relayer logic and standards, and avoid hardwiring assumptions about bridge behavior until Mysten Labs clarifies the model.
Anticipated privacy as a protocol primitive will require builders to revisit compliance integration, especially as FATF and MiCA guidance evolves. Protocol-native audit hooks may become a baseline expectation for regulated apps, so teams should begin mapping out how object-level privacy granularity intersects with selective disclosure requirements.
The parallel execution model on Sui means that privacy features could impact throughput/TPS in unpredictable ways, particularly if Mysticeti v2’s optimizations are not fully realized at launch. Builders should track performance updates closely and plan for phased rollouts or fallback modes if TPS dips below current baselines.
Unknown cryptographic primitives remain a blocker for long-term planning. Until Mysten Labs finalizes its ZK-SNARKs or alternative proof system, developers should architect privacy features to be swappable, minimizing refactor risk as the protocol matures.
In the meantime, actionable planning means treating privacy as a first-class product primitive, designing for object-level privacy granularity, and preparing for compliance integration hooks. For questions or partnership opportunities, reach out via Contact. The next 18 months will be defined by uncertainty, but also by the opportunity to shape privacy as a core feature of the Sui ecosystem.
