This release focuses on strengthening execution safety and improving consistency across the network. As Stable continues to scale real-world stablecoin usage, v1.3.0 introduces targeted improvements across validation, EVM behavior, and RPC reliability to reduce edge-case risks and support production-grade infrastructure.
Stable v1.3.0 is a mandatory, non-backward compatible upgrade.
Upgrade activation: May 13, 2026 (around 07:00 UTC)
Upgrade height: 24077500
Recommended upgrade deadline for node operators: May 13, 2026
Partners running self-hosted infrastructure should upgrade before the deadline to avoid potential disruptions, including issues with deposit and withdrawal flows.
v1.3.0 introduces several improvements designed to tighten validation across the stack and reduce unintended execution paths.
System transaction handling was enhanced to validate not only the sender but also the destination and method selector, closing potential execution gaps. Transaction validation has also been strengthened across formats such as EIP-7702, with stricter checks on structure and authorization handling.
At the RPC layer, non-public namespaces are no longer exposed by default, and signing APIs are only enabled under explicit secure configurations. Input validation has also been tightened, including enforcement of EIP-55 address formatting and stricter constraints on query inputs.
This release expands protections around precompile execution.
The Prague precompile address range has been added to blocked addresses, and unknown precompile methods now require query gas. These changes reduce the risk of unintended execution and improve safety around low-level contract interactions.
v1.3.0 resolves several edge cases in EVM execution.
The upgrade includes corrected gas accounting for failed stateful precompile calls, fixes to refund behavior following ERC20 internal call failures, and improvements to precompile warm-set handling. The release also corrects COINBASE opcode behavior and aligns EIP-7702 authorization rollback with the specification.
This upgrade improves consistency across RPC responses and node behavior.
Fixes include resolving system transaction responses with from = 0x0, improving feeHistory error logging, and ensuring chainId consistency in historical full transaction responses. These changes improve reliability for indexers, explorers, and application backends interacting with Stable.
To ensure a smooth transition, we recommend that partners:
Partners running self-hosted infrastructure should prepare their Stable v1.3.0 upgrade process before May 13, 2026.
Node operators should stage the new binary in advance if using Cosmovisor, or be prepared to manually replace the binary and restart their node at the scheduled upgrade height if upgrading manually.
Validate deposit and withdrawal flows post-upgrade
Review any infrastructure relying on system transaction assumptions or RPC behavior
Monitor node logs and synchronization status during the upgrade window
Note: Partners using public or third-party RPC providers or the BSC version of $STABLE do not need to take any action.
Stable v1.3.0 is a mandatory upgrade. Nodes running older versions after activation will not function.
This upgrade does not involve a chain reset or state migration. Existing chain data is preserved, and no state export/import is required.
We’ll share additional technical references and updates ahead of activation.
Documentation: https://docs.stable.xyz
Mainnet Hub: https://hub.stable.xyz
Blog: https://blog.stable.xyz
X: @Stable
Community: https://discord.gg/stablexyz