# T11 Network Upgrade

T11 gives applications more time to submit signed transactions and updates pricing and validation for calls to Tempo's built-in protocol functions.

For most partners, T11 requires action only if you use fixed gas limits or construct precompile calls directly.

:::info[T11 status]
T11 is active on testnet and mainnet. Release [v1.14.0](https://github.com/tempoxyz/tempo/releases/tag/v1.14.0) is required for T11; see the [Network Upgrades and Releases table](https://tempo.xyz/developers/docs/guide/node/network-upgrades#node-operator-updates) for the current node-operator release status.
:::

## Timeline

| Network | Date | Unix timestamp |
|---------|------|----------------|
| Testnet | Live: September 9, 2026 at 14:00 UTC | `1788962400` |
| Mainnet | Live: September 10, 2026 at 14:00 UTC | `1789048800` |

Node operators were required to run [v1.14.0](https://github.com/tempoxyz/tempo/releases/tag/v1.14.0) before activation to stay synced.

## T11 upgrade overview

T11 includes three protocol changes:

* **Longer transaction submission window.** Applications can give signed transactions up to five minutes to reach the network, instead of 30 seconds.
* **Updated gas pricing.** Calls to Tempo's built-in protocol functions pay a higher input gas charge that better reflects their processing cost.
* **Stricter precompile validation.** Precompile calls must use standard ABI encoding, and operations that check lists for duplicate values pay for that work explicitly.

## Longer transaction submission window

Some transactions pass through approval systems, relayers, or separate signing devices before reaching the network. The existing 30-second maximum can expire before those steps finish.

T11 increases the maximum expiry window to five minutes. Applications can still choose a shorter window when appropriate.

Replay protection remains in place, so the same signed transaction cannot be submitted twice. Transactions created before T11 continue to follow the existing 30-second limit.

Read the [TIP-1093 specification](https://tips.sh/1093).

## Updated gas pricing

Tempo provides built-in protocol functions, called precompiles, for operations such as account and token management. T11 increases the input gas charge for these calls from 6 to 30 gas per 32 bytes.

The increase is small for typical calls. Calls with less than 1 KiB of input add less than 768 gas. Integrations that submit unusually large inputs or use fixed gas limits should re-check their gas estimates and limits.

Applications that estimate gas before submitting transactions should automatically account for the new pricing.

Read the [TIP-1100 specification](https://tips.sh/1100).

## Stricter precompile validation

T11 requires calls to Tempo precompiles to use standard ABI encoding. Calls with overlapping or trailing data, gaps in dynamic data, or non-zero padding are rejected. Applications that use standard contract libraries and SDKs should already produce compatible calls.

T11 also adds a gas charge for checking duplicate values in account key permissions and Zone configuration lists. Duplicate values remain invalid, but the validation work is now included in the transaction's gas cost.

Integrations that construct precompile calls manually should verify their encoding. Applications should also estimate gas on the network where the transaction will execute instead of relying on fixed limits.

Read the [TIP-1105 specification](https://tips.sh/1105).

## Integration impact

Estimate gas on the network where the transaction will execute instead of relying on fixed limits, verify that precompile calls use standard ABI encoding with no trailing data or duplicate list values, and consider the longer expiry window for transactions that pass through approval or relay workflows.