Vol. 1 · 7 Jun 2026
tempowiki
← Field guide
Build

Build on Tempo: connect & deploy

Tempo is EVM-compatible: connect to mainnet (chain ID 4217) or the Moderato testnet (42431) with standard tooling. State-creating operations cost more by design to deter state bloat.

5 min read · Updated 2026-06-08

Connect your wallet or node

Tempo is EVM-compatible, so existing Ethereum wallets and clients work. There are two public networks:

  • Tempo Mainnet — chain ID 4217 (0x1079), RPC https://rpc.tempo.xyz
  • Moderato (Testnet) — chain ID 42431 (0xa5bf), RPC https://rpc.moderato.tempo.xyz

Both share the same predeployed system contracts, so code you test on Moderato behaves the same on mainnet. The block explorer for both is at https://explore.tempo.xyz.

Deploy with standard tooling

Because Tempo's execution layer is built on Reth and targets the Osaka hard fork, standard Solidity tooling — Foundry and Hardhat — works without modification. The full EVM opcode set is supported.

The one behavioural difference to remember: there is no native token, so BALANCE, SELFBALANCE, and CALLVALUE return 0. Contracts that assume a payable native coin need to be adapted to use TIP-20 stablecoins instead.

Design for the gas schedule

Tempo deliberately makes state creation expensive to deter state bloat. Under TIP-1000, new storage slots and new accounts cost 250,000 gas, and contract deployment costs 1,000 gas per byte — far above Ethereum.

The practical guidance is to pre-fund accounts and avoid patterns that create lots of new on-chain state. For high-frequency deposits, prefer virtual (forwarding) addresses (TIP-1022), which let you derive unlimited customer-specific addresses off-chain without per-address on-chain state. Tempo also offers native account abstraction — fee sponsorship, batched calls, scoped access keys, and passkey/P256 signatures — via its custom Tempo Transaction type (0x76), without requiring ERC-4337 bundlers.

Keep reading

Related

Citations

Sources

  1. [1]Tempo Docs — Connection details (chain IDs & RPC URLs) ↗
  2. [2]Tempo Docs — EVM compatibility (gas schedule & opcodes) ↗
  3. [3]Tempo blog — Account Abstraction on Tempo ↗

tempowiki is a neutral, sourced reference. Every claim above is drawn from the cited sources; where a detail is uncertain it is omitted rather than guessed.

Answer-first

Frequently asked

What are Tempo's chain IDs and RPC URLs?
Mainnet is chain ID 4217 (0x1079) at https://rpc.tempo.xyz. The Moderato testnet is chain ID 42431 (0xa5bf) at https://rpc.moderato.tempo.xyz.
Can I use Foundry and Hardhat?
Yes. Tempo's execution layer is built on Reth and targets the Osaka hard fork, so standard Solidity tooling works. The full opcode set is supported, except BALANCE, SELFBALANCE, and CALLVALUE return 0 (no native token).
Why is deploying contracts more expensive than on Ethereum?
TIP-1000 is Tempo's anti-state-bloat gas schedule: new storage slots and accounts cost 250,000 gas and deployment costs 1,000 gas per byte, nudging apps to pre-fund accounts and avoid bloating state.