Sui mainnet v1.78.1 upgrade: protocol 135, RPC/GQL fixes
The Sui mainnet v1.78.1 release ships Protocol version 135 (commit mainnet-v1.78.1). It disables defer_unpaid_amplification on all networks and aligns mainnet main settings with the 1.77 branch, including v134 original_package_id costs and consensus block limits.
Developers get better upgrade-cap introspection: the sui-framework adds the ability to fetch the original package ID from an UpgradeCap. Node operators also receive operational controls and stability improvements.
Key infrastructure changes include: a fix for a spurious “upgraded system packages are not locally available” invariant during framework upgrades; the ability for fullnode operators to override the embedded RPC store bitmap periodic-compaction interval (default 30 days; 0 disables periodic compaction); and isolation of bitmap pruning state per database.
For APIs, gRPC error messages now include the offending object id for version/digest mismatch while keeping the same API shape. Additionally, sui-kv-rpc can start a second unencrypted gRPC listener for trusted internal callers (plaintext-address).
GraphQL adds transaction subscription support from a historical cursor, and CLI/Move compiler updates improve correctness by fixing an inlining bug for cast operations and adding warnings for constant expressions that will always error at runtime.
Overall, this is a tech/infra upgrade focused on protocol parameter alignment, upgrade tooling, and reduced operational/API friction for Sui validators, full nodes, and application developers.
Neutral
This is a Sui core protocol and node/API maintenance release (mainnet v1.78.1), not a tokenomics or network-usage shock. The Protocol 135 change mainly tweaks internal amplification/defer behavior and aligns cost/consensus limits, while the rest focuses on correctness fixes (invariant, error diagnostics) and operational controls (RPC bitmap compaction/pruning, safer pruning isolation).
Historically, similar chain upgrades that improve upgrade-cap tooling, reduce spurious invariants, and enhance API observability tend to lower integration and reliability risk rather than directly driving demand. In the short term, traders may see minor sentiment swings around upgrade timelines, but liquidity and market stability usually remain governed more by broader macro flows and Sui ecosystem activity than by these implementation details.
In the long term, better upgrade tooling and clearer error messages can reduce developer friction and node operation issues, which supports steady ecosystem building. However, since the article does not indicate major throughput, fees, or staking changes, the expected market impact is mostly neutral.