- Configurable fee tokens: set
feeTokento pay fees with a supported TIP-20 token. Learn more - Fee sponsorship: set
sponsor: trueto use Privy gas sponsorship on Tempo - Concurrent transactions: set
nonceKeyto send parallel transactions. Most apps can omit this since Privy uses expiring nonces by default - Batched calls: batch multiple calls in the transaction’s
callsarray - Scheduled transactions: set
validBeforeorvalidAfterto control when the network can include the transaction
Unlike standard EVM transactions, Tempo transactions use a
calls array instead of top-level to
and data fields. This enables multiple contract calls to execute atomically in one transaction.Parameters
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.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.
Optional parameter to enable gas sponsorship for this Tempo transaction. Learn
more.
Returns
tempoActions integration, view the Tempo transaction
recipe.
