Sui just added privacy math to its chain. The release note still has a catch.
This is the first major L1 bet that confidential DeFi should be a native primitive, not an app-level patch.
CryptoVibe Desk · sui · privacy · defi
- →Sui mainnet-v1.74.1 shipped on July 1 with protocol version 128 and new cryptographic operations in the changelog.
- →Ristretto255 and bulletproofs matter because they can support private amounts, private voting, and cleaner confidential DeFi design.
- →The catch is scope: the changelog says testnet, so developers need proof these calls are usable from Move on Sui now.
- Ristretto255 → Ristretto255 is a math system that lets apps handle hidden values in a safer, more standard way.
- bulletproofs → Bulletproofs are proofs that show a private number is valid without showing the number itself.
- DKG → DKG is a process where validators create shared cryptographic keys without one party holding the whole secret.
- epoch → An epoch is a fixed operating period after which the network updates validator and system state.
Sui added privacy primitives this week. MystenLabs' July 1 mainnet-v1.74.1 release says protocol version 128 is live. The changelog includes Ristretto255 group operations and bulletproofs range proof verification. It also includes a DKG advancement fix and a switch to timestamp-based epoch close.
The code-level bet is bigger than the release note. Sui is moving confidential-computation pieces closer to the chain itself. Most competing chains still push privacy into application wrappers, custom circuits, or off-chain proving systems. That works, but it makes every app rebuild the same sharp tool.
At the contract level, Ristretto255 and bulletproofs point at a specific future. Confidential AMMs can hide trade sizes. Private voting can hide choices until reveal. Payment apps can prove amounts sit inside valid bounds without making every amount public. If you're building on Sui, this is the part to read before the thread.
There is a catch. PR #26998 is described as enabling Ristretto255 and bulletproofs range proof verification “on testnet.” The same item appears in the July 1 mainnet changelog. That means the release proves protocol work landed, but it doesn't fully prove broad Move-callable mainnet availability. Devs need the exact callable surface, not vibes.
The other protocol changes are less exciting, but they matter. PR #26896 added always_advance_dkg_to_resolution and corrected a version 126 issue that had been changed after testnet release. Mysten says version 127 repairs it with no operator action required. That's validator coordination, not product marketing.
Today's devnet-v1.75.0 pre-release adds protocol version 129. It includes explicit bounds for binary pools, insert_before and insert_after APIs for sui::linked_table, and Google Cloud Storage support for state-sync archive fallback. Those are plumbing changes. They reduce footguns for developers and node operators.
The tradeoff is complexity for native power. Putting privacy math into the protocol can make confidential apps simpler later. It also means the protocol team owns more surface area forever. If demand for private swaps or private on-chain voting appears, Sui's bet compounds. For now, the only number that matters is version 128, plus whether developers can actually call the new primitives in production.
MystenLabs' choice to land Ristretto255 and bulletproofs in protocol version 128 is the right bet because confidential DeFi needs shared primitives, not every app writing its own wrapper.
Before the end of July 2026, watch for MystenLabs documentation or a Move example that proves Ristretto255 and bulletproofs calls work on production Sui.
Primary links and supporting reads used by the desk for this story.
Forward this.
