Important
This release is required for the T14 network upgrade. Validators and RPC operators must upgrade before their network's activation.
T14 adds configurable accounts: several weighted owners with an approval threshold, and owners can change without changing the address. See the T14 upgrade page.
Update Priority
| User Class | Priority |
|---|---|
| Validators | High |
| RPC Nodes | High |
Nodes on an older release stop following the chain when T14 activates.
Activation Times
| Network | Activation | Unix timestamp |
|---|---|---|
| Moderato testnet | November 24, 2026, 15:00 UTC | 1795532400
|
| Mainnet | December 8, 2026, 15:00 UTC | 1796742000
|
TIPs included with T14
- TIP-1107: Configurable Accounts: Accounts with weighted owners and a threshold.
- TIP-1113: Account Migration and Original-Key Retirement: An existing account can become configurable at the same address. Its original key stops working on Tempo.
- TIP-1111: Configurable Account Access Keys: Configurable accounts can grant access keys and act as access keys for other accounts.
- TIP-1154: Configurable Accounts on Zones: Zones read account configuration from Tempo, so an account has the same owners on a zone.
- TIP-1137: Remove Admin Access Keys: No new admin keys can be granted.
- TIP-1152: T14 hardening: Validator endpoint, fee recipient, Zone Portal and AA batch gas rules (below).
Operators
Breaking Changes
- Image verification: from 1.19.0, images have GitHub build-provenance attestations and no Cosign signature. Switch to
gh attestation verify(guide). - Validator endpoints: endpoints over 255 bytes and IPv4-mapped IPv6 endpoints are rejected from T14. Check your registered endpoint.
- Block fees: a block must pay fees to the proposer's registered fee recipient.
What's Changed
- Verification mode (#8438, #9388):
--consensus.verification-modedefaults tohardfork, which switches to deferred verification once T14 is active.immediateanddeferredstill work. - Transaction pool (#9267, #9321, #9184, #9331): Subpools default to 200 MB, all transactions go in the 2D nonce pool with a limit per authority, and removed transactions are revalidated in batches.
- Consensus startup (#9360, #9127, #8905): The startup DKG epoch can't pass the finalized tip, loaded blocks are checked, and the node warns when a peer set nears
max-peers-per-set. - Flags and binaries (#9190, #9378):
--builder.disable-prewarmingtakes a value, and binaries carry version metadata.
Developers
SDK Versions for Configurable Accounts
| SDK | Version |
|---|---|
viem (viem/tempo)
| 2.57.19 or later |
| Accounts SDK | >= accounts 1.0.0
|
| tempo-alloy (Rust) | tempo/v1.19.0
|
| Foundry | >= v1.10.0 |
Breaking Changes
- Admin access keys: new admin keys are rejected from T14. Existing ones become access keys with no spending limit until revoked. Add the device as a signer instead (details).
Existing single-key accounts keep working unchanged. To move to configurable accounts, see the T14 integration impact and the account upgrade checklist.
Full Changelog: tempo/v1.18.4...tempo/v1.19.0