Sui just changed how it handles failed withdrawals. The release notes don't say what changed, and that's the catch.
DeFi contract authors on Sui just got a silent failure-mode change with protocol version 126. The only place to find the actual delta is the PR diff.
CryptoVibe Desk · sui · protocol-upgrade · defi
- →Sui shipped mainnet-v1.73.2 today, advancing to protocol version 126, with a documented change to how the runtime handles insufficient-funds withdrawals.
- →The release notes name the change but not the delta, which means any DeFi contract that branches on specific withdrawal error types has an unknown variable until someone reads the diff.
- →Watch for DeFi protocols on Sui reporting unexpected withdrawal behavior in the two weeks after protocol version 126 finishes activating across the network.
- protocol version → A number that marks which set of rules the Sui network is running. Smart contracts built against one version may behave differently under the next.
- runtime → The part of Sui's software that executes contract code when a transaction fires. Changes here change what happens when your contract hits an edge case.
- failure mode → What a smart contract does when a transaction cannot complete. DeFi contracts often check for specific failure types and branch their logic based on which one fires.
Sui shipped mainnet-v1.73.2 today, quietly moving the on-chain protocol version to 126.
The key change: how the runtime handles a failed withdrawal. The release notes say the behavior changed. They don't say how.
Per MystenLabs, the change lives in PR #26849. The notes describe it as altering "how insufficient funds for withdrawals are handled" and nothing more. If you've built a Sui contract that handles withdrawal errors, the announcement won't tell you whether your error assumptions still hold. Read the diff.
At the contract level, this matters more than the headline implies. Predictable failure modes are what DeFi protocol authors build on. A lending contract that gates collateral release on a successful withdrawal is trusting the error type stays constant. A vault that catches failures and reroutes funds has the same dependency. A silent change to that behavior is a cache invalidation problem: nothing breaks until it does, and then it breaks in production.
The rest of the release is more routine. Sui's GraphQL layer picks up checkpoint-by-digest lookup and a new asTransactionObject query type, which indexers and block explorers have needed. The sui move format CLI now passes through to prettier-move, the auto-formatter that has become the de facto standard in the Move ecosystem.
There's also a saturating-math fix in the indexing framework's retry path. Without it, a specific edge case in streaming retry backoff could cause an indexer to stall indefinitely. Node operators running full indexers should take this update. The fix converts a potential infinite wait into a bounded retry.
One note: the epoch-advancement change in this release applies to Testnet only. It switches from validator-vote-driven epoch advances to timestamp-driven ones. This is not a Mainnet change.
Sui contract authors: PR #26849 is the read before your next deployment. The release notes told you the category. The diff tells you the delta.
MystenLabs named the change without naming the delta. DeFi contract authors on Sui are now in production with an unknown variable, and the release notes won't bail them out.
Any DeFi protocol on Sui posting an incident report citing unexpected withdrawal behavior after protocol version 126 activation. Watch for this within two weeks of today.
Primary links and supporting reads used by the desk for this story.
Forward this.
