Sui just shipped another protocol cleanup. The real work is cost control.
Mysten's latest release is less about flashy features and more about tightening the knobs that decide what validators actually have to carry.
CryptoVibe Desk · sui · mysten-labs · protocol-upgrades
- →Mysten Labs released Sui testnet-v1.78.1 with Protocol Version 135 on August 25, after mainnet hit Version 134 two days earlier.
- →The important part is configuration: unpaid deferral gets disabled everywhere, while mainnet absorbs cost and consensus-limit changes from v134.
- →Watch whether operators see fewer upgrade and RPC edge cases before the next mainnet release, because this cleanup only matters if it reduces friction.
- protocol version → A protocol version is the rule set validators use to agree on what the chain accepts.
- consensus block limit → A consensus block limit sets how much work or data can fit into one agreed block.
- RPC → RPC is the way apps ask a blockchain node for data or send it transactions.
- framework upgrade → A framework upgrade changes the core on-chain packages that other Sui apps depend on.
Sui Protocol Version 135 is now on testnet. Mysten Labs released testnet-v1.78.1 on August 25, according to its GitHub release. The release follows mainnet-v1.77.3 from August 23, which moved mainnet to Protocol Version 134.
The code does what the announcement says, plus cleanup. Mysten disabled defer_unpaid_amplification on all networks. It also applied v134's original_package_id cost changes and consensus block limits on mainnet. That is the real story here: Sui is tightening execution cost and consensus settings, not shipping a wallet feature.
At the contract level, original_package_id matters because framework packages are not normal app code. They sit underneath the things developers build. If their cost model is off, the chain can price important operations poorly. That becomes an operator problem first, then a user problem later.
The tradeoff is boring but useful. Sui gets stricter limits and cleaner accounting. Teams also get another round of version edges across nodes, gRPC, GraphQL, and CLI paths. If you're a Sui dev reading this, your bag is not the token price today. It's whether your tooling keeps returning the same data after the upgrade.
The release also includes operator-facing fixes. The embedded RPC store now has bitmap periodic compaction defaulting to 30 days, per Mysten's notes. The TransactionExecutionService gRPC change is only error-message text, with no API shape change. That distinction matters. A changed error string can break sloppy tests, but it should not break a real client contract.
This is a configuration cleanup release, for now. Mainnet's v134 config now contains only the deferral disable, matching the 1.77 branch, according to the release notes. That sounds small, but chain operations are mostly small knobs that become expensive when they drift. Read the PR diff, not the thread.
The implication is simple. Mysten is using the next protocol step to reduce loose behavior before it becomes production debt. That is not glamorous. It is how serious chains age without making every upgrade feel like a migration weekend.
Mysten's choice to disable defer_unpaid_amplification across all networks was the right call because unpaid execution behavior should not stay a configurable footgun across branches.
Before Sui's next mainnet protocol release, watch whether release notes show zero API-shape changes for gRPC and GraphQL while keeping the v134 cost and consensus-limit settings intact.
Primary links and supporting reads used by the desk for this story.
Forward this.
