> ## Documentation Index
> Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tempo Overview

> Send Tempo transfers from Fireblocks with fee token selection, fee sponsorship, parallel nonces, memos and virtual addresses, all through the API.

> [!NOTE]
>
> Every Tempo feature in this section is in beta and available through the API only. To get access, contact your Customer Success Manager (CSM).

Fireblocks runs Tempo on a dedicated transaction stack that supports five Tempo-native features: fee token selection, fee sponsorship, parallel nonces, memos and virtual addresses.

| Feature | What it does | How you use it |
| - | - | - |
| [Fee token selection](https://developers.fireblocks.com/docs/tempo-fee-token-selection.md) | Pay the network fee in any eligible USD stablecoin, per transaction | `feeCurrency` |
| [Fee sponsorship (fee payer)](https://developers.fireblocks.com/docs/tempo-fee-sponsorship.md) | A different vault account in your workspace pays the network fee | `feePayerAccountId` |
| [Parallel nonces](https://developers.fireblocks.com/docs/tempo-parallel-nonces.md) | Send several transactions from one vault account at the same time | `nonceStrategy`, `nonceLane` |
| [Memos](https://developers.fireblocks.com/docs/tempo-memos.md) | Attach a 32-byte reference, such as an invoice ID, to a TIP-20 transfer | `memo` on the destination |
| [Virtual addresses (TIP-1022)](https://developers.fireblocks.com/docs/tempo-virtual-addresses.md) | Receive deposits on derived addresses that the protocol forwards to one master wallet | Register an omnibus master wallet, then use its virtual addresses |

## 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_TEST` on 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](https://tempo.xyz/developers/docs/protocol/transactions/spec-tempo-transaction), the EIP-2718 type `0x76` 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

| Endpoint | When to use it |
| - | - |
| `POST /v1/operations/tempo/transfer` | The dedicated Tempo endpoint. It exposes every Tempo field at the top level of the request. Use it for every feature in this section. |
| `POST /v1/transactions` | The standard create-transaction endpoint. It supports plain Tempo transfers. The features in this section aren't available on it. |

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](https://developers.fireblocks.com/reference/api-idempotency.md#transaction-idempotency).

```json POST /v1/operations/tempo/transfer theme={"system"}
{
  "assetId": "PATHUSD_TEMPO_MODERATO_TEST_O46L",
  "amount": "100",
  "source": { "type": "VAULT_ACCOUNT", "id": "5" },
  "destination": {
    "type": "ONE_TIME_ADDRESS",
    "oneTimeAddress": { "address": "0x0F9C84F83Bd812E5cd84ca18D91Cb04D4F8fc4b6" }
  },
  "feeLevel": "MEDIUM",
  "externalTxId": "3b1f8c2e-5d4a-4e7b-9a60-2c8d1e5f7a94"
}
```

### 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 `networkRecords` array of the transaction object (`GET /v1/transactions/{txId}`). Each record has its own `assetId`, `source`, `destination`, `netAmount`, `networkFee` and `txHash`. See the [NetworkRecord object](https://developers.fireblocks.com/reference/transaction-objects.md#networkrecord). 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 its `assetId` is the token that paid it.
* **Fee currency.** `feeCurrency` on the transaction is the asset that paid the fee. The fee token you asked for is kept in `requestedFeeCurrency`.
* **Fee payer.** On a sponsored transaction, `feePayerInfo.feePayerAccountId` names 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. Set `feeLevel` to `LOW`, `MEDIUM` or `HIGH` instead.
* **Transfers only.** Contract calls still go out as standard EVM (type `0x2`) transactions and don't get the Tempo features in this section.
