---
id: TIP-1152
title: T14 Hardfork Meta TIP
description: Meta TIP linking proposed T14 TIPs and additional fork-gated changes.
authors: Richard Janis Goldschmidt (@SuperFluffy), Jennifer (@jenpaff)
status: Approved
related: TIP-1017, TIP-1107, TIP-1111, TIP-1113, TIP-1137, TIP-1154
protocolVersion: T14
---

# TIP-1152: T14 Hardfork Meta TIP

## Abstract

T14 adds configurable accounts, with account migration, access keys and zone
support, removes admin access keys, enforces proposer
fee recipients, bounds validator endpoint lengths, defaults consensus to
deferred verification after the fork boundary, blocks Zone Portal refund
claims while paused, and charges each AA batch call target's cold access once.
This meta TIP links the individual TIPs and specifies the additional protocol
changes.

## Motivation

Collect the T14 upgrade scope and implementation links in one place for review.

---

# T14 TIPs

The following TIPs have changes proposed behind T14.

| TIP | Change |
| --- | --- |
| [TIP-1107: Configurable Accounts](https://github.com/tempoxyz/tempo/pull/7510) | Account creation, signature verification, commitment storage and owner updates. |
| [TIP-1113: Account Migration and Original-Key Retirement](https://github.com/tempoxyz/tempo/pull/7510) | Upgrades an existing account in place to a configurable account and retires its original key. |
| [TIP-1111: Configurable Account Access Keys](https://github.com/tempoxyz/tempo/pull/7510) | Lets a configurable account act as an access key and sign key authorizations. |
| [TIP-1154: Configurable Accounts on Zones](https://github.com/tempoxyz/tempo/pull/8721) | Zone support for configurable accounts: zones read account commitments from Tempo. |
| [TIP-1137: Remove Admin Access Keys](https://github.com/tempoxyz/tempo/pull/8204) | Disables new admin-key grants and removes existing keys' admin authority. Implementation: [#8618](https://github.com/tempoxyz/tempo/pull/8618). |

---

# Additional protocol changes

These changes are not covered by an individual T14 TIP. They are proposed behind
T14; pre-T14 execution rules are preserved.

## 1. Bound validator endpoint lengths

**PR**: [#8206](https://github.com/tempoxyz/tempo/pull/8206) · **Author**: @hamdiallam

Amends [TIP-1017](./tip-1017.md): `addValidator`, `rotateValidator`, and
`setIpAddresses` revert with `InvalidIp(string input, string reason)` when `ingress` or
`egress` exceeds 255 bytes, the maximum the one-byte length prefix in validator
signature messages can encode. Ingress is checked before egress, and each
length before its format. Malformed inputs within the limit still revert with
`NotIpPort` (ingress) or `NotIp` (egress). Stored endpoints are not
revalidated, and V1 is unchanged.

## 2. Default consensus to deferred verification after the fork boundary

**PR**: [#8438](https://github.com/tempoxyz/tempo/pull/8438) · **Author**: @decofe

Defaults `--consensus.verification-mode` to `hardfork`. Selects immediate or
deferred verification once per epoch using the previous epoch's finalized
boundary-block timestamp, or genesis for epoch zero. Deferred verification
starts when that timestamp reaches T14; explicit `immediate` and `deferred`
overrides remain available.

## 3. Enforce the proposer's registered fee recipient

**PR**: [#8572](https://github.com/tempoxyz/tempo/pull/8572) · **Author**: @SuperFluffy

Block execution rejects a block if its beneficiary differs from the proposer's
`ValidatorConfigV2` fee recipient, or if the proposer has no entry. The recipient
is resolved from parent state. A registered zero address burns the fees.

## 4. Pause Zone Portal refund claims

**PR**: [#8295](https://github.com/tempoxyz/tempo/pull/8295) · **Author**: @decofe

From T14, a paused Zone Portal rejects refund claims, alongside deposits and
withdrawal processing. Batch settlement continues while paused. Pre-T14 portal
behavior is unchanged.

## 5. Reject IPv4-mapped IPv6 validator endpoints

**PR**: [#8865](https://github.com/tempoxyz/tempo/pull/8865) · **Author**: @hamdiallam

Amends [TIP-1017](./tip-1017.md): from T14, `addValidator`, `rotateValidator`,
and `setIpAddresses` revert with `InvalidIp(string input, string reason)` when `ingress` or
`egress` is an IPv4-mapped IPv6 address (`::ffff:a.b.c.d`). Such an endpoint
must use its IPv4 form, so ingress uniqueness cannot be bypassed by spelling one
endpoint two ways. Stored endpoints are not revalidated, and V1 is unchanged.

## 6. Charge AA batch call target access once per cold target

**PR**: [#9096](https://github.com/tempoxyz/tempo/pull/9096) · **Authors**: @klkvr, @0xrusowsky 

From T14, each call after the first in a Tempo transaction pays the cold account
access cost (2,600 gas) only when its target is outside the transaction's warm
set and no earlier call targeted it. The warm set holds the sender, the first
call's target, precompiles and access-list addresses. It leaves out the
beneficiary, which is warmed after intrinsic gas, so intrinsic gas doesn't
depend on which validator builds the block. Every other call pays the warm
access cost (100 gas). Before T14, every call after the first paid 2,600 gas,
even when its target repeated. The charge stays in intrinsic gas, so the pool
still rejects underfunded batches up front.
