Sui’s mainnet upgrade to v1.82.3, released on October 22, 2026, brings a suite of protocol and node‑level changes that refine fee structures, address handling, and developer tooling. The most visible shift is the introduction of protocol version 139, which activates the `enable_forwarding_addresses` flag on devnet and allows forwarding address registries to be treated as implicitly read system objects. This change paves the way for more flexible transaction routing in future releases.
A key economic adjustment is the reduction of the non‑refundable storage fee from 1% to 0.01% of the storage rebate on mainnet. The same reduction applies to protocol version 138, ensuring consistency across the network. Additionally, protocol 139 introduces a charge of 1% of the per‑byte object read cost for non‑system package inputs, a new metric that will influence how developers structure package interactions.
The upgrade also addresses randomness generation reliability. Under protocol version 131, a random‑beacon DKG that misses its timeout round would disable randomness for the entire epoch. The new logic now allows the DKG to continue running and can re‑enable randomness mid‑epoch if it completes, improving the robustness of epoch‑based randomness.
Node‑side improvements include a pruning mechanism for full nodes that do not enable object or checkpoint pruning. Older `executed_transaction_digests` entries are dropped after the previous epoch, limiting disk and memory usage. Consensus consumers can opt into full‑epoch replay with acknowledgements, simplifying state synchronization for new participants.
Developer tooling receives several enhancements. The gRPC layer now accepts an optional `x-sui-consistent-read-checkpoint` header, enabling clients to request data up to a specific checkpoint and receive an `Unavailable` error if the server cannot meet the deadline. When the `enable-simulate-allowed-proposers` flag is on, `SimulateTransaction` restricts returned transactions to allowed proposers for clients with a protocol version header of 136 or higher. A new signature scheme, `MLDSA65`, is added, allowing ML‑DSA‑65 signatures and multisig members to be submitted via `ExecuteTransaction` and verified by `VerifySignature`.
Finally, JSON‑RPC and subscription endpoints see refined error handling and richer response payloads. `SubscribeTransactions` and `SubscribeCheckpoints` now populate `effects` objects, clever errors, and event JSON when requested, aligning them with `GetTransaction`. Requests below a node’s retention period return `OUT_OF_RANGE` instead of an internal error, improving client diagnostics.
Together, these changes enhance Sui’s scalability, security, and developer experience, positioning the network for broader adoption and more efficient operation.
