tempoxyz/tempo v1.4.0 on GitHub

foundry: use v1.6.0-t1c ( foundryup -n tempo -i v1.6.0-t1c )
tempo-alloy: pin the dependency to v1.4.0
pytempo: use v0.3.1
tempo-go: use 0.3.0
viem: use 2.47.0

Important

This release is required for the T1C network upgrade with the following activation times:

Node operators must update before activation, otherwise nodes will fall out of sync with the network.

This release includes a breaking keychain-signature migration at T1C (only V2signatures and hashes accepted post T1C).

Libraries & Tools

Migrated Keychain Signatures from legacy to V2: pre-T1C only legacy keychain signatures (V1) are accepted, post-T1C only keychain signatures V2 (type 0x04) are accepted. Pre T1C keys will continue to be accessible, only the signature type and hash calculations have changed.
KeyAuthorization wildcard removed post-T1C: chain_id=0 is no longer valid after activation; key authorizations must use the exact Tempo chain ID.
Precompile fork boundary update: precompiles switch from Prague to Osaka at T1C.

Added t1c hardfork support in chainspec/genesis and activation wiring (#2860).
Bumped precompile set from Prague to Osaka at T1C (#2809).
Added keychain signature V2 support and hardfork-aware validation gates (#2867).
Enforced strict post-T1C key authorization chain_id checks (no wildcard) (#2871).
Moved keychain and fee/reserve checks to the T1C boundary (#2861, #2862, #2866, #2870).
Improved txpool expiry/key tracking cleanup and paused-pool handling (#2874, #2878).
Added checkpoint-guarded atomic rollback protection for batched precompile state mutations (#2879).
Fixed fee-payer whitelist integration test coverage for T1C behavior (#2875).