> ## 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 Parallel Nonces

> Send several Tempo transactions from one vault account at the same time with nonce lanes or expiring transactions, and understand the fee impact of each.

> [!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).

On a standard EVM chain, each address has one nonce counter, so a vault account can have only one transaction in flight at a time. Tempo's 2D nonces add a second dimension, the nonce key or "lane". Each lane is its own counter, so transactions on different lanes don't wait for each other. Set `nonceStrategy` to choose how a transfer gets its nonce.

| `nonceStrategy` | Behavior | Ordering | Extra fee |
| - | - | - | - |
| `SEQUENTIAL` (default) | Lane 0, the standard EVM nonce | Strict, across all of the vault account's transactions | None |
| `USER_DEFINED_LANE` | The lane you set in `nonceLane`, from `1` to `16` | Strict within a lane, none across lanes | One-time cost the first time a lane is used |
| `EXPIRING` | No nonce sequence. The transaction is valid for up to 5 minutes. | None | None |

## Set the strategy

On `POST /v1/operations/tempo/transfer`, `nonceStrategy` and `nonceLane` are top-level fields:

```json POST /v1/operations/tempo/transfer theme={"system"}
{
  "assetId": "PATHUSD_TEMPO_MODERATO_TEST_O46L",
  "amount": "40",
  "source": { "type": "VAULT_ACCOUNT", "id": "5" },
  "destination": { "type": "VAULT_ACCOUNT", "id": "8" },
  "nonceStrategy": "USER_DEFINED_LANE",
  "nonceLane": 3,
  "externalTxId": "5a6b7c8d-9e0f-4a1b-8c2d-3e4f5a6b7c8d"
}
```

`nonceLane` is an integer from 1 to 16, and Fireblocks accepts it only with `USER_DEFINED_LANE`.

## Choose a strategy

* **Use `USER_DEFINED_LANE`** when some transactions must land in order and others don't. For example, give payouts lane 1 and treasury rebalancing lane 2. Transactions on the same lane are queued one after another, so a stuck transaction holds up only its own lane.
* **Use `EXPIRING`** for the most throughput when order doesn't matter. Expiring transactions need no nonce, so any number can be in flight at once.
* **Lanes belong to the vault account's Tempo address, not to an asset.** A PathUSD transfer and an OpenUSD transfer on lane 3 from the same vault account queue behind each other.

## Fee implications

* **Opening a lane costs extra gas, once.** The first transaction on a new lane creates permanent state on-chain. For that transaction, Fireblocks adds 250,000 gas. In testing, the first transfer on a new lane cost 0.00045 USD, against 0.00005 USD for a sequential transfer. Later transactions on that lane cost about the same as sequential ones.
* **Lanes are permanent.** Once opened, a lane stays open for that address. Reuse a few lanes instead of spreading load across all 16.
* **Expiring transactions add no state, so they cost nothing extra.** If one isn't included before it expires, it fails and can't be revived, because the expiry is part of the signed transaction. Create a new transaction instead. Policy approval happens before the expiry window starts, so waiting for an approval doesn't use it up.
* **No speed-up or replace.** Replace-by-fee isn't available for `USER_DEFINED_LANE` or `EXPIRING` transactions. Set a suitable `feeLevel` when you create the transaction.

For the protocol rules, see Tempo's [transaction specification](https://tempo.xyz/developers/docs/protocol/transactions/spec-tempo-transaction).
