Subscribe to Stable
>1K subscribers
Share Dialog
We’re pleased to announce an upcoming Stable Mainnet protocol upgrade: Stable v1.2.0 on February 4, 8:00 AM UTC.
This release is focused on strengthening the network’s production readiness through improvements to token usability, developer ergonomics, and chain observability. The intent is to reduce friction for integrators and improve the reliability of downstream infrastructure (indexers, explorers, analytics, wallets, and application backends) operating on Stable.
With v1.2.0, USDT0 becomes the native gas asset on Stable, replacing gUSDT. This removes the need to wrap or unwrap gas assets and unifies fee payment and settlement in a single stablecoin-denominated flow, simplifying wallet UX and integrations.
v1.2.0 adds a protocol-level on-chain signal when an undelegation completes. This enables applications and indexers to track staking lifecycle completion deterministically through chain data, without relying on polling or inferred state.
Note: This is an observability improvement, not a Stable Hub UI change. Hub UI support will follow in a separate release.
Share Dialog
We’re pleased to announce an upcoming Stable Mainnet protocol upgrade: Stable v1.2.0 on February 4, 8:00 AM UTC.
This release is focused on strengthening the network’s production readiness through improvements to token usability, developer ergonomics, and chain observability. The intent is to reduce friction for integrators and improve the reliability of downstream infrastructure (indexers, explorers, analytics, wallets, and application backends) operating on Stable.
With v1.2.0, USDT0 becomes the native gas asset on Stable, replacing gUSDT. This removes the need to wrap or unwrap gas assets and unifies fee payment and settlement in a single stablecoin-denominated flow, simplifying wallet UX and integrations.
v1.2.0 adds a protocol-level on-chain signal when an undelegation completes. This enables applications and indexers to track staking lifecycle completion deterministically through chain data, without relying on polling or inferred state.
Note: This is an observability improvement, not a Stable Hub UI change. Hub UI support will follow in a separate release.
This release fixes a Solidity compatibility issue affecting balanceOf() calls on the STABLE token for certain older compiler versions, improving reliability for teams migrating existing contracts.
v1.2.0 introduces API-managed gas waivers for controlled zero-gas flows, designed for onboarding and user-facing payment experiences, with safeguards such as per-transaction limits, block caps, and rate limiting.
This release also includes dependency upgrades and stability improvements to support continued production performance and operational resilience.
To ensure a smooth transition, we recommend that partners:
Confirm support for USDT0-based gas fee handling across signing, fee estimation, and transaction submission flows.
Update indexers / analytics pipelines to listen for the new undelegation completion event signal.
Validate STABLE token integrations, particularly if supporting older Solidity builds.
Review any workflows that rely on prior gUSDT assumptions.
Check our FAQ and reach out to the Stable team if you have any enquiries.
We will share additional release notes and technical references ahead of activation. Stay tuned!
Documentation: https://docs.stable.xyz
Mainnet Hub: https://hub.stable.xyz
Blog: https://blog.stable.xyz
X: @stable
Community: https://discord.gg/stablexyz
This release fixes a Solidity compatibility issue affecting balanceOf() calls on the STABLE token for certain older compiler versions, improving reliability for teams migrating existing contracts.
v1.2.0 introduces API-managed gas waivers for controlled zero-gas flows, designed for onboarding and user-facing payment experiences, with safeguards such as per-transaction limits, block caps, and rate limiting.
This release also includes dependency upgrades and stability improvements to support continued production performance and operational resilience.
To ensure a smooth transition, we recommend that partners:
Confirm support for USDT0-based gas fee handling across signing, fee estimation, and transaction submission flows.
Update indexers / analytics pipelines to listen for the new undelegation completion event signal.
Validate STABLE token integrations, particularly if supporting older Solidity builds.
Review any workflows that rely on prior gUSDT assumptions.
Check our FAQ and reach out to the Stable team if you have any enquiries.
We will share additional release notes and technical references ahead of activation. Stay tuned!
Documentation: https://docs.stable.xyz
Mainnet Hub: https://hub.stable.xyz
Blog: https://blog.stable.xyz
X: @stable
Community: https://discord.gg/stablexyz
No comments yet