Sui Devnet v1.79.0 Adds Protocol v136 and Transaction Controls
Sui has released devnet v1.79.0, introducing protocol versions 135 and 136 alongside transaction, package, and infrastructure changes. The Sui update disables unpaid amplification from protocol v135 across all networks and applies revised package costs and consensus block limits on mainnet. Protocol v136 adds a 10 MB package-loading limit in the Move VM.
The release also introduces proposer-restricted transaction expiration through TransactionExpiration::Validity. The feature is enabled only on devnet, allowing transactions to name the validators permitted to propose them. Full nodes now submit these transactions only to the listed validators. gRPC clients must preserve the allowed_proposers field when reconstructing transactions, or the transaction digest will change.
A new Sui PTB restriction limits how TxContext can appear in Move call signatures. Invalid transactions now fail earlier with a dedicated InvalidTxContext error. Additional package invariant checks were also added.
For infrastructure operators, the alternative JSON-RPC and GraphQL indexers now require --ledger-grpc-url and no longer support legacy Bigtable options. GraphQL adds multiGetBalances for querying balances across multiple addresses. The CLI also adds a --package-size option for Sui Move tests.
The changes are primarily technical and affect devnet users, node operators, developers, and tooling providers rather than end users directly.
Neutral
The expected market impact is neutral because Sui devnet v1.79.0 is primarily a software and infrastructure release, not a token-economic change. It does not announce a supply adjustment, staking change, major mainnet activation, partnership, or user-facing application launch. Most headline features, including proposer-restricted expiration, are enabled only on devnet.
In the short term, SUI trading is unlikely to receive a major fundamental catalyst. Developers and node operators may need to update clients, and temporary compatibility issues could create limited operational uncertainty, particularly for indexer operators and clients that reconstruct transactions. However, the release provides explicit migration requirements and should not materially affect network liquidity or market stability.
Over the longer term, stronger transaction validation, package-size limits, clearer PTB errors, and more targeted validator submission could improve reliability and developer experience. Similar protocol and client releases on major networks typically produce limited price action unless they coincide with a mainnet upgrade, outage, security event, or significant adoption announcement. Traders should therefore treat this release as a technical development signal rather than a direct bullish or bearish catalyst, while monitoring whether the features move from devnet to testnet and mainnet.