Skip to main content
This tab holds the concepts, architecture, and narrative context for Stable. It’s the background reading that sits behind every capability tab — why USDT0 is the gas token, how single-slot finality works, how payments, confidential transfers, and guaranteed blockspace fit together, and what’s on the roadmap. Looking to ship something specific? Jump to the capability tab instead: Accounts, Payments, Contracts, AI/Agents, or Infrastructure. Or run the Quick start to send a testnet transaction in five minutes.

​
Foundation

Overview

What Stable is and how to read this documentation.

Key features

Headline specs: single-slot finality, USDT0 as gas, full EVM compatibility.

Difference from Ethereum

What stays the same and what changes when you port from Ethereum.

Core concepts

USDT0 dual role, guaranteed blockspace, transfer aggregator, finality.

​
USDT0 behavior

USDT0 behavior on Stable

Dual-role balance, reconciliation events, and contract design rules.

USDT as gas

Why Stable uses USDT0 to pay for gas and what that means for fees.

Flow of funds

How USDT moves end-to-end across Stable.

USDT0 features

Every USDT0-specific feature with links to each.

​
Architecture

Technical overview

Consensus, execution, database, and RPC layers in one page.

Core optimizations

The performance work behind sub-second finality.

Finality

Single-slot finality, reorg behavior, and what “confirmed” means.

Gas pricing

Base-fee-only model priced in USDT0.

​
Use case narratives

Payments

Why Stable fits P2P, subscriptions, invoices, and pay-per-call.

Payroll

Batched and scheduled payroll runs on Stable.

Sponsored transactions

Letting applications cover gas for their users.

Private transfers

Upcoming confidential payment flows.

Quick start

Send a first transaction on testnet before diving deeper.

Technical roadmap

What’s shipped and what’s coming.

FAQ

Common answers about chain IDs, RPC endpoints, and onboarding.
Last modified on April 23, 2026