diff --git a/src/pages/guide/node/network-upgrades.mdx b/src/pages/guide/node/network-upgrades.mdx index 5bbf5b7b..42ed5c1c 100644 --- a/src/pages/guide/node/network-upgrades.mdx +++ b/src/pages/guide/node/network-upgrades.mdx @@ -15,6 +15,8 @@ For detailed release notes and binaries, see the [Changelog](/changelog). | Release | Date | Network | Description | Priority | |---------|------|---------|-------------|----------| +| v1.7.0 (targeted) | Mon, May 11, 2026 | Moderato + Mainnet | Required for T4; embeds consensus context into the block header to unlock deferred verification (TIP-1031) and bundles T4 bug fixes and security hardening (TIP-1046). | Required | +| [v1.6.0](https://github.com/tempoxyz/tempo/releases/tag/v1.6.0) | Apr 16, 2026 | Moderato + Mainnet | Required for T3; implements enhanced access key permissions with periodic limits and call scoping (TIP-1011), the signature verification precompile (TIP-1020), and virtual addresses for TIP-20 deposit forwarding (TIP-1022). | Required | | [v1.5.3](https://github.com/tempoxyz/tempo/releases/tag/v1.5.3) | Apr 9, 2026 | Moderato + Mainnet | Patch release that restores OTLP HTTPS telemetry and fixes an epoch-transition consensus race that could incorrectly block straggling peers. Validators that skipped v1.5.2 should upgrade directly to this release. | Recommended | | [v1.5.2](https://github.com/tempoxyz/tempo/releases/tag/v1.5.2) | Apr 8, 2026 | Moderato + Mainnet | Maintenance release with the latest reth update, payload builder and RPC improvements, plus transaction validation and mempool hardening. | Recommended | | [v1.5.1](https://github.com/tempoxyz/tempo/releases/tag/v1.5.1) | Mar 29, 2026 | Moderato + Mainnet | Security patch for RPC endpoints that accept `stateOverride`, including `eth_call` and `debug_traceCall`. This release is required for RPC providers and other public RPC nodes, and low priority for validators. | RPC only | @@ -32,6 +34,26 @@ For detailed release notes and binaries, see the [Changelog](/changelog). --- +## T4 + +| | | +|---|---| +| **Scope** | Embed consensus context into the block header to unlock deferred verification, plus T4 bug fixes and security hardening | +| **TIPs** | [TIP-1031: Embed Consensus Context in the Block Header](/protocol/tips/tip-1031), [TIP-1046: T4 Hardfork Meta TIP](/protocol/tips/tip-1046) | +| **Details** | [T4 network upgrade](/protocol/upgrades/t4) | +| **Release** | v1.7.0 (targeted for Mon, May 11, 2026 16:00 CEST) | +| **Testnet** | Moderato: May 14, 2026 16:00 CEST (unix: 1778767200) | +| **Mainnet** | Presto: May 18, 2026 16:00 CEST (unix: 1779112800) | +| **Priority** | Required | + +### Who is affected? + +All node operators must upgrade before the T4 activation timestamp. TIP-1031 changes how block headers are produced and verified; non-upgraded nodes will have their proposals rejected and will fall out of consensus at activation. + +Smart contract developers and integrators are not directly affected by TIP-1031, but should review [TIP-1046](/protocol/tips/tip-1046) for the bundled gas accounting changes and access-key scope validation updates that may affect transaction gas usage post-T4. + +--- + ## T3 | | | diff --git a/src/pages/protocol/upgrades/t4.mdx b/src/pages/protocol/upgrades/t4.mdx new file mode 100644 index 00000000..66cd2d52 --- /dev/null +++ b/src/pages/protocol/upgrades/t4.mdx @@ -0,0 +1,44 @@ +--- +title: T4 Network Upgrade +description: Details and timeline for the T4 network upgrade, including consensus context in the block header and bundled bug fixes. +--- + +# T4 Network Upgrade + +This page summarizes T4 scope. + +:::info[T4 is not live yet] +The features described on this page are scheduled for T4 and are not active on Moderato or Presto yet. They only become live once the T4 activation timestamps are reached. +::: + +## Timeline + +| Network | Date | Timestamp | +|---------|------|-----------| +| Moderato (testnet) | May 14, 2026 4pm CEST | `1778767200` | +| Presto (mainnet) | May 18, 2026 4pm CEST | `1779112800` | + +Node operators must upgrade to the T4-compatible release (v1.7.0, targeted for May 11, 2026 4pm CEST) before the Moderato activation timestamp. + +## Overview + +T4 is Tempo's next network upgrade. It introduces the following changes: +- Embedding consensus context into the block header to unlock deferred verification and reduce finalization latency ([TIP-1031](/protocol/tips/tip-1031)) +- A bundle of T4 bug fixes and security hardening (https://tips.sh/1046) + +**Action required for node operators:** Upgrade to v1.7.0 before the Moderato activation timestamp. Non-upgraded nodes will fall out of consensus. + +## Compatible SDK releases + +T4-compatible SDK releases will be listed here as they ship. + +## Related docs +- [Network upgrades and releases](/guide/node/network-upgrades) +- [TIP-1031: Embed Consensus Context in the Block Header](/protocol/tips/tip-1031) +- [TIP-1046: T4 Hardfork Meta TIP](/protocol/tips/tip-1046) + +## Feature TIPs + +### TIP-1031: Embed Consensus Context in the Block Header + +[TIP-1031](/protocol/tips/tip-1031) adds an optional `Context` field (epoch, view, parent view, leader) as the last field of `TempoHeader`. This commits consensus metadata to the block hash so Tempo blocks implement Commonware's `CertifiableBlock` trait, enabling deferred verification (optimistic notarization with async background verification) and reduced finalization latency. Pre-activation headers are unchanged; post-activation headers require the field and validators reject mismatched context. diff --git a/vocs.config.ts b/vocs.config.ts index 9da48202..89c8e12b 100644 --- a/vocs.config.ts +++ b/vocs.config.ts @@ -725,11 +725,15 @@ export default defineConfig({ collapsed: true, items: [ { - text: 'T3', + text: 'T4', + link: '/protocol/upgrades/t4', + }, + { + text: 'T3 (Active)', link: '/protocol/upgrades/t3', }, { - text: 'T2 (Active)', + text: 'T2', link: '/protocol/upgrades/t2', }, ],