Tempo Protocol supports two distinct transaction types: Tempo Transactions (typeDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/tempoxyz/tempo/llms.txt
Use this file to discover all available pages before exploring further.
0x76) and Standard EVM Transactions. Each type serves different use cases and has unique characteristics.
Transaction Types
Tempo Transaction (Type 0x76)
Tempo Transactions are Tempo’s native transaction format, designed for high-throughput payment systems and modern account abstraction features. Key Features:- Multiple signature types (secp256k1, P256, WebAuthn)
- Batch execution (multiple calls in a single transaction)
- 2D nonce system for parallel transaction submission
- Expiring nonces for time-based replay protection
- Gas sponsorship via fee payer signatures
- Optional fee token preference
- EIP-7702 delegation support with Tempo signatures
- Key authorization for adding access keys
- Payment applications requiring high throughput
- Gasless transactions and meta-transactions
- Smart contract wallets and account abstraction
- Applications needing WebAuthn or passkey support
- Batch operations (multiple transfers, state updates)
Standard EVM Transactions
Tempo supports all standard Ethereum transaction types for compatibility with existing tools and wallets. Supported Types:- Legacy (Type 0x00): Original Ethereum transactions with
gasPrice - EIP-2930 (Type 0x01): Access list transactions
- EIP-1559 (Type 0x02): Dynamic fee transactions with
maxFeePerGasandmaxPriorityFeePerGas - EIP-7702 (Type 0x04): Set Code transactions for account delegation
- Existing wallet compatibility (MetaMask, hardware wallets)
- Standard Ethereum contracts and dApps
- Tools expecting standard EVM transaction formats
When to Use Each Type
Use Tempo Transactions When:
- High throughput: Processing payments or transactions at scale
- Parallel execution: Submitting multiple independent transactions simultaneously
- Gasless UX: Implementing gas sponsorship or meta-transactions
- Alternative signatures: Using WebAuthn, passkeys, or P256 keys
- Batch operations: Executing multiple calls atomically
- Flexible nonces: Using expiring nonces or 2D nonces for better UX
Use EVM Transactions When:
- Wallet compatibility: Using existing wallets (MetaMask, Ledger, etc.)
- Standard tooling: Working with standard Ethereum development tools
- Simple transfers: Standard ETH or token transfers
- Existing contracts: Interacting with contracts expecting standard EVM txs
Transaction Structure Comparison
| Feature | Tempo Transaction | EVM Transaction |
|---|---|---|
| Type ID | 0x76 | 0x00, 0x01, 0x02, 0x04 |
| Signatures | secp256k1, P256, WebAuthn | secp256k1 only |
| Calls per Transaction | Multiple (batch) | Single |
| Nonce System | 2D nonces + expiring nonces | Sequential only |
| Gas Sponsorship | Built-in via fee payer | Not supported |
| Fee Token | Optional preference | Native token only |
| Access Lists | Supported (EIP-2930) | Supported (EIP-2930+) |
| Authorization Lists | Tempo-style (EIP-7702 adapted) | Standard EIP-7702 |
Gas Considerations
Tempo Transactions
- Base cost: Standard EIP-1559 dynamic fees
- Expiring nonce cost: ~13,000 gas for time-based replay protection
- Batch optimization: Multiple calls share base transaction overhead
- Fee token: Optional TIP-20 token for fee payment
EVM Transactions
- Standard costs: Standard Ethereum gas pricing
- No batch support: Each operation requires a separate transaction
- Sequential nonces: Must manage nonce ordering carefully