Unlike standard EVM transactions, Tempo transactions use a
calls array instead of a single
to/data/value. This enables multiple contract calls to execute atomically in one
transaction. View the Tempo transaction
recipe for full examples.Parameters
118
required
Transaction type for Tempo’s native envelope.
number
required
The Tempo chain ID. Use
4217 for mainnet or 42431 for Moderato (testnet).TempoCall[]
required
An array of calls to execute atomically. At least one call is required. Each call has
to
(required), data, and value.Hex
Address of the supported TIP-20 token used to pay Tempo fees. If omitted, Tempo’s fee-token
preference rules apply. Tempo has no
native gas token.
bigint
2D nonce key. Use
0 for the protocol-managed sequential nonce, or a non-zero value to use a
parallel user nonce slot, enabling concurrent transactions.bigint
Sequential nonce within the nonce key slot. Populated automatically if omitted.
bigint
Transaction expiration as a Unix timestamp in seconds. The transaction will not be included after
this time.
bigint
Earliest inclusion time as a Unix timestamp in seconds. The transaction will not be included
before this time.
bigint
Gas limit for the transaction. Estimated automatically if omitted.
bigint
Maximum total fee per gas unit in wei. Estimated automatically if omitted.
bigint
Maximum priority fee per gas unit in wei. Estimated automatically if omitted.
ConnectedWallet
required
The wallet to sign the transaction with.
Returns
HexString
The signed transaction, ready to broadcast.

