Vol. 1 · 7 Jun 2026
Tempo logo
Coremainnetprotocol component

Tempo

The payments-first Layer 1 blockchain, incubated by Stripe and Paradigm.

Data completeness
85%
Confidence
90%
Sources
3
Last reviewed
7 Jun 2025
The take

What to know

Tempo is not trying to be a cheaper Ethereum. It is trying to be the settlement rail for stablecoin payments, payroll, remittances, treasury, and machine payments, with payment behaviour enshrined in the protocol.

Best for

  • +Stablecoin payments and payouts at scale
  • +Enterprises wanting predictable, stablecoin-denominated fees
  • +AI-agent and machine payments via MPP

Watch out

  • Validator set is initially permissioned
  • Audits were ongoing in mid-2026 with no active public bug bounty
  • Some features (sub-blocks, non-USD FX, privacy) are phased or disabled

The numbers

Metrics

Throughput (testnet confirmed)

20K TPS

Block time

600 ms

Integrated partners

60 partners


The record

Key facts

Type
Layer 1 blockchain, EVM-compatible (Reth SDK, targets Osaka)· 95%
Mainnet chain ID
4217 (0x1079)· 90%
Consensus
Simplex BFT (Commonware), ~600ms blocks, deterministic finality· 90%
Native token
None; fees paid in USD-denominated TIP-20 stablecoins· 95%
Incubated by
Stripe and Paradigm· 95%
Mainnet launch
18 March 2026 (with the Machine Payments Protocol)· 90%

Questions

FAQ

Does Tempo have its own token?
No. Tempo has no native gas token. Network fees are paid in USD-denominated TIP-20 stablecoins that have enough Fee AMM liquidity. No $TEMPO token or airdrop has been announced.
Who is behind Tempo?
Tempo was incubated by Stripe and Paradigm and operates as an independent company. Matt Huang, co-founder of Paradigm, leads it.
Is Tempo EVM-compatible?
Yes. It runs an EVM execution layer on the Reth SDK targeting the Osaka hardfork, so standard Solidity and Foundry-style tooling works, with payment-native differences such as zero native balance semantics.

The graph

Connected entities