Skip to content

Releases: tempoxyz/tempo

Release v1.11.0

Choose a tag to compare

@github-actions github-actions released this 22 Jul 17:18
Immutable release. Only release title and notes can be modified.
v1.11.0
fc6a697

Important

This release is required for the T8 network upgrade scheduled for testnet on July 27, 2026 16:00 CEST (1785160800) and mainnet on July 30, 2026 16:00 CEST (1785420000). Node operators must update before activation or their nodes will fall out of sync. T8 activates versioned StablecoinDEX order storage, FeeAMM policy changes, current-committee persistence, and the final phase of TIP-20 reward deprecation.

Update Priority

User Class Priority
Validators High
RPC Nodes High

Nodes that are not updated will fall out of sync at the T8 activation timestamp.

Activation Times

Network Date Timestamp
Testnet July 27, 2026 16:00 CEST (14:00 UTC) 1785160800
Mainnet July 30, 2026 16:00 CEST (14:00 UTC) 1785420000

TIPs included with T8

The T8 network upgrade includes:

  1. TIP-1042 FeeAMM TIP-403 Policy Exemptions: Fee collection checks the fee payer as an authorized sender without requiring the FeeManager to be an authorized recipient. Public FeeAMM operations retain policy enforcement, with explicit authorization requirements for liquidity providers and recipients on mint and burn. Existing pools are grandfathered and are not revalidated or migrated at activation.
  2. TIP-1062 Versioned DEX Order Storage: Introduces version-dispatched StablecoinDEX order storage. Legacy version-0 orders remain readable, while T8 writes compact version-1 records that reduce an order from six storage slots to four. Post-T8 flip-order rewrites migrate the rewritten record through the versioned storage path.
  3. TIP-1070 Current Committee State: Activates the CurrentCommittee precompile at 0xC077E00000000000000000000000000000000000. An epoch-boundary system call persists the committee selected by the finalized DKG outcome, including the fallback outcome when DKG does not complete, so contracts can read the committee that is actually effective for consensus.
  4. TIP-1075 Deprecate TIP-20 Rewards: Completes the two-stage reward shutdown begun at T7. After T8, transfers, mints, burns, fee refunds, and other balance-changing paths stop checkpointing reward accumulators. Rewards settled before T8 remain claimable indefinitely; lazy rewards that were not checkpointed before activation are forfeited.
  5. TIP-1087 V2 DEX Order Storage with Book Indexes: Adds version-2 orders that replace the repeated 32-byte book key with a compact index, reducing indexed orders from four slots to three. New orderbooks persist their index automatically. Pre-existing orderbooks remain functional with version-1 writes until their index is supplied by off-chain migration tooling through the new setBookIndex API.

Breaking Changes

  • Consensus-breaking upgrade: T8 changes protocol state-transition rules. Nodes that do not run this release before activation will reject or produce invalid blocks after the T8 timestamp.
  • TIP-20 pending reward behavior changes: T8 disables reward-accumulator updates on ordinary balance changes. Only reward balances settled before activation remain claimable; integrations must not rely on a post-T8 transfer to checkpoint older lazy accruals.
  • StablecoinDEX now contains mixed order layouts: Readers and writers must use the versioned order-storage abstraction. Direct assumptions about the legacy six-slot order layout are invalid for T8-created orders, and unknown versions must be rejected.
  • DEX index migration is off-chain assisted: Existing orderbooks are not scanned or migrated automatically. They continue writing version-1 orders until setBookIndex(uint32) records a verified index; tooling may also use bookIndexForKey(bytes32) and bookKeyForIndex(uint32).
  • FeeAMM policy authorization changes: Fee collection no longer checks FeeManager recipient authorization, while T8 liquidity mint and burn paths enforce the TIP-1042 participant checks. Existing pools are not revalidated.
  • New reserved precompile surface: The CurrentCommittee precompile becomes active at 0xC077E00000000000000000000000000000000000. Tooling and contracts must treat this address as reserved protocol space.
  • Consensus snapshot archive layout changed: Snapshot manifests are written at the archive root instead of under consensus/. Snapshot producers and consumers that depend on the old prefix must be updated.

Operators

What's Changed

  • T8 activation schedule (#6866, #6888): Adds the T8 chainspec configuration and schedules activation for July 27 on testnet and July 30 on mainnet.
  • Consensus-enabled snapshot startup (#6536, #6714, #6796): When a snapshot includes consensus certificates, starts fresh nodes from its smallest certified height; otherwise the existing execution-finalized fallback remains in place. This also relaxes archive contents to hash/size and safe-unpack constraints, moves the manifest to the archive root, adds certification-anchor recovery scenarios, and passes --force through to the wrapped Reth download command.
  • CL-to-EL backfill and startup floors (#6517, #6723, #6872): Simplifies the DKG/executor startup path, backfills CL blocks to the finalized floor before the main executor loop, treats an unfillable archive backfill as a hard error, and preserves a nonzero marshal startup floor across restarts.
  • Execution/consensus reconciliation (#6790, #6801): Makes hybrid gap tracking aware of the Reth finalized watermark and permits EL to be ahead of CL when the overlapping finalized block hashes agree, avoiding unnecessary rewinds while still rejecting inconsistent state.
  • Finalized archive observability (#6775): Reports the contents of the finalized block archive to make snapshot and recovery state easier to diagnose.
  • DKG correctness and diagnostics (#6809, #6834): Corrects invalid dealer-log diagnostics and preserves first-write-wins finalized dealer logs while filling incomplete caches, keeping validators on the same DKG input.
  • Consensus proposal metrics (#6831): Counts canonical self-proposals even when EL is already at or ahead of the CL finalized block.
  • Regenesis validator-state safety (#6599, #6745, #6820): Synchronizes ValidatorConfigV2 during regenesis, fully replaces its block-0 current and historical state when validator counts change, streams large changesets to avoid OOMs, and fixes a process-seed-dependent static-file provider self-deadlock.
  • Follower reliability (#6392, #6754, #6783): Enforces websocket upstreams, adds keepalive pings and reconnect behavior, and uses a follower-specific executor that verifies finalizations, advances the marshal, and maintains a one-epoch sync window.
  • Consensus operations and tooling (#6229, #6545, #6633, #6678): Lowers noisy cut-short event logs, defines a three-epoch --minimal sync window, moves identity transitions from node RPC to an xtask, and exercises strict-startup behavior in end-to-end testing.
  • Hardware telemetry (#6814): Exposes a static anonymized hardware metric covering CPU, core count, memory, and filesystem types while omitting disk names and mount sources.
  • Reth and Alloy updates (#6797, #6878): Updates the pinned Reth revision and Alloy core dependencies used by the node.

Developers

SDK Crate Versions

Package Version Notes
tempo-alloy 1.10.1 Published since the previous binary release.
tempo-primitives 1.10.1 Published since the previous binary release.
tempo-contracts 1.10.1 Includes T8 ABI/address surfaces.
tempo-chainspec 1.10.1 Includes the standalone hardfork dependency.
tempo-hardfork 1.10.1 New crate for Tempo hardfork identifiers and activation schedules.

T8 Protocol Changes

  • FeeAMM TIP-403 policy exemptions (#6604, #6605, #6808): Implements TIP-1042's T8 fee-collection exemption, adds the liquidity lifecycle authorization gates, updates txpool policy invalidation to stop tracking the exempt FeeManager recipient side, and documents that existing pools are grandfathered.
  • Versioned StablecoinDEX order storage (#4075, #6546): Adds version detection and dis...
Read more

Release v1.10.2

Choose a tag to compare

@github-actions github-actions released this 17 Jul 13:26
Immutable release. Only release title and notes can be modified.

This patch release updates the v1.10.x release line with alloy dependency updates.

Update Priority

User Class Priority
Validators High
RPC Nodes High

Operators running v1.10.x should upgrade to v1.10.2.

tempo-primitives@1.10.1

Choose a tag to compare

@tempoxyz-release-bot tempoxyz-release-bot released this 07 Jul 10:55
Immutable release. Only release title and notes can be modified.
3e95ed3

What's Changed

Full Changelog: https://github.com/tempoxyz/tempo/compare/tempo-alloy@1.10.0...tempo-primitives@1.10.1

tempo-hardfork@1.10.1

Choose a tag to compare

@tempoxyz-release-bot tempoxyz-release-bot released this 07 Jul 10:55
Immutable release. Only release title and notes can be modified.
3e95ed3

What's Changed

Full Changelog: https://github.com/tempoxyz/tempo/compare/tempo-alloy@1.10.0...tempo-hardfork@1.10.1

tempo-contracts@1.10.1

Choose a tag to compare

@tempoxyz-release-bot tempoxyz-release-bot released this 07 Jul 10:55
Immutable release. Only release title and notes can be modified.
3e95ed3

Patch Changes

  • Added IStorageCredits::Mode::as_str returning the lowercase string label for a storage credit mode. (by @DerekCofausper, #6734)
What's Changed

tempo-chainspec@1.10.1

Choose a tag to compare

@tempoxyz-release-bot tempoxyz-release-bot released this 07 Jul 10:54
Immutable release. Only release title and notes can be modified.
3e95ed3

What's Changed

Full Changelog: https://github.com/tempoxyz/tempo/compare/tempo-alloy@1.10.0...tempo-chainspec@1.10.1

tempo-alloy@1.10.1

Choose a tag to compare

@tempoxyz-release-bot tempoxyz-release-bot released this 07 Jul 10:54
Immutable release. Only release title and notes can be modified.
3e95ed3

Patch Changes

  • Added typed RecoveryAuthority selector and set_receive_policy_for_receiver helper for building validated TIP-1028 receive-policy calls, rejecting recovery authorities that can never pass ReceivePolicyGuard.claim(). (by @DerekCofausper, #6734)
What's Changed

tempo-primitives@1.10.0

Choose a tag to compare

@tempoxyz-release-bot tempoxyz-release-bot released this 30 Jun 07:02
Immutable release. Only release title and notes can be modified.
325c5a4

Minor Changes

  • Bump the Tempo SDK crate set to the 1.10 minor release. (by @DerekCofausper, #6610)
What's Changed

tempo-hardfork@1.10.0

Choose a tag to compare

@tempoxyz-release-bot tempoxyz-release-bot released this 30 Jun 07:02
Immutable release. Only release title and notes can be modified.
325c5a4

Minor Changes

  • Bump the Tempo SDK crate set to the 1.10 minor release. (by @DerekCofausper, #6610)
What's Changed

tempo-contracts@1.10.0

Choose a tag to compare

@tempoxyz-release-bot tempoxyz-release-bot released this 30 Jun 07:02
Immutable release. Only release title and notes can be modified.
325c5a4

Minor Changes

  • Bump the Tempo SDK crate set to the 1.10 minor release. (by @DerekCofausper, #6610)
What's Changed