Built for payments, not trading
Most blockchains are general-purpose platforms that can also move money. Tempo inverts that priority: it is a payments-first Layer 1, and many of its design choices only make sense through that lens.
The clearest example is stablecoin gas. Tempo has no native token; fees are paid in USD-denominated TIP-20 stablecoins, with a Fee AMM converting between them. A user moving dollars never has to acquire a separate, volatile gas coin — a recurring friction on general-purpose chains.
Finality and cost
Tempo produces blocks roughly every 500ms with deterministic sub-second finality via Simplex BFT — a confirmed transfer is settled and cannot be re-orged. Base fees for a simple transfer target under $0.001.
For a payment rail, deterministic finality is a meaningful difference from chains where finality is probabilistic and a merchant must wait for several confirmations. The trade-off is the safety-over-liveness rule: Tempo will halt if more than one-third of validators are unavailable, rather than risk conflicting histories.
The honest trade-offs
Tempo is not strictly 'better' than every alternative — it makes different trade-offs:
- Permissioned validators. Tempo launched with an approved validator set (Stripe, Visa, Zodia Custody, MoneyGram), with a stated path toward permissionless validation. This favours accountability over open participation today.
- No native asset. Removing the gas token simplifies UX but means the network's economics work differently from chains with a staked native coin.
- Payments-tuned EVM.
BALANCE/SELFBALANCE/CALLVALUEreturn 0, and state creation is deliberately expensive (TIP-1000), so some general-purpose contracts need adapting.
The neutral reading: Tempo optimises hard for dollar payments and machine-to-machine commerce, and accepts constraints elsewhere to do it.