Wallet Developer Guide

Tempo is EVM-compatible, so standard transactions work out of the box. However, Tempo has no native gas token, which means wallet behaviors like balance display and gas quoting need adjustment.

To deliver the best experience for your users, integrate Tempo Transactions — a protocol-native EIP-2718 transaction type (type byte 0x76) that provides fee token selection, fee sponsorship, call batching, concurrent nonces, passkey signing, and scheduled execution — without requiring a bundler, paymaster, or third-party vendor.

SDKs are available for TypeScript, Rust, Go, Python, and Foundry. Integration typically takes less than an hour.

Wallet integration steps

import { client } from './viem.config'
import { parseUnits } from 'viem'
 
// Sends a Tempo Transaction (type 0x76)
const { receipt } = await client.token.transferSync({
  amount: parseUnits('100', 6),
  to: '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEbb',
  token: '0x20c0000000000000000000000000000000000001',
})

import { privateKeyToAccount } from 'viem/accounts'
import { createClient } from 'viem/tempo'
 
export const client = createClient({
  account: privateKeyToAccount('0x...'),
})

import { client } from './viem.config'
 
const userFeeToken = await client.fee.getUserToken({
  account: '0x...'
})
 
const balance = await client.token.getBalance({
  account: '0x...',
  token: userFeeToken.address
})

import { privateKeyToAccount } from 'viem/accounts'
import { createClient } from 'viem/tempo'
 
export const client = createClient({
  account: privateKeyToAccount('0x...'),
})

import { client } from './viem.config'
import { parseUnits } from 'viem'
 
const { receipt } = await client.token.transferSync({
  amount: parseUnits('100', 6),
  feeToken: '0x20c0000000000000000000000000000000000002', 
  to: '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEbb',
  token: '0x20c0000000000000000000000000000000000001',
})

import { privateKeyToAccount } from 'viem/accounts'
import { createClient } from 'viem/tempo'
 
export const client = createClient({
  account: privateKeyToAccount('0x...'),
})

await client.fee.setUserTokenSync({
  token: '0x20c0000000000000000000000000000000000001',
})

Already using EIP-7702 or EIP-4337?

If you've integrated a third-party account abstraction provider for batching, sponsorship, or smart accounts, Tempo Transactions provide these features natively at the protocol level. See the feature comparison for details.

Wallet integration recipes

Get user's fee token

Retrieve the user's configured fee token preference:

import { getUserToken } from 'viem/tempo'
 
const feeToken = await client.fee.getUserToken({
  account: userAddress
})

See getUserToken for full documentation.

Get token balance

Check a user's balance for a specific token:

import { getBalance } from 'viem/tempo'
 
const balance = await client.token.getBalance({
  account: userAddress,
  token: tokenAddress
})

See getBalance for full documentation.

Set user fee token

Set the user's default fee token preference. This will be used for all transactions unless a different fee token is specified at the transaction level.

import { setUserToken } from 'viem/tempo'
 
await client.fee.setUserTokenSync({
  token: '0x20c0000000000000000000000000000000000001',
})

See setUserToken for full documentation.

Checklist

Before launching Tempo support, ensure your wallet:

• Integrates Tempo Transactions for transaction submission
• Checks fee token balance instead of native balance
• Hides or removes native balance display for Tempo
• Displays USD as the currency symbol for gas
• Quotes gas prices in the user's fee token
• Provides fee token selection in the UI (dropdown or account setting)
• Pulls token/network assets from Tempo's tokenlist
• (Recommended) Sponsors fees for your users via fee sponsorship
• (Recommended) Uses expiring nonces for lower-cost transactions that don't require nonce management

Learning Resources