Skip to main content

What Is TIP-20? Tempo's Token Standard Explained

TIP-20 is Tempo's native token standard for stablecoins and payment tokens. Here is what it adds to ERC-20: memos, a currency field, quote tokens, fee payment, and issuer controls.

Written by Eco
What Is TIP-20? Tempo's Token Standard Explained

TIP-20 is the native token standard on Tempo, the payments-focused Layer 1 blockchain. Tempo describes TIP-20 tokens as its standard for stablecoins and payment tokens, and the foundation for transaction fees, payment lanes, DEX quote tokens, and routing on the Stablecoin DEX (Tempo Docs, TIP-20 tokens). Every TIP-20 token is created through a single factory contract by calling createToken.
​

TIP-20 keeps the familiar ERC-20 functions for balances, allowances, and transfers, then adds payment features at the protocol level (TIP-20 specification). This article covers what those features are, how the currency and quote token fields work, how TIP-20 tokens pay gas, and where the standard departs from ERC-20 in Tempo's own documentation.
​

What is TIP-20 on Tempo?

TIP-20 is Tempo's stablecoin-native token standard. It extends ERC-20 with built-in memo fields, transfer policies, a declared currency, and a quote token for the native DEX. Tempo strongly recommends that anyone issuing a stablecoin on Tempo use TIP-20 rather than a custom contract (Tempo Docs).
​

The overview page lists the protocol functions TIP-20 underpins: transaction fees, payment lanes, DEX quote tokens, optimized routing for DEX liquidity, optional onchain logoURI metadata, implicit approvals for listed precompiles, and enshrined payment-channel reserve flows (Tempo Docs, TIP-20 tokens). The specification states that TIP-20 tokens "extend the ERC-20 token standard with built-in functionality like memo fields and transfer policies" (TIP-20 specification).
​

All TIP-20 tokens come from the TIP20Factory contract. The factory's createToken function takes six arguments: name, symbol, currency, quoteToken, admin, and salt. The admin address receives DEFAULT_ADMIN_ROLE on the new token (TIP-20 specification).
​

What features does TIP-20 add for payments?

TIP-20 adds three payment features: fee payment in the token itself, reserved blockspace through payment lanes, and 32-byte transfer memos. Only TIP-20 tokens can pay transaction fees on Tempo, and payment TIP-20 transactions get blockspace that other applications cannot consume (Tempo Docs).
​

Transfer memos

Transfer memos let a sender attach a 32-byte memo to a transfer for payment references, invoice IDs, or transaction notes (Tempo Docs, TIP-20 tokens). The specification exposes this through transferWithMemo, which "transfers tokens from caller to recipient with a memo" (TIP-20 specification). For a business reconciling incoming payments, the memo carries the reference that would otherwise live in a separate database.
​

Payment lanes

Tempo describes payment lanes as reserved blockspace for payment TIP-20 transactions. According to the docs, even when popular applications compete for blockspace, payroll runs or customer disbursements still execute predictably (Tempo Docs, TIP-20 tokens).
​

Paying fees in a stablecoin

Tempo says only TIP-20 tokens can be used to pay transaction fees on the network. A user pays with a USD-denominated TIP-20; if it differs from the validator's preferred token, the Fee AMM needs enough liquidity to convert the fee, and the account does not need a separate native gas token (Tempo Docs, TIP-20 tokens). The selection order and conversion rules are set out in the Tempo fee specification. Eco's explainer on pathUSD, Tempo's fee stablecoin walks through the fallback token.
​

What is the TIP-20 currency field?

The currency field names the reference asset that one unit of the token is designed to be worth. It is not the token's name or its pricing denomination. Tempo uses it for routing and pricing on the Stablecoin DEX, and currently only USD-denominated stablecoins can pay fees or trade on that DEX.
​

Tempo's guidelines say a token tracking an asset with an ISO 4217 code should use that code, such as "USD", "EUR", or "XAU" for gold. A token tracking a non-ISO asset at 1:1 uses the reference asset's symbol, so bridged WBTC uses "BTC". A token priced in a currency but not pegged to it should not use that currency's code, and a token with no reference asset uses its own symbol (Tempo Docs, TIP-20 tokens). The specification adds that currency is immutable after creation (TIP-20 specification).
​

The docs frame the test this way: the field determines what a token would trade against on a DEX built for assets that trade within 2% of a 1:1 price (Tempo Docs, TIP-20 tokens). Tempo's own examples, reproduced below, show how common assets map (Tempo Docs, TIP-20 tokens).
​

Token

Tracks

currency

USDC

US Dollar

USD

USDT

US Dollar

USD

EURC

Euro

EUR

Bridged WBTC

Bitcoin

BTC

Bridged stETH

Ether

ETH

Tokenized gold (priced in USD)

Gold

XAU

Governance token (e.g. UNI)

Itself

UNI

What is a TIP-20 quote token?

Each TIP-20 has a quoteToken used for pricing and routing on Tempo's Stablecoin DEX. Tokens whose currency is USD must pair with a USD-denominated TIP-20. The quote token is set at creation and can later be changed through a two-step staged update (TIP-20 specification).
​

The specification names setNextQuoteToken to stage a new quote token and completeQuoteTokenUpdate to finalize it (TIP-20 specification). The overview gives an example of a USDG TIP-20 paired with other stablecoins so traders can swap between USD tokens through resting orders on the DEX orderbook, subject to available liquidity and slippage limits (Tempo Docs, TIP-20 tokens). pathUSD sits at the root of this tree as the default USD quote token; see Eco's pathUSD explainer for how routing works.
​

What compliance controls does TIP-20 include?

TIP-20 ships with role-based access control, transfer policies through the Tempo Policy Registry (TIP-403), supply caps, and pause controls. Issuers can grant, revoke, and delegate roles without changing contract code, which separates who can mint from who can pause (Tempo Docs).
​

The roles Tempo lists are ISSUER_ROLE for minting and burning, PAUSE_ROLE and UNPAUSE_ROLE for halting transfers, and BURN_BLOCKED_ROLE for burning tokens from blocked addresses in compliance actions (Tempo Docs, TIP-20 tokens). Each token can reference a TIP-403 policy, either a whitelist or a blacklist, and one policy can be shared across multiple tokens (Tempo Docs, TIP-20 tokens). Supply caps set a maximum token supply (Tempo Docs, TIP-20 tokens).
​

How is TIP-20 different from ERC-20?

TIP-20 exposes standard ERC-20 functions, but Tempo lists several departures: fixed 6 decimals, deterministic factory addresses, no burnFrom, no proxy upgrades, and a reversed hasRole argument order. Tempo's migration guide advises against porting custom ERC-20 methods into a TIP-20 token (Tempo migration guide).
​

The migration guide notes that OpenZeppelin ERC-20 tokens commonly use 18 decimals, while TIP-20 uses 6 (Tempo Docs, Migrate from ERC-20); the specification confirms decimals always return 6 (TIP-20 specification). Token addresses are derived from the factory caller and a salt and use the 12-byte prefix 20C00000000000000000000000; if the address is already occupied, creation reverts rather than overwriting the token (TIP-20 specification).
​

Other differences from the migration guide: TIP-20 does not expose burnFrom, so burns are limited to the holder's own balance; proxy upgrade patterns are not portable; TIP20Factory.createToken does not accept a policy ID; and TIP-20's hasRole takes the account first, hasRole(account, role), unlike OpenZeppelin (Tempo Docs, Migrate from ERC-20). The guide's summary line is that "TIP-20 is native" (Tempo Docs, Migrate from ERC-20).
​

Area

Typical ERC-20 (OpenZeppelin)

TIP-20

Source

Decimals

Commonly 18

Fixed at 6

Deployment

Custom contract

TIP20Factory createToken

Memos

Not in standard

32-byte memo via transferWithMemo

burnFrom

Common extension

Not exposed

Upgrades

Proxy patterns

Not portable

Fee payment

Not applicable

USD TIP-20s can pay gas

Frequently asked questions

These answers restate points from Tempo's TIP-20 overview, specification, and migration guide. They cover the questions developers and issuers most often raise before creating or integrating a TIP-20 token, drawing on the TIP-20 specification.
​

Can any TIP-20 token pay gas on Tempo?

No. Currently only USD-denominated stablecoins can pay transaction fees (Tempo Docs, TIP-20 tokens).
​

Does a TIP-20 token need a logo onchain?

No. Every TIP-20 exposes an optional logoURI, and tokens without one continue to work (TIP-20 specification).
​

Can the currency field be changed later?

No. The specification marks currency as immutable after creation (TIP-20 specification).
​

Does Tempo have a native gas token for TIP-20 transfers?

No. Fees are paid in TIP-20 stablecoins; see Eco's guide on whether Tempo has a token.
​

Methodology and sources

This explainer was written on November 19, 2026 from Tempo's published documentation only, primarily the TIP-20 specification. It makes no safety or investment judgment on any token, and protocol details can change with network upgrades.

Related reading

For more on the Tempo network, start with the hub and its sibling explainers. Each links back to Tempo's own documentation for primary detail.

Did this answer your question?