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.To pay Tempo fees with a token, set
feeToken to a supported TIP-20 token. View the Tempo
transaction recipe for
examples. To sponsor fees for a Tempo transaction, set sponsor: true in the transaction options.
Privy adds a Tempo fee payer signature before broadcasting the transaction. Learn
more.Parameters
Transaction type for Tempo’s native envelope.
The Tempo chain ID. Use
4217 for mainnet or 42431 for Moderato (testnet).An array of calls to execute atomically. At least one call is required. Each call has
to
(required), data, and value.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.
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.Sequential nonce within the nonce key slot. Populated automatically if omitted.
Transaction expiration as a Unix timestamp in seconds. The transaction will not be included after
this time.
Earliest inclusion time as a Unix timestamp in seconds. The transaction will not be included
before this time.
Gas limit for the transaction. Estimated automatically if omitted.
Maximum total fee per gas unit in wei. Estimated automatically if omitted.
Maximum priority fee per gas unit in wei. Estimated automatically if omitted.
The wallet to send the transaction from.
Optional parameter to enable gas sponsorship for this Tempo transaction. Learn
more.
Returns
The hash for the broadcasted transaction.
tempoActions integration, view the Tempo transaction
recipe.
