Skip to main content

What Is pathUSD? Tempo's Fee Stablecoin Explained

pathUSD is the Bridge-issued USD stablecoin that serves as Tempo's fallback fee token and root quote token on its Stablecoin DEX. Here is what it does and how it works.

Written by Eco
What Is pathUSD? Tempo's Fee Stablecoin Explained

pathUSD is a US dollar stablecoin issued by Bridge on Tempo, the payments-focused Layer 1 blockchain. It is the first stablecoin deployed to the chain, created at the mainnet genesis block on January 16, 2026 (Tempo network upgrades) ahead of the March 18, 2026 public launch (Tempo blog), the root quote token on Tempo's Stablecoin DEX, and the fallback token the protocol uses for gas when no other fee token is specified (Tempo Docs).
​

Most people who use Tempo never hold pathUSD directly. Tempo describes it as routing infrastructure rather than a consumer stablecoin, and recommends OUSD for balances and payments (Tempo Docs). This article covers who issues pathUSD, what backs it, how fees fall back to it, and why it sits at the center of Tempo's DEX.
​

What is pathUSD on Tempo?

pathUSD is a USD-denominated TIP-20 token predeployed at Tempo's genesis. It has two protocol jobs: it is the default quote token that other USD stablecoins can pair against on the native DEX, and it is the fee token the protocol falls back to when a user, account, contract, or validator sets no preference of its own.
​

The token lives at the predeploy address 0x20c0000000000000000000000000000000000000 on Tempo Mainnet (chain ID 4217), with the name and symbol "pathUSD", currency "USD", and 6 decimals (Tempo Docs, pathUSD contract). Because it was the first TIP-20 deployed, its own quote token is the zero address (Tempo Docs).
​

Tempo's partner listing summarizes the asset in one line: a US dollar stablecoin issued by Bridge (Tempo partners, pathUSD). A faucet-issued test version exists on Tempo Testnet (Moderato, chain ID 42431) at the same address, but testnet balances have no relationship to mainnet pathUSD and are not interchangeable (Tempo Docs, Testnet pathUSD).
​

Who issues pathUSD and what backs it?

Bridge issues pathUSD, and Tempo's documentation states the token is backed one-to-one by high-quality USD-denominated reserves. Users mint pathUSD by depositing USDC.e and redeem it back to USDC through Bridge. Tempo points readers to Bridge's own site for details on how those reserves are allocated.
​

The issuance and backing language comes from the "Issuance & Backing" section of Tempo's quote token documentation, which names Bridge as issuer and links to Bridge for reserve allocation practices (Tempo Docs, Issuance & Backing). The same section describes the mint and redeem path: deposit USDC.e to mint, redeem back to USDC through Bridge.
​

Tempo's partner page also lists a route for getting pathUSD by swapping from OUSD on Tempo, plus an on-ramp option through Bridge (Tempo partners, pathUSD). This article does not assess reserve quality or issuer risk; readers should review Bridge's disclosures directly.
​

How does pathUSD work as Tempo's fallback fee token?

Tempo charges gas in USD stablecoins and picks the fee token by checking preferences in order: transaction, account, TIP-20 contract, then Stablecoin DEX call. If none of those levels sets a token, the protocol falls back to pathUSD. Validators without a stated preference also default to receiving pathUSD.
​

Tempo's fee specification says users can pay gas in any TIP-20 token whose currency is USD, provided it has enough liquidity on the enshrined Fee AMM against the validator's preferred token (Tempo fee specification). The lookup walks a fixed hierarchy and stops at the first level that names a token:

  1. Transaction level: the fee_token field on a Tempo transaction.

  2. Account level: a preference set with setUserToken on the FeeManager precompile.

  3. TIP-20 contract: a transfer or transferWithMemo call uses that token.

  4. Stablecoin DEX: certain swap calls use the tokenIn argument.

  5. Fallback: pathUSD.

That order is quoted from the "fee token preferences" section of the spec (Tempo fee specification). On the validator side, the spec states that if validators have not specified a fee token preference, the protocol expects pathUSD as their fee token (Tempo fee specification, validator preferences).
​

What changed with the T13 upgrade

After the T13 network upgrade, which went live on mainnet on November 3, 2026 (Tempo network upgrades), the fallback became an ordered list: pathUSD first, then OUSD (0x20c0000000000000000000006a37da5c996874be). The protocol picks the first token in which the fee payer's balance covers the maximum fee. If neither covers it, the transaction is invalid, and a zero maximum fee selects pathUSD (Tempo fee specification, ordered fallback from T13).
​

How fees convert to the validator's token

When a user pays in one stablecoin and the validator prefers another, the Fee AMM converts the payment after the transaction executes. The spec sets a fixed rate of 0.9970 per hop, meaning a direct pool pays 0.9970 validator tokens per 1.0 user token before integer rounding, a 0.3% conversion cost per hop. If the user's token already matches the validator's preference, no conversion happens (Tempo fee specification, fee swap execution).
​

Why is pathUSD the quote token on the Stablecoin DEX?

Every USD TIP-20 on Tempo picks one other USD TIP-20 as its quote token, forming a tree. pathUSD sits at the root as an issuer-neutral option, so no single stablecoin issuer holds a privileged spot in Tempo's liquidity graph. The tree guarantees exactly one routing path between any two USD stablecoins.
​

Tempo's documentation says the design exists because Tempo aims to be neutral across stablecoin issuers, and pathUSD "provides a neutral option that any token can pair against" on the DEX (Tempo Docs, Why pathUSD?). The single-path tree is meant to reduce liquidity fragmentation and simplify routing, including for thinly traded pairs (Tempo Docs, Tree Structure).
​

Tempo gives a cross-stablecoin payment example. Market makers provide liquidity for USDX/pathUSD and OUSD/pathUSD. A user sends USDX to a merchant who settles in OUSD, and the DEX routes USDX to pathUSD to OUSD atomically in one transaction. Neither party holds pathUSD; it exists only as routing infrastructure (Tempo Docs, Example). OUSD itself lists pathUSD as its quoteToken (Tempo Docs, OUSD).
​

Using pathUSD is optional. Tokens can list any other USD TIP-20 as their quote token if they choose (Tempo Docs).
​

pathUSD vs OUSD vs USDC.e on Tempo

Tempo's own documentation separates the roles of its three most referenced USD tokens. pathUSD handles routing and fee fallback, OUSD is the recommended stablecoin for balances and payments, and USDC.e is the bridged asset used to mint pathUSD. The table below draws only on Tempo-published descriptions of each.
​

Token

Role on Tempo

Fee fallback position

Source

pathUSD

Root quote token on the Stablecoin DEX and the protocol's fallback fee token

First

OUSD

Recommended stablecoin for balances and payments; quote token is pathUSD

Second, from T13

USDC.e

Bridged USDC (by Stargate per Tempo's partner listing); deposited to mint pathUSD

Not in fallback list

Frequently asked questions

These answers restate points from Tempo's documentation on pathUSD, fees, and the Stablecoin DEX. They cover the questions that price-tracker pages for pathUSD typically leave out: whether users need to hold it, how it differs from testnet tokens, and whether it is meant to be a payments stablecoin.
​

Do I need pathUSD to use Tempo?

No. Users can pay fees in any USD TIP-20 with enough Fee AMM liquidity, and Tempo says most users never need to hold pathUSD directly (Tempo Docs, OUSD).
​

Is testnet pathUSD the same as mainnet pathUSD?

No. They share an address but live on separate networks and are not interchangeable (Tempo Docs).
​

Is pathUSD a consumer stablecoin?

Tempo says pathUSD "is not meant to compete as a consumer-facing stablecoin" and recommends OUSD for that role (Tempo Docs).
​

Can validators accept pathUSD as fees?

Yes. Validators can accept pathUSD as a fee token, and it is the default when they set no preference (Tempo fee specification).
​

Methodology and sources

This explainer was written on November 18, 2026 from Tempo's published documentation and partner pages only. It includes no price, supply, or market data, makes no safety or investment judgment, and does not describe any Eco integration with Tempo. Protocol details can change with network upgrades.

Related reading

For more on the Tempo network, start with the Tempo hub and its sibling explainers on the network's token and mainnet launch. Eco publishes these as neutral, sourced guides to stablecoin infrastructure across chains. Each article below links back to Tempo's own documentation for primary detail.

Did this answer your question?