Tempo

• Name: Tempo
• URL: https://tempo.xyz/
• Category: Stablecoin payments blockchain / settlement infrastructure / payments-first smart-account platform
• Tags: ethereum-ecosystem
• Summary: Tempo is a payments-first chain, not a general-purpose L1 with a payments page bolted on. The part worth tracking is stablecoin-denominated gas, dedicated payment lanes, custom transaction flows for sponsorship and scheduling, and private Zones with issuer and compliance hooks.
• What it does:
  • Provides a payments-optimized blockchain for stablecoin transfers, issuance, settlement, and smart-contract applications
  • Lets users pay transaction fees directly in supported USD stablecoins instead of a native volatile gas token, with a protocol-level Fee AMM handling conversion to validators’ preferred fee asset
  • Introduces Tempo Transactions, a custom EIP-2718 transaction type with fee sponsorship, batch calls, scheduled payments, passkey-friendly account flows, and concurrent transaction support
  • Enshrines payments-oriented primitives including TIP-20 token extensions, dedicated payment lanes, structured memo/reconciliation patterns, and a built-in stablecoin DEX
  • Offers private Tempo Zones: separate execution environments anchored to Tempo where balances and transaction history are hidden from public observers while issuer compliance policies remain enforceable
  • Publishes deep first-party docs, SDKs, CLI tooling, protocol references, wallet/account guides, and open-source repos for the main chain and Zones stack
• Key claims:
  • Official site and docs describe Tempo as a “payments-first blockchain” or “the blockchain for payments at scale,” built around stablecoin-native payments rather than generic chain activity
  • Tempo states that it has no native token for gas; fees are paid directly in USD stablecoins and TIP-20 transfers target sub-millidollar cost levels
  • The protocol docs present Tempo Transactions as a core differentiator, emphasizing batch payments, sponsorship, access keys, scheduled execution, and parallel transaction throughput
  • Tempo markets dedicated payment lanes and deterministic finality as protection against the noisy-neighbor problems that hit general-purpose chains during congestion
  • Tempo Zones are framed as compliance-aware privacy infrastructure: private balances and transfers, sequencer visibility for compliance, validity proofs, and inherited TIP-403 issuer-policy enforcement
  • The public ecosystem materials show Tempo courting a broad payments stack of issuers, ramps, wallets, compliance vendors, custody platforms, and data / infra partners
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Tempo’s official site, docs portal, protocol references, ecosystem pages, and open-source GitHub repositories for the main chain and Zones; see ../whitepapers/tempo-primary-sources-2026-04-25.md.
• Sources:
  • https://tempo.xyz/
  • https://tempo.xyz/ecosystem
  • https://docs.tempo.xyz/
  • https://docs.tempo.xyz/llms.txt
  • https://docs.tempo.xyz/learn/tempo/
  • https://docs.tempo.xyz/protocol/transactions/
  • https://docs.tempo.xyz/protocol/fees/
  • https://docs.tempo.xyz/protocol/zones/
  • https://github.com/tempoxyz
  • https://github.com/tempoxyz/tempo
  • https://github.com/tempoxyz/zones

Internal linkages

• Strongest payment-chain peers: plasma and stable.
• Useful asset-and-issuer contrast: circle-usdc.

Governance / control risk

• The leverage sits in validator admission, sponsored-transaction defaults, fee-AMM policy, payment-lane allocation, and the Zone operators who get to enforce privacy and compliance rules in practice.

• So the clean read is not payments chain in the abstract. It is a stablecoin settlement chain whose routing, privacy, and issuer-policy surfaces can still centralize fast.

• Last reviewed: 2026-06-02 UTC