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
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.

