There are two ways to hold stablecoins on Tempo. You can sign in to Tempo Wallet, the first-party wallet at wallet.tempo.xyz, or you can add Tempo Mainnet as a custom network in an EVM wallet you already use, such as MetaMask or Rabby. The manual route takes five fields: network name, RPC URL, chain ID 4217, currency symbol USD, and the explorer URL (Tempo Docs, Add Tempo to MetaMask).
This guide covers both routes, the settings for mainnet and the Moderato testnet, what to expect from balances and fees once you connect, and which wallet providers Tempo's partner directory lists. For background on the chain itself, start with What Is Tempo Blockchain?
What is Tempo Wallet?
Tempo Wallet is Tempo's own wallet for holding and moving funds on the network. Its site describes it as a first-party wallet for balances, transfers, deposits, private balances, and account control. You sign in with a passkey (Tempo Wallet).
The Tempo Wallet homepage lists four core actions: Send, to move funds on Tempo; Receive, to share your wallet address; Deposit, to add funds with supported rails; and Zones, to manage private balances on Tempo. It states the wallet is built for Tempo "with passkey sign-in and account controls in one place" (Tempo Wallet).
Passkey accounts differ from a browser wallet holding a single private key. Tempo's wallet documentation recommends a passkey or device key for new accounts, and notes that on a single-key account, losing the key loses the account (Tempo Docs, Wallets). Apps can also sign users in with an existing Tempo Account through the Accounts SDK, where Tempo holds the account's keys and the app receives an access key that signs within limits the user approves (Tempo Docs, Wallets).
How do I add Tempo to MetaMask?
Open MetaMask's network menu, choose Add a custom network, and enter the Tempo Mainnet details from the table below. Save the network and switch to it. Tempo's docs page also offers a one-click option: connect your browser wallet on the page and approve the network request (Tempo Docs, Add Tempo to MetaMask).
Tempo's guide says the manual setup works for MetaMask or any EVM wallet "in under a minute." In Rabby or another wallet, you add a custom network from that wallet's settings instead of a network menu (Tempo Docs, Add Tempo to MetaMask). The steps, in order:
Open the network settings. In MetaMask, open the network menu and select Add a custom network.
Enter the network details: name, RPC URL, chain ID, currency symbol, and block explorer URL.
Save the network and switch to it.
Import each stablecoin you hold by its token address so the balance shows up.
Your address does not change. Tempo's guide states that your wallet's address is the same on Tempo as on Ethereum, so funds sent to your existing EVM address on Tempo arrive at the account you already control (Tempo Docs, Add Tempo to MetaMask).
What are the Tempo network settings?
Tempo Mainnet uses chain ID 4217, the RPC URL https://rpc.tempo.xyz, the currency symbol USD, and the explorer at explore.tempo.xyz. The Moderato testnet uses chain ID 42431 with its own RPC and explorer. Both networks support standard EVM tools, but testnet funds are separate from mainnet funds (Tempo Docs, Network details).
The values below come from Tempo's network details page (Tempo Docs, Network details) and match the MetaMask setup guide (Tempo Docs, Add Tempo to MetaMask). Copy them exactly; a mistyped RPC URL or chain ID is the usual reason a custom network fails to save.
Field | Tempo Mainnet | Tempo Testnet (Moderato) |
|---|---|---|
Network name | Tempo Mainnet | Tempo Testnet (Moderato) |
Chain ID | 4217 | 42431 |
Currency symbol | USD | USD |
HTTP RPC | ||
WebSocket RPC | wss://rpc.tempo.xyz | wss://rpc.moderato.tempo.xyz |
Block explorer |
Testnet stablecoins come from Tempo's faucet, and Tempo notes that testnet funds are separate from mainnet funds (Tempo Docs, Network details). For upgrade history and launch details, see Tempo Mainnet Launch Date, Chain ID, RPC and Upgrades.
Why does my wallet show a large USD balance on Tempo?
That number is a placeholder, not money. Tempo has no native token, so the native balance an EVM wallet displays for the network carries no value. Tempo's guide tells users to ignore the large USD figure and import each stablecoin they hold by its contract address instead (Tempo Docs, Add Tempo to MetaMask).
The guide points to Tempo's token list as the place to find stablecoin addresses, naming OUSD and USDC.e as examples (Tempo Docs, Add Tempo to MetaMask). Tempo's wallet integration guide makes the same point from the wallet builder's side: wallets should check a user's fee token balance rather than calling eth_getBalance, and should not display any native balance for Tempo users (Tempo Docs, Wallet integration).
If a stablecoin still does not appear after you import it, confirm you are on chain ID 4217 and not the testnet. Addresses can match across networks while balances do not (Tempo Docs, Network details).
How do fees work in a Tempo wallet?
You pay network fees in a stablecoin, not ETH. Tempo's guide says you do not need ETH or any other token. By default, a transfer pays its fee in the stablecoin it sends, and most other transactions fall back to pathUSD (Tempo Docs, Add Tempo to MetaMask).
That default comes from Tempo's MetaMask guide (Tempo Docs, Add Tempo to MetaMask) and is repeated on the wallets page, which says the wallet pays each fee in a stablecoin (Tempo Docs, Wallets). The fallback token is covered in What Is pathUSD? Tempo's Fee Stablecoin Explained, and questions about a native coin or airdrop are covered in Does Tempo Have a Token?
Wallets that integrate Tempo natively can offer more control. Tempo asks wallet teams to let users choose which stablecoin pays fees, through a dropdown at confirmation or an account setting, and to display USD as the gas currency symbol (Tempo Docs, Wallet integration).
What is the difference between a browser wallet and Tempo Transactions?
A browser wallet like MetaMask sends standard Ethereum transactions signed by one private key. Tempo Transactions are Tempo's own transaction type, which add fee sponsorship, batched calls, and passkey or device-key signing. Both work on Tempo, but the feature set differs (Tempo Docs, Wallets).
Tempo's wallets page compares the two side by side (Tempo Docs, Wallets):
Signers: a browser wallet uses one private key; Tempo Transactions support passkeys, device keys, or private keys, with several per configurable account.
Network fees: paid by the user in a browser wallet; can be sponsored by an app with Tempo Transactions.
Multiple calls: one call per transaction in a browser wallet; several calls that succeed or fail together with Tempo Transactions.
Lost keys: losing a browser wallet key loses the account; on a configurable account, another signer can replace it.
The integration guide describes Tempo Transactions as a protocol-native EIP-2718 transaction type with type byte 0x76 that provides these features without a bundler or paymaster (Tempo Docs, Wallet integration). Hardware wallets also hold one private key, so Tempo treats their accounts as single-key accounts with the same limits (Tempo Docs, Wallets).
Which wallets support Tempo?
Tempo's partner directory groups wallet providers into four types: embedded, custodial and institutional, self-custodial, and agentic. Some self-custodial apps, including Gem Wallet and OKX Wallet, support Tempo already, so no manual network setup is needed. Others, such as MetaMask and Rabby, work through the custom network steps above (Tempo Docs, Wallets partners; Add Tempo to MetaMask).
The listings below summarize Tempo's Wallets partner page. Inclusion in Tempo's directory is a listing, not a review; check each provider's own documentation for current Tempo features.
Self-custodial wallets
Tempo lists Bitget Wallet, Mt Pelerin's Bridge Wallet, Gem Wallet, OKX Wallet, Rabby, and Safe. It describes Gem Wallet as an open-source mobile wallet for iOS and Android with native Tempo support, and OKX Wallet as a multi-chain wallet with native Tempo support (Tempo Docs, Wallets). The MetaMask guide adds that Tempo works with EVM wallets such as MetaMask, Rabby, and Ledger (Tempo Docs, Add Tempo to MetaMask).
Safe for shared accounts
For accounts with several owners, Tempo points to Safe smart accounts. Tempo's smart accounts page says Safe provides contract accounts with multiple owners and signature thresholds, and that Safe's transaction service documents support for Tempo and the Moderato testnet (Tempo Docs, Smart accounts).
Embedded wallets for apps
App builders can embed wallets through Blockradar, Crossmint, Dynamic, Para, Privy, or Turnkey. Tempo's page notes that Para's Tempo announcement covers testnet and that generic EVM signing does not give batching or fee sponsorship, while Privy's Tempo integration supports batched calls and fee-token selection (Tempo Docs, Wallets).
Custody and agent wallets
Institutional options listed include Bridge Wallets, BitGo, Coinbase Prime, Cubist CubeSigner, DFNS, Fireblocks, and Utila. Tempo also states that Coinbase supports Tempo for retail transfers in its iOS and Android apps, where customers can select Tempo as the network when sending or receiving supported assets. For AI agents, Tempo lists Enact and Sponge (Tempo Docs, Wallets).
Frequently asked questions
These short answers restate Tempo's own documentation on wallets and network setup.
What is Tempo's chain ID?
Tempo Mainnet is chain ID 4217. The Moderato testnet is 42431 (Tempo Docs, Network details).
Do I need ETH to use Tempo?
No. Fees are paid in stablecoins, and Tempo's guide says you do not need ETH or any other token (Tempo Docs, Add Tempo to MetaMask).
Is my Tempo address different from my Ethereum address?
No. An EVM wallet uses the same address on Tempo as on Ethereum (Tempo Docs, Add Tempo to MetaMask).
Can I use a Ledger with Tempo?
Tempo's docs name Ledger among compatible EVM wallets. A hardware wallet account is a single-key account, so it has the same limits as a browser wallet (Tempo Docs, Wallets).

