Stable primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Homepage and docs landing page

  • URLs:
  • Key takeaways:
    • The homepage is relatively sparse, but the docs are unusually rich and clearly act as the real source of truth
    • Stable positions itself as global infrastructure for instant USDT payments and as a Layer 1 where USDT0 is both the gas asset and a token developers can use directly
    • The docs landing page makes the project’s intended surface area explicit: accounts, payments, contracts, AI/agents, infrastructure, and learning materials

2) llms.txt index

  • URL: https://docs.stable.xyz/llms.txt
  • Key takeaways:
    • The llms.txt index is highly informative and exposes the breadth of the actual product surface faster than the homepage does
    • It shows Stable is not only a payments chain: the docs span consensus, execution, database architecture, system precompiles, AI/agent tooling, MCP integration, x402, gas waivers, guaranteed blockspace, and confidential-transfer plans
    • This strongly suggests Stable should be cataloged as a docs-first payments/control-plane project rather than only as a branded L1

3) Key features and core concepts

  • URLs:
  • Key takeaways:
    • Stable says its headline differentiators are single-slot finality, full EVM compatibility, USDT0 as gas, and cross-chain USDT0 bridging
    • The docs also foreground payments-specific features: guaranteed blockspace, gas waivers, a USDT transfer aggregator, and planned confidential transfers
    • The dual-role USDT0 design is a major architectural quirk: the same underlying balance is exposed as both a native asset and an ERC-20, with explicit indexing and contract-porting caveats

4) Ethereum comparison

  • URL: https://docs.stable.xyz/en/explanation/ethereum-comparison
  • Key takeaways:
    • Stable explicitly wants Ethereum developers to port without changing tooling, but not without changing assumptions
    • The docs say the biggest differences are deterministic finality, USDT0-denominated gas, no priority tips, and the dual-role asset model
    • This is high-signal because it clarifies Stable is not just another EVM chain with faster blocks; it changes the value and fee model in a very opinionated way around stablecoin settlement

5) Technical overview

  • URL: https://docs.stable.xyz/en/explanation/tech-overview
  • Key takeaways:
    • Stable describes a four-layer stack: StableBFT consensus, Stable EVM, StableDB, and split-path RPC
    • The docs distinguish clearly between what is live now and what is roadmap work, which is useful for avoiding over-crediting roadmap features as current reality
    • The architecture pages imply a hybrid design: standard EVM developer compatibility on top of a chain stack that borrows ideas and modules from Cosmos-style infrastructure

6) AI/agents and x402

  • URLs:
  • Key takeaways:
    • Stable treats AI agents as first-class users with self-custodied wallets, MCP-based docs/runtime access, and per-request paid services
    • The x402 explainer says Stable wants to make HTTP-native micropayments practical with sub-second settlement, a single-asset wallet model, and public facilitator infrastructure
    • This is a strong categorization clue: Stable is not merely selling consumer payments or chain throughput, but trying to become a settlement environment for agent commerce and API monetization

7) Tokenomics

  • URL: https://docs.stable.xyz/en/reference/tokenomics
  • Key takeaways:
    • Stable separates the payment asset (USDT0) from the governance/staking asset (STABLE)
    • The tokenomics page says STABLE secures the network through delegated PoS, governs upgrades, and may receive distributions sourced from USDT0 gas revenue
    • This helps clarify the economic model: Stablecoin-denominated user fees on one side, governance and validator incentives through a separate network token on the other

Whitepaper / technical-doc status

  • No canonical standalone Stable whitepaper or litepaper surfaced in this pass.
  • The strongest source of truth is the docs corpus itself, especially the llms.txt index and the architecture/core-concept pages.
  • If this project is revisited later, it may be worth checking whether a formal consensus paper, architecture paper, or token design paper appears as mainnet matures.

Research notes

  • Best current category for the library: stablecoin payments blockchain / USDT-native Layer 1 / agent-payments infrastructure.
  • The key insight is that Stable is trying to collapse three things into one environment: stablecoin settlement rail, EVM app platform, and agent-friendly payment substrate.
  • The docs are much more revealing than the homepage, especially because they openly document the chain’s unusual stablecoin-as-gas model, enterprise throughput primitives, and AI-agent integration surfaces.