What is Tempo?
Tempo is a Layer-1 blockchain purpose-built for payments. It combines EVM compatibility with payment-specific features like stablecoin gas fees, payment lanes, built-in compliance support, and the Machine Payments Protocol (MPP) for inline HTTP payments.Tempo is designed for high-throughput payment applications with sub-second finality and the ability to pay transaction fees in stablecoins instead of a volatile native token.
Key features
- Stablecoin gas fees — Pay transaction fees in USD stablecoins, eliminating the need for a volatile gas token
- Sub-second finality — Transactions finalize in approximately 500 milliseconds using Simplex Consensus
- Payment lanes — Dedicated blockspace ensures payment transactions always have room, even during network congestion
- Tempo Transactions — Custom EIP-2718 transaction type with fee sponsorship, batch calls, 2D nonces, access keys, and scheduled transactions
- TIP-20 token standard — Extended ERC-20 with ISO 20022 memos, compliance hooks, and 6-decimal precision for stablecoins
- Machine Payments Protocol (MPP) — HTTP 402-based inline payments for paid APIs, MCP tools, and agentic commerce
- Enshrined stablecoin DEX — Protocol-level exchange for stablecoin swaps with limit orders and flip orders
- EVM compatible — Deploy Solidity contracts using familiar tools like Foundry, Hardhat, and Remix
Network details
- Mainnet
- Testnet
| Property | Value |
|---|---|
| Network name | Tempo Mainnet |
| Chain ID | 4217 (0x1079) |
| Currency | USD stablecoins (no native token) |
| Block time | ~0.5 seconds |
| Finality | Sub-second (Simplex Consensus) |
| Explorer | explore.mainnet.tempo.xyz |
What is the Tempo API?
The Tempo API allows developers to communicate with the Tempo blockchain to build payment applications. To read data from and send transactions to the Tempo blockchain, an application must connect to a Tempo RPC node. When communicating with a Tempo RPC node, the Tempo client implements a JSON-RPC specification, a communication protocol allowing one to make remote calls and execute them as if they were made locally. Tempo supports all standard Ethereum JSON-RPC methods plus Tempo-specific extensions for payments and compliance.How to start using the Tempo API
To use the Tempo API, you need access to a Tempo RPC node.- Sign up with Chainstack.
- Deploy a Tempo node.
- Use your Chainstack endpoint in your applications.
Predeployed contracts
Tempo includes several predeployed system contracts for payments, tokens, and compliance. These addresses are the same on both mainnet and testnet:| Contract | Address | Purpose |
|---|---|---|
| TIP-20 Factory | 0x20fc000000000000000000000000000000000000 | Create TIP-20 stablecoin tokens |
| Fee Manager | 0xfeec000000000000000000000000000000000000 | Handle fee payments and conversions |
| Stablecoin DEX | 0xdec0000000000000000000000000000000000000 | Enshrined DEX for stablecoin swaps |
| TIP-403 Registry | 0x403c000000000000000000000000000000000000 | Transfer policy registry for compliance |
| pathUSD | 0x20c0000000000000000000000000000000000000 | First stablecoin deployed |
| Multicall3 | 0xcA11bde05977b3631167028862bE2a173976CA11 | Batch multiple calls |
| CreateX | 0xba5Ed099633D3B313e4D5F7bdc1305d3c28ba5Ed | Deterministic contract deployment |
| Permit2 | 0x000000000022d473030f116ddee9f6b43ac78ba3 | Token approvals and transfers |
Get testnet tokens
The faucet is only available on Tempo testnet. On mainnet, acquire stablecoins from issuers or ecosystem partners.
tempo_fundAddress RPC method on the public Tempo RPC:
Important differences from Ethereum
No native token balance
Tempo has no native token. Theeth_getBalance method returns a placeholder value. To check balances, query TIP-20 token contracts directly using balanceOf.
Stablecoin gas fees
Transaction fees are paid in TIP-20 stablecoins. The Fee AMM automatically converts between stablecoins, so users can pay in any supported USD token.Transaction receipts
Tempo transaction receipts include additional fields:feeToken— The TIP-20 token address used to pay feesfeePayer— The address that paid the fees (may differ from sender with fee sponsorship)