Stablecoin payments on Tempo
Native stablecoin L1: gas sponsored at the protocol layer.
Tempo is a stablecoin-native L1: the protocol pays validator gas in the stable, so apps don't have to maintain a relayer treasury. Tab's integration is scoped against the public testnet; mainnet deploy ships alongside Tempo's launch.
Why merchants pick Tab on Tempo
Gas is invisible
Tempo's protocol-layer gas sponsorship means the buyer never sees a gas token. Tab doesn't need to top up a relayer with the chain's native asset.
Stablecoin-native settlement
αUSD is the L1's reference asset, not an ERC-20 wrapper. Transfers settle as raw protocol ops, not through a token contract.
Same Tab surface
Dashboards, OpenTab, subscriptions, TabBot, all light up the moment the mainnet deploy lands. No new UX to learn.
Drop into the Tempo integration in a day.
Same EIP-712 signature, same router contract, same REST API you already use on every other chain. The only thing that changes is the chain id and the stablecoin address.
- Chain id
- 0
- Stablecoin
- αUSD
- Token contract
- —
- Public RPC
- —
- Explorer
- —
Technical notes
Status
Public mainnet pending. Tab's EVM-compatible router compiles cleanly against Tempo's EVM layer; the integration work is in adapting the gas-sponsorship paymaster path.
Indexer
Standard JSON-RPC + event log path. No special-casing required for the Tempo indexer.
Updates
Subscribe to /docs/resources/changelog for deploy notes once mainnet ships.
Ship your first Tempo payment today.
Claim a handle, hand out a link, take αUSD. Then read the contracts and decide for yourself whether to trust us.