Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Anchorage opens Tempo custody with a pathUSD funding requirement

The integration gives institutions a custody route for payment-chain assets, while the network’s broader fee flexibility and Anchorage’s current implementation require different funding decisions.

Anchorage Digital Bank, N.A. added Tempo custody on 15 October 2026, making four assets available to institutional clients: OUSD, USDT0, USDC.e and pathUSD. Support includes address creation, deposits and withdrawals through the bank’s segregated custody accounts and policy controls.[1]

The platform currently requires pathUSD for transaction fees. Additional fee assets may follow; general TIP-20 support is planned to shorten future token integrations.[1]

The platform’s fee choice is narrower than the network’s

Tempo has no native gas token. Its protocol accepts USD-denominated native TIP-20 stablecoins with sufficient liquidity in the Fee AMM. A transaction can select a fee token, and an account can set a default. That network capability does not mean a particular custodian has enabled every eligible asset.[2]

The distinction matters for treasury operations: a large payment balance and a usable fee balance are separate requirements. A process that funds only the payment asset can still leave an instruction unable to proceed through a platform whose fee token is different.[1]

The token name identifies a particular route

At a glance01

Roles in Tempo’s documentation

Roles in Tempo’s documentation
AssetDocumented role
OUSDIssued directly on Tempo; integration partners provide USD minting and redemptionSource 4
USDC.eUSDC bridged through Stargate; can be swapped into OUSDSource 4
pathUSDBridge-issued quote and fallback fee token; minted with USDC.e and redeemed to USDC through BridgeSource 3

Tempo’s OUSD guide describes swaps as requiring liquidity and compatible transfer policies. It also explains that choosing a fee token changes what pays for the transaction; it does not convert the payment amount. A treasury team therefore needs to distinguish the asset delivered to its recipient from the asset spent on execution.[4]

The pathUSD documentation distinguishes production balances from faucet tokens on Tempo’s test network, even though the contract address is the same. Network identity is therefore part of asset verification: matching a ticker and address alone does not establish that an incoming balance is production money.[3]

Gas economics should be kept separate from custody pricing

Tempo specifies a dynamic base fee for a 50,000-gas transfer of about US$0.00003 at the floor and US$0.0006 at the cap. For 10,000 such transfers, those endpoints imply approximately US$0.30–US$6 in base fees. This illustration excludes priority fees, different gas use and Anchorage service charges.[2]

At that scale, a treasury implementation can be more constrained by approvals, correct asset selection and timely fee replenishment than by the illustrated base-gas amount. The custody addition addresses institutional access; operating the payment process still requires those balances and controls to be configured coherently.

Follow the evidence

Sources & further reading

  1. Tempo custody support Anchorage Digital · 15 Oct 2026 · Accessed 21 Oct 2026
  2. Transaction fee mechanics Tempo · Accessed 21 Oct 2026
  3. pathUSD on mainnet and quote tokens Tempo · Accessed 21 Oct 2026
  4. OUSD and the Tempo stablecoin routes Tempo · Accessed 21 Oct 2026

Report an error or submit an update