Stable

• Name: Stable
• URL: https://stable.xyz/
• Category: stablecoin payments blockchain / USDT-native Layer 1 / agent-payments infrastructure
• Tags: ethereum-ecosystem
• Summary: Stable is a USDT0-first payments chain, not a generic EVM that happens to like stablecoins. The part worth keeping is direct stablecoin gas, enterprise blockspace policy, gas-waiver logic, transfer aggregation, and the explicit agent-payments push around x402 and MCP tooling.
• What it does:
  • Provides an EVM-compatible Layer 1 where USDT0 is both the gas token and the main settlement asset, while STABLE serves as the governance and staking token
  • Targets payment-heavy use cases including P2P transfers, subscriptions, invoice settlement, payroll, merchant flows, and pay-per-call APIs
  • Exposes core chain functionality to EVM contracts through precompiles and keeps standard Ethereum tooling largely unchanged apart from gas, finality, and dual-role asset semantics
  • Adds payments-specific infrastructure such as guaranteed blockspace for enrolled enterprise workloads, gas-waiver flows, and a transfer-aggregation pipeline for high-volume USDT0 settlement
  • Treats AI agents as first-class users, with docs covering MCP servers, agent wallets, paid MCP tools, and x402-based agent-to-agent or agent-to-API payments
• Key claims:
  • The docs position Stable as a delegated Proof-of-Stake Layer 1 with single-slot finality, roughly 0.7 second block times, and full EVM compatibility
  • The core-concepts and Ethereum-comparison pages say USDT0 is both the native balance and an ERC-20 token on the same underlying balance, which creates distinctive integration and indexing caveats that developers must handle explicitly
  • The key-features pages emphasize guaranteed blockspace, gas waivers, cross-chain USDT0 bridging, and transfer aggregation as differentiators for enterprise payment throughput
  • The tech-overview pages describe a four-layer stack spanning StableBFT, Stable EVM, StableDB, and split-path RPC, with Autobahn consensus and StableVM++ parallel execution framed as roadmap upgrades rather than already-live features
  • The AI/agents docs explicitly connect Stable to MCP tooling, agent wallets, and x402-priced HTTP endpoints, showing that the project is trying to become an agent-friendly settlement environment rather than only a human-operated payments chain
• Whitepaper: No canonical standalone Stable whitepaper or litepaper surfaced in this pass. The strongest source of truth is the official docs corpus, especially the llms.txt index plus the architecture, core-concepts, payments, and AI/agents pages; see ../whitepapers/stable-primary-sources-2026-04-27.md.
• Sources:
  • https://stable.xyz/
  • https://docs.stable.xyz/en/
  • https://docs.stable.xyz/llms.txt
  • https://docs.stable.xyz/en/explanation/key-features
  • https://docs.stable.xyz/en/explanation/core-concepts
  • https://docs.stable.xyz/en/explanation/tech-overview
  • https://docs.stable.xyz/en/explanation/ethereum-comparison
  • https://docs.stable.xyz/en/explanation/ai-agents-overview
  • https://docs.stable.xyz/en/explanation/x402
  • https://docs.stable.xyz/en/reference/tokenomics

Internal linkages

• Strongest payment-chain peers: plasma and tempo.
• Useful paid-request overlay contrast: x402.

Governance / control risk

• The leverage sits in validator and governance policy, USDT0 dependence, guaranteed-blockspace admission, gas-waiver rules, and which agent-payment or bridge paths get first-class support.

• So this is not just stablecoin gas on an EVM. It is a payments chain whose defaults can decide who gets priority throughput and which payment flows are easiest to operationalize.

• Last reviewed: 2026-06-02 UTC