Mysten Labs has released Sui testnet v1.80.1, which uses protocol version 137. The build includes updates to 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.
These 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.
Frequently Asked Questions
FAQs Sui Testnet v1801 and Protocol 137 Features for Node Operators
1 What is Sui Testnet v1801
Its the latest update to the Sui test network It brings more features from Protocol 137 mainly aimed at node operators
2 What is Protocol 137
Protocol 137 is a set of network upgrades for Sui It changes how nodes behave and communicate improving performance and reliability
3 Why should I care about this update as a node operator
Because it changes how your node works If you dont update your node may fall out of sync miss rewards or fail to connect properly
4 Do I have to upgrade my node
Yes if you run a node on Testnet Staying on an old version will likely cause errors or disconnections
5 How do I upgrade my Sui node to v1801
Pull the latest release from the official Sui GitHub repo rebuild or download the binary then restart your node Follow the official upgrade guide for exact steps
6 What new features does Protocol 137 add for node operators
It mainly improves consensus efficiency checkpoint handling and network communication between validators and full nodes Specifics are in the release notes
7 Will this update affect my staking rewards
On Testnet rewards arent real But on Mainnet similar upgrades can affect performance and rewards if you dont upgrade in time
8 What happens if I skip this upgrade
Your node may stop syncing get forked off the network or become unreachable by peers
9 How do I check if my node is running v1801
Run suinode version or check your nodes startup logs It should show v1801
10 Where can I find the official release notes
On the Sui GitHub releases page Always check there first for upgrade instructions and known issues
11 Is this a breaking change
For Testnet yesolder versions may not be compatible with the new protocol rules after the upgrade
12 Do I need to wipe my database before upgrading
Usually no But always read the release notessometimes a resync is recommended for major protocol changes