<!-- tempo-docs-context -->
> Source: [/docs/protocol/upgrades/t14](https://tempo.com/developers/docs/protocol/upgrades/t14.md)
> Section: [Tempo EVM](https://tempo.com/developers/docs/development.md). Build on Tempo EVM: wallets and keys, payments, transactions and fees, TIP-20 Tokens, contracts, exchange, network details, nodes, protocol specifications, and changelog.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.com/developers/llms.txt) and Markdown pages directly.

# T14 Network Upgrade

T14 upgrades the Account Keychain so accounts on Tempo support multiple signers, with approval thresholds, key rotation, and recovery built into the protocol. It also ends admin access keys' key management and tightens validator, consensus, and Zone Portal rules.

:::tip[T14 status]
T14 is scheduled to activate on testnet on November 24, 2026 and on mainnet on December 8, 2026, both at 15:00 UTC. Its scope may still change before activation. Until T14 activates, the account changes run only on the [Tempo Accounts devnet](https://tempo.com/developers/docs/accounts/create#connect-to-the-devnet).
:::

**Integration note:** T14 stops new admin access keys and removes existing ones' power to manage other keys. Existing admin keys can still spend without limit until you revoke them. If you use an admin key to manage a user's other keys, plan the change before T14. [See integration impact](https://tempo.com/developers/docs/protocol/upgrades/t14#integration-impact).

## Timeline

| Network | Status | Activation date (UTC) | Unix timestamp |
|---------|--------|-----------------------|----------------|
| Testnet | Scheduled | November 24, 2026 15:00 | `1795532400` |
| Mainnet | Scheduled | December 8, 2026 15:00 | `1796742000` |

<span id="overview" />

## T14 overview

* **Multiple signers per account:** several signers approve together once their weights reach a threshold, such as any two of three finance leads, with no multisig contract to deploy.
* **Keys change, the address doesn't:** signers replace a lost key or add a backup at the same address, without moving funds.
* **Existing accounts upgrade in place:** a single-key account gains signers and a threshold and keeps its address and balances.
* **Team approval for access keys:** a team's account can act as another account's access key, approving with its own signers.
* **Zone support:** these accounts work on Zones with the same signers and threshold.
* **Admin access keys removed:** Tempo rejects new admin access keys.
* **Validator and consensus rules:** blocks must pay the proposer's registered fee recipient, endpoint formats are stricter, and consensus defaults to deferred verification.
* **Paused Zone Portals:** a paused Zone Portal also rejects refund claims. Batch settlement continues.
* **Cheaper batches:** a batch call pays cold access only for a target no earlier call reached.

<span id="features" />

## T14 features

<span id="changes-to-accounts" />

### Multiple signers for accounts

T14 extends the Account Keychain so one address can be controlled by up to 48 signers. Each signer has a weight, and a transaction runs once the weights of the approving signers reach the account's threshold. With three signers at weight 1 and a threshold of 2, any two can approve a payment.

* **Mixed signing methods:** signers can be passkeys, P-256 keys, or standard Ethereum keys, so a user's passkey and a provider's key can approve together.
* **Rotation and recovery at the same address:** the current signers replace the signer list and threshold in one transaction. The address and balances stay the same, so anyone paying the account needs no update.
* **In-place upgrades:** an existing single-key account adds signers at the same address, and its original key is retired.
* **Team approval for access keys:** an account with multiple signers can be another account's [access key](https://tempo.com/developers/docs/accounts/access-keys) and approves with its own signers.

Read the specifications for [multiple signers](https://tips.sh/1107), [in-place upgrades](https://tips.sh/1113), and [access keys](https://tips.sh/1111), and the [Tempo EVM reference](https://tempo.com/developers/docs/development/configurable-accounts).

### Multiple signers on Zones

Zones read each account's signer configuration from Tempo, so an account uses the same signers and threshold on a Zone as on Tempo. A signer change applies on a Zone once it imports that Tempo block. Configuration updates and upgrades revert on a Zone with `UnsupportedOnZone()`.

Read the [specification](https://tips.sh/1154).

### Admin access key removal

From T14, Tempo rejects new admin access keys, and only an account's own key or its signers authorize, change, or revoke access keys. An admin key authorized before T14 keeps spending as an access key without limits until you revoke it. To let a second device manage keys, [add it as a signer](https://tempo.com/developers/docs/accounts/account-configuration/configuration-updates#add-a-signer).

Read the [specification](https://tips.sh/1137).

### Validator and consensus changes

* **Fee recipient:** Tempo rejects a block whose beneficiary isn't the proposer's fee recipient in `ValidatorConfigV2`, or whose proposer has no entry. A registered zero address burns the fees.
* **Endpoint format:** `addValidator`, `rotateValidator`, and `setIpAddresses` revert with `InvalidIp` when an ingress or egress address is longer than 255 bytes. They also revert for the IPv4-mapped IPv6 form, such as `::ffff:192.0.2.1`. Tempo doesn't recheck endpoints registered before T14.
* **Consensus verification:** `--consensus.verification-mode` defaults to `hardfork`, which switches to deferred verification at the first epoch boundary after T14. An explicit `immediate` or `deferred` setting still overrides it.

Read the [specification](https://tips.sh/1152).

### Paused Zone Portals

From T14, a paused Zone Portal also rejects refund claims. Batch settlement continues.

Read the [specification](https://tips.sh/1152).

### Batch call gas

From T14, each call after the first in a Tempo transaction pays the 2,600-gas cold access cost only when no earlier call targeted it and validation hasn't already loaded it, such as the sender, a fee payer, or the access key. Other calls pay 100 gas. Before T14, every call after the first paid 2,600 gas.

Read the [specification](https://tips.sh/1152).

## Integration impact

* **Existing accounts:** single-key accounts and limited access keys keep working unchanged. Adding signers to an account is optional.
* **Admin access keys:** if you use an admin key to manage a user's other keys, [add that device as a signer](https://tempo.com/developers/docs/accounts/account-configuration/configuration-updates#add-a-signer) instead and revoke admin keys you no longer need before T14 ([details](https://tempo.com/developers/docs/protocol/upgrades/t14#admin-access-key-removal)).
* **Account upgrades:** the upgrade call only exists once T14 activates on a network. Sent earlier, the transaction still pays its fee but leaves the account unchanged, so send upgrades only after activation.
* **Signature parsing:** accounts with multiple signers sign with the [`0x05` multisig signature](https://tempo.com/developers/docs/development/configurable-accounts#multisig-signature-format). Viem builds and reads it. If you parse or verify Tempo transaction signatures yourself, handle this type. It isn't valid as a fee payer signature, in subblock transactions, or in authorization lists.
* **Contracts that check signatures from configurable accounts:** single-key accounts are unchanged. A registered or upgraded account answers ERC-1271 `isValidSignature`, so Permit2 and similar verifiers work unchanged. After an upgrade, contracts using OpenZeppelin `SignatureChecker` before v5.1 still accept the retired original key. Contracts can also call `verifyConfigurableAccount` on the [signature verifier precompile](https://tempo.com/developers/docs/development/configurable-accounts#verify-owner-approvals-in-a-contract).
* **Validators:** check your fee recipient and endpoint formats against the [validator and consensus changes](https://tempo.com/developers/docs/protocol/upgrades/t14#validator-and-consensus-changes).
