Every Tempo feature in this section is in beta and available through the API only. To get access, contact your Customer Success Manager (CSM).
Before you start
- Tempo has no native gas token. Every fee is paid in a USD-denominated TIP-20 stablecoin. The Tempo base asset in your workspace, such as
TEMPO_MODERATO_TESTon the Moderato testnet, is a placeholder and holds no value. - TIP-20 and ERC-20 tokens are both supported. You can list and transfer any TIP-20 or ERC-20 token contract on Tempo. Some features work with TIP-20 tokens only: paying fees, memos, fee sponsorship and virtual-address forwarding.
Tempo transactions
Fireblocks sends Tempo transfers as Tempo Transactions, the EIP-2718 type0x76 envelope. This envelope carries the fields that make each Tempo feature possible: fee_token, fee_payer_signature, nonce_key, nonce and valid_before. Fireblocks builds the envelope, signs it with MPC and broadcasts it. You never handle the raw envelope.
Two ways to create a Tempo transfer
Both endpoints create a regular Fireblocks transaction, with the same Policy Engine rules, statuses and webhooks as any other transfer. Set a unique
externalTxId on every request so a retry can’t create a second transfer. See Transaction idempotency.
POST /v1/operations/tempo/transfer
How fees appear on the transaction
- Network records. A Fireblocks transaction can move funds more than once on-chain. Each movement is a network record, listed in the
networkRecordsarray of the transaction object (GET /v1/transactions/{txId}). Each record has its ownassetId,source,destination,netAmount,networkFeeandtxHash. See the NetworkRecord object. A regular Tempo transfer always has at least two records. The payment record is the amount delivered to the destination. The fee record is the fee charged, and itsassetIdis the token that paid it. - Fee currency.
feeCurrencyon the transaction is the asset that paid the fee. The fee token you asked for is kept inrequestedFeeCurrency. - Fee payer. On a sponsored transaction,
feePayerInfo.feePayerAccountIdnames the vault account that paid.
Limits
- Use
feeLevel, not custom gas values. Custom per-gas fees (maxFeePerGas,maxPriorityFeePerGas) aren’t supported on Tempo during the beta. SetfeeLeveltoLOW,MEDIUMorHIGHinstead. - Transfers only. Contract calls still go out as standard EVM (type
0x2) transactions and don’t get the Tempo features in this section.