Every Tempo feature in this section is in beta and available through the API only. To get access, contact your Customer Success Manager (CSM).
How it works
A sponsored Tempo Transaction carries two signatures, one from each account, over two different payloads:- The sender signs the transfer with the fee token left blank. This lets the fee payer choose the token.
- The fee payer signs a separate payload that commits to the fee token and to the sender’s address. The signature can’t be reused to sponsor a different sender.
- Fireblocks combines both signatures into one transaction and broadcasts it. The chain charges the fee to the fee payer, in the fee token.
Set up the fee payer
Pick the vault account that will pay fees, and fund it with the stablecoin you’ll use for fees, such as PathUSD on Tempo.Rules
- The fee payer must be a vault account in the same workspace as the source.
- The fee payer must be a different vault account from the source. Fireblocks rejects the request with a 400 error: “A vault account cannot sponsor its own fee”.
- The fee payer pays in the transaction’s
feeCurrency. If you leavefeeCurrencyout, Tempo picks the fee token using its fee-token rules (see How Tempo chooses the fee token). Set it to control which token the fee payer spends. - Sponsorship works only for TIP-20 transfers. An ERC-20 transfer on Tempo always pays its own fee.
Create a sponsored transfer
AddfeePayerAccountId to a POST /v1/operations/tempo/transfer request.
feePayerAccountId on its own turns sponsorship on, so you don’t need useGasless. Don’t send useGasless: false with it, or the transfer goes out unsponsored and the source pays the fee. useGasless: true without feePayerAccountId doesn’t sponsor the transfer.
POST /v1/operations/tempo/transfer
Response
feePayerInfo.feePayerAccountId on the transaction. See How fees appear on the transaction.
Code sample
The sample reads credentials from environment variables. Never hardcode an API key or secret key.TypeScript