Sui testnet v1.80.1 brings protocol 137 changes for developers and node operators

Mysten Labs has released Sui testnet v1.80.1, introducing protocol version 137 and a series of changes across Sui's execution, data and node infrastructure.

The release is aimed mainly at developers, validators, full-node operators and teams building infrastructure around Sui. It includes updates to Move execution, cryptographic verification, GraphQL, gRPC, JSON-RPC and archival services.

Importantly, this is a testnet release, not a Sui mainnet upgrade. The changes give developers and infrastructure teams a chance to test compatibility before features move further through Sui's release process.

Protocol 137 adds several infrastructure changes

One of the more notable changes in protocol 137 affects Ristretto255 range-proof verification.

The release lowers the per-bit cost of bulletproof range-proof verification and raises the limit on batch size multiplied by range-bit length from 512 to 1,024. That allows larger batches to be verified in a single call.

Protocol 137 also introduces or enables several execution-related changes, including allowances support, additional programmable transaction block checks and changes to how certain constants are charged for gas.

For node operators, Sui has also added an opt-in consensus transaction pool that allows validators to pull transactions from a validator-side, gas-price-prioritized pool when proposing blocks.

These changes are largely invisible to regular SUI users, but they can matter for applications and infrastructure that interact with the network at a deeper level.

GraphQL and archival services get updates

The release also expands Sui's data infrastructure.

The GraphQL Subscription root for checkpoints, events and transactions is now part of the production schema. Operators still need to enable it for their deployments, but clients no longer need to rely on a staging-only schema for the subscription type.

The Bigtable-backed archival gRPC service also gains support for Move package queries, including retrieving packages, datatypes, functions and package versions.

That matters for developers and indexers that need access to historical Sui data without relying entirely on full nodes. Sui's documentation describes gRPC as the current recommended interface, while JSON-RPC has been deprecated.

Why developers should pay attention

The release is less about a feature that SUI holders will immediately see and more about strengthening the infrastructure underneath Sui applications.

Wallets, indexers, RPC providers and other applications can be affected by changes to execution behavior and data APIs even when users do not need to make any changes themselves.

That makes testnet releases particularly useful. Developers can test their applications against the new protocol version, identify compatibility issues and adjust their infrastructure before similar changes reach production.

Sui has also been pushing deeper into financial infrastructure and agent-driven applications. Its upcoming Basecamp event, for example, is expected to focus on finance, payments and infrastructure, following a recent teaser from Mysten Labs around a major new finance product.

This is not a mainnet upgrade

The most important distinction is deployment status.

Sui testnet v1.80.1 is not a completed mainnet upgrade. The release is explicitly tagged as a testnet build with protocol version 137.

That means developers can begin testing the new behavior, but performance or compatibility observed on testnet should not automatically be treated as evidence of how the same changes will behave on Sui mainnet.

The release also shows why the staging process matters. Changes to execution, gas accounting, GraphQL, gRPC and validator behavior can affect infrastructure even when there is no immediate user-facing change.

For now, the focus is on testing and compatibility. The more important milestone will come if and when these protocol 137 changes are enabled on mainnet and applications across the Sui ecosystem absorb them without disruption.