Sui just shipped a cleanup release. The boring fixes matter before money moves.
This is not a feature splash. It is Mysten tightening upgrade history, RPC answers, and compiler warnings before the next mainnet step.
CryptoVibe Desk · sui · protocols · developer-tools
- →Mysten Labs published Sui testnet-v1.78.0 on August 18, moving the release line to Protocol Version 134.
- →The important work sits in provenance, RPC behavior, subscriptions, and compiler warnings, not new user-facing features.
- →Watch whether these fixes reach mainnet after v1.77.2, because upgrade handling is where tooling usually breaks quietly.
- testnet → A testnet is a live practice network where developers run changes before they reach the real network.
- UpgradeCap → An UpgradeCap is the object that gives its holder permission to upgrade a Sui package.
- RPC → RPC is the request system apps use to ask a node for blockchain data.
- Move compiler → The Move compiler checks Move code before it runs on Sui.
Sui's v1.78.0 testnet release is plumbing work. Mysten Labs published the release on August 18 and moved the testnet line to Sui Protocol Version 134, according to the release notes.
The code does what the announcement says, plus something more useful. It tightens how Sui tools handle package upgrades, node responses, subscriptions, and bad Move code. That matters because upgrade state is where explorers, wallets, and indexers can quietly show users the wrong thing.
The most important change is framework support for retrieving the original package ID from an UpgradeCap. At the contract level, that means tooling can trace an upgraded package back to where it started. If you're building around Sui packages, that provenance is not a nice extra. It is how you avoid treating a later version like a totally separate object.
This is a cache invalidation problem, not a marketing problem. A package changes, but the surrounding tools still need a stable way to reason about identity. The tradeoff is more explicit upgrade tracking for less ambiguity in downstream systems.
The August 18 release also includes fixes across node, gRPC, GraphQL, and CLI behavior. GraphQL gets historical-cursor transaction subscriptions. TransactionExecutionService gets clearer mismatch errors. gRPC gets a plaintext listener option for trusted internal callers. The Move compiler now warns on constant expressions that will always error at runtime.
None of that sells a keynote. It does reduce the places where developers lose time on confusing answers. If you're a Sui dev reading this, those error messages are part of the product.
There is one operational detail worth watching. The embedded RPC store bitmap periodic-compaction default is 30 days in the August 18 testnet notes. That default can look boring until indexer teams discover it changes storage behavior under real load.
The timing also matters. The same v1.78.0 changes appeared first in the Sui devnet pre-release on August 17, then in testnet on August 18. The latest mainnet release in the provided bundle is still v1.77.2 from August 13, at Protocol Version 133.
So this is not mainnet news yet. For now, it is Mysten moving hardening work through the release path before users depend on it. Read the PR diff, not the thread. The useful part is not that Sui shipped another version. It is that the next version is cleaning up the places where infrastructure tends to lie by accident.
Mysten Labs' choice to harden package provenance before mainnet is the right call because upgrade history is where wallets and explorers quietly mislead users.
By the next Sui mainnet release, watch whether Protocol Version 134 lands with the original-package-ID UpgradeCap support and GraphQL historical-cursor subscriptions intact.
Primary links and supporting reads used by the desk for this story.
Forward this.
