Sui Protocol v1.79.1 Adds Protocol v135 and v136

| github.com
Sui Protocol v1.79.1 introduces protocol versions 135 and 136, updating transaction validation, Move package loading, consensus limits and validator networking. From protocol version 135, unpaid amplification is disabled across all networks. Mainnet also receives revised package costs and consensus block limits. Version 136 adds a 10MB Move VM package arena limit and additional package invariant checks. The Sui Protocol upgrade introduces TransactionExpiration::Validity, which restricts selected transactions to named consensus proposers. The feature is currently enabled only on devnet. Full nodes will route these transactions only to the specified validators. PTB TxContext rules are also stricter, with invalid structures failing earlier through an InvalidTxContext error. gRPC clients must preserve the allowed_proposers field when reconstructing simulated transactions to avoid mismatched transaction digests. Indexer operators must now use --ledger-grpc-url for alternative JSON-RPC and GraphQL services, while Bigtable options have been removed. GraphQL adds multiGetBalances for querying multiple addresses, and the CLI introduces a Move test package-size limit. For traders, the Sui Protocol release is mainly a technical and infrastructure upgrade, not an immediate SUI price catalyst.
Neutral
The release is unlikely to create a direct short-term price catalyst for SUI because it does not introduce a token-economic change, major liquidity event or immediate mainnet feature with broad user visibility. Devnet-only proposer restrictions further limit near-term market impact. Traders may initially treat the upgrade as routine infrastructure news. Over the longer term, stricter transaction validation, package safeguards, improved proposer routing and clearer indexer requirements could support network reliability and developer confidence. These improvements may be modestly constructive for SUI if they encourage application growth and usage, but any price effect is likely to depend on adoption, transaction activity and broader crypto-market conditions. Historical protocol upgrades typically have limited lasting impact unless they materially change network usage or token demand.