Sui Testnet v1.80.1 Expands Protocol 137 Features For Node Operators

TL;DR

• Mysten Labs has released Sui testnet v1.80.1 using protocol version 137.
• The build includes updates across protocol logic, GraphQL, JSON-RPC and archival services.
• This is a testnet release and should not be described as a live Sui mainnet upgrade.

Mysten Labs has published Sui testnet v1.80.1, giving developers and infrastructure operators an early look at protocol version 137 changes before they move further through the release process.

The build touches several parts of the stack, from Move execution and RPC behavior to archival services.

Protocol 137 Adds Several Developer-Facing Changes

The release expands what can be tested around cryptographic verification, package visibility and data services.

Among the changes, Ristretto255 range-proof verification becomes cheaper and supports larger batches, while the GraphQL subscription root moves into the production schema for operators that choose to enable it.

Archival infrastructure also gets broader package-query support through the Bigtable-backed gRPC service.

Those are not the kinds of changes most SUI holders will notice directly, but they matter to teams building wallets, indexers, trading systems and applications that depend on reliable network data.

The update also changes some execution and gas-accounting behavior under protocol version 137.

Testnet Means Exactly That

The important caveat is deployment status.

v1.80.1 is a testnet build.

It should not be described as a completed Sui mainnet upgrade, and any performance or behavior observed in the test environment should not automatically be treated as live mainnet behavior.

That is precisely why testnet releases exist.

They give operators and developers time to identify compatibility issues before a version becomes part of the production network.

For Sui, the release shows continued movement across the infrastructure stack without requiring users to take any immediate action.

The more interesting question comes later: which of these protocol 137 changes graduate into mainnet, and how smoothly the ecosystem absorbs them when they do.

Developers will also be watching compatibility rather than just new features. Changes to GraphQL, JSON-RPC and execution behavior can affect tooling even when no user-facing migration is required, so testnet gives indexers and application teams a place to catch assumptions before they become production incidents. Sui’s release cadence has been fast, which makes that staging process particularly important. A protocol version can look impressive in a changelog, but the real test is whether wallets, RPC services and applications continue working cleanly once the same code path reaches a busier environment.

This article was written by the News Desk and edited by Samuel Rae.