---
id: TIP-1158
title: T15 Hardfork Meta TIP
description: Meta TIP linking proposed T15 TIPs and additional fork-gated changes.
authors: Jennifer (@jenpaff)
status: Draft
related: TIP-1017, TIP-1022, TIP-1045, TIP-1094, TIP-1150, TIP-1160, TIP-1166, TIP-1171, TIP-1179, TIP-1180, TIP-1181
protocolVersion: T15
---

# TIP-1158: T15 Hardfork Meta TIP

## Abstract

T15 enables TIP-20 transfers within Zones, resolves TIP-1022 virtual addresses
on Zones and adds Zone-specific virtual deposit addresses, replaces the Zone
deposit queue cap with per-token withdrawal limits at the portal, adds an
org registry that gates Zone transfers, and lets configurable accounts sign
channel-reserve vouchers. It also lets static-only payment calls carry up to
32 trailing bytes and stay in the payment lane, makes the boundary block's DKG
outcome a block validity rule checked against the parent state, rejects
trailing bytes after DKG data in a block's extra data, disables ValidatorConfig
V1 and the V1 to V2 migration, and charges input cost on fixed-gas Zone
precompile calls. This meta TIP links the individual TIPs and specifies the
additional protocol changes.

## Motivation

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

---

# T15 TIPs

The following TIPs have changes proposed behind T15.

| TIP | Change | Implementation |
| --- | --- | --- |
| [TIP-1160: Zone TIP-20 Transfers](https://github.com/tempoxyz/tempo/pull/8858) | Enables TIP-20 transfers between accounts within a Zone, behind the portal's `transfersEnabled` opt-in, and mirrors each token's pause flag from Tempo. | [#8549](https://github.com/tempoxyz/tempo/pull/8549) |
| [TIP-1179: Zone Virtual Address Resolution](https://github.com/tempoxyz/tempo/pull/9428) | Zones read Tempo's TIP-1022 address registry, so deposits and transfers to a virtual address credit its master under the master's receive policy. | [#9409](https://github.com/tempoxyz/tempo/pull/9409) |
| [TIP-1094: Zone Virtual Deposit Addresses](https://github.com/tempoxyz/tempo/pull/7746) | Private deposit addresses that belong to one Zone, resolved by a Zone registry. | [#8864](https://github.com/tempoxyz/tempo/pull/8864) |
| [TIP-1171: Unbounded Zone Deposit Queues](https://github.com/tempoxyz/tempo/pull/9383) | Removes the Zone deposit queue cap and the withdrawal reserve. | [#9437](https://github.com/tempoxyz/tempo/pull/9437) |
| [TIP-1150: Per-Token Zone Withdrawal Limits](https://github.com/tempoxyz/tempo/pull/8903) | Rate-limits withdrawals per token at the Zone Portal; withdrawals over the limit queue until capacity refills. | [#9414](https://github.com/tempoxyz/tempo/pull/9414) |
| [TIP-1180: Zone Identity](https://github.com/tempoxyz/tempo/pull/9436) | A `ZoneIdentity` predeploy records orgs and members; Zone execution allows a TIP-20 transfer, deposit or withdrawal only along an edge both orgs allow for that token. | [#9432](https://github.com/tempoxyz/tempo/pull/9432) |
| [TIP-1181: Zone Identity Reads](https://github.com/tempoxyz/tempo/pull/9439) | An org's admin, and readers it names, may read its members' account-scoped state through precompile getters and the redacted RPC. | [#9438](https://github.com/tempoxyz/tempo/pull/9438) |
| [TIP-1166: Configurable Account Voucher Signers](https://github.com/tempoxyz/tempo/pull/9133) | Lets configurable accounts sign TIP20ChannelReserve vouchers (MPP). | [#9293](https://github.com/tempoxyz/tempo/pull/9293), [#9420](https://github.com/tempoxyz/tempo/pull/9420) |

---

# Additional protocol changes

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

## 1. Allow trailing bytes in payment calls

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

Amends [TIP-1045](./tip-1045.md): from T15, a static-only payment call MAY carry
up to 32 arbitrary bytes after its ABI-encoded arguments and still qualify for
the payment lane. Integrators append fixed-size tags, such as attribution IDs,
to TIP-20 transfers; since [TIP-1116](./tip-1116.md) these calls execute, but as
general transactions. The trailing bytes are not interpreted and do not change
which allow-list entry matches. A call with more than 32 trailing bytes matches
no entry. Entries with dynamic types (TIP20ChannelReserve `settle` and
`close`) are unchanged and remain bounded by the 2048-byte calldata limit.

## 2. Check the boundary block's DKG outcome in execution

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

The last block of each epoch (the boundary block) carries the next epoch's
`OnchainDkgOutcome` in its `extra_data`. Consensus supplies only the DKG
ceremony output; the payload builder fills in `epoch`, `next_players` and
`is_next_full_dkg` from ValidatorConfigV2 in the parent state.

From T15, the block executor decodes a boundary block's `extra_data` as an
`OnchainDkgOutcome` and rejects the block if decoding fails or any field
differs from the parent state:

- `epoch` MUST be the next epoch.
- `next_players` MUST be the active ValidatorConfigV2 validators, skipping
  those whose public key, ingress or egress does not decode and counting each
  public key once.
- `is_next_full_dkg` MUST be true exactly when the next epoch is
  ValidatorConfigV2's next full DKG epoch.

The outcome MUST fill all of `extra_data`
([change 3](#3-reject-trailing-bytes-in-dkg-extra-data)). ValidatorConfigV2 is
read from the backing database, and these reads are not part of the block's
state or access list. The check is skipped when ValidatorConfigV2 is not
initialized in the parent state. Consensus compares only the ceremony output.
Before T15, verifying validators compare the whole outcome against the parent
state.

## 3. Reject trailing bytes in DKG extra data

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

A block's `extra_data` carries a signed DKG dealer log or, in the boundary
block, the next epoch's `OnchainDkgOutcome`. Before T15, decoders ignore any
bytes after these values. From T15, decided by the block's timestamp, the value
MUST fill all of `extra_data`:

- A proposal whose dealer log has trailing bytes fails verification. The DKG
  manager ignores such a log in notarized or finalized blocks, so its dealer
  does not count for the ceremony.
- A boundary block whose outcome has trailing bytes fails consensus
  verification. Execution also rejects it in the change 2 check whenever
  ValidatorConfigV2 is initialized.

The committee system call still reads the outcome without this check.

## 4. Disable ValidatorConfig V1 and the V1 to V2 migration

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

From T15, every selector of the ValidatorConfig (V1) precompile, including its
views, reverts with `UnknownFunctionSelector(bytes4)`, as do
`migrateValidator` and `initializeIfMigrated` on ValidatorConfigV2
([TIP-1017](./tip-1017.md)). All other ValidatorConfigV2 functions are
unchanged.

Once ValidatorConfigV2 is initialized, as on mainnet and Moderato, consensus,
DKG and fee-recipient lookups read only V2, so V1 writes have no effect and the
migration calls already revert with `AlreadyInitialized`. Pre-T15 behavior is
preserved, so historical blocks replay unchanged. Tooling that still uses V1,
such as `xtask generate-add-peer`, must use ValidatorConfigV2 on networks at
T15 or later.

## 5. Charge input cost on fixed-gas Zone precompile calls

**PR**: [#9381](https://github.com/tempoxyz/tempo/pull/9381) · **Author**: @0xrusowsky

From T15, fixed-gas Zone precompile calls (ZTIP20 transfers and approvals, and
the receive policy claim) charge `fixed_gas + input_cost` instead of the flat
fixed gas alone, so calldata padding pays for its length. Calldata length is
public, so charging for it reveals nothing. The fixed gas still stays above the
worst-case storage-dependent cost of every legitimate call, so normal usage does
not reveal storage state.
