Sui shipped a hardening upgrade. The important changes are limits, costs, and cleanup.
This is not a shiny feature drop. It is Mysten tightening the parts that decide what nodes accept, price, and serve.
CryptoVibe Desk · sui · infrastructure · validators
- →Mysten Labs released Sui mainnet-v1.78.1 with Sui Protocol Version 135, according to its August 27 release notes.
- →The release turns off defer_unpaid_amplification everywhere and moves mainnet onto cost and consensus limits first planned for v134.
- →Watch node, RPC, GraphQL, and indexer behavior through September, because hardening releases usually fail at the edges.
- protocol version → A protocol version is the rule set that Sui validators use to decide which transactions and blocks are valid.
- validator → A validator is a machine run by an operator that checks transactions and helps keep the chain moving.
- RPC → RPC is the request layer apps use when they ask a blockchain node for data or submit transactions.
- indexer → An indexer reads blockchain data and organizes it so apps can search it quickly.
Sui's v1.78.1 is a hardening release. Mysten Labs released mainnet-v1.78.1 on August 27 with Sui Protocol Version 135, according to the release notes. The testnet build landed two days earlier, on August 25, with the same protocol-version changes.
The code path matters more than the version tag. This release disables `defer_unpaid_amplification` on all networks. It also applies the original_package_id costs and consensus block limits that were planned in v134 to mainnet. That is not a product launch. It is a rule-tightening pass.
At the protocol level, cost changes are not cosmetic. They decide which transactions remain cheap, which ones get priced out, and where spam becomes expensive. Consensus block limits do the same kind of work one layer lower. They put firmer bounds on what validators can pack into the system.
If you're running Sui infrastructure, this is the release note you read twice. Feature releases break demos. Hardening releases break assumptions. The obvious risk is not that Sui users see a new button. The risk is that a node, indexer, or app server held an old mental model of costs and limits.
The embedded RPC store change is a good example. Mysten says fullnode operators can override the bitmap periodic-compaction interval. If they omit the setting, it stays at 30 days. If they set it to zero, periodic compaction turns off. That is a small config detail until storage behavior starts showing up in operator dashboards.
The same release also carries node, gRPC, GraphQL, and CLI fixes. Those sound like edge cleanup because they are. But most chain reliability failures live at edges. Apps hit GraphQL. Wallets and services hit RPC. Validators discover the real shape of limits under load.
There is a useful secondary lesson from the Pyth Hermes migration context. CryptoSlate reported that Sui builders using Pyth had to update both client-side price fetching and on-chain Move package dependencies. Different release, different source quality, but the pattern is familiar. Infrastructure changes rarely stop at one layer.
Sui v1.78.1 looks boring in the right way. The tradeoff is fewer loose settings for more predictable mainnet behavior. Read the release diff, not the headline number.
Mysten is making app teams reverse-engineer the v134-to-v135 cost changes. That is the weak spot: transaction shapes can change price before builders know what broke.
Before September 30, 2026, watch whether Sui GitHub issues show validator stalls or GraphQL/indexer regressions tied to mainnet-v1.78.1.
Primary links and supporting reads used by the desk for this story.
Forward this.
