From 47f24f12ba290743b37e37b2d2cf813c72b44047 Mon Sep 17 00:00:00 2001 From: Jennifer <5339211+jenpaff@users.noreply.github.com> Date: Wed, 8 Apr 2026 12:18:35 +0100 Subject: [PATCH] docs(node): add v1.5.2 release and fee-recipient warning Co-authored-by: Jennifer <5339211+jenpaff@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d681d-243e-750d-977f-60496016133f Co-authored-by: Amp --- src/pages/cli/node.mdx | 6 +++++- src/pages/guide/node/network-upgrades.mdx | 5 +++++ src/pages/guide/node/validator.mdx | 6 +++++- 3 files changed, 15 insertions(+), 2 deletions(-) diff --git a/src/pages/cli/node.mdx b/src/pages/cli/node.mdx index 52ea6327..3d0e3b42 100644 --- a/src/pages/cli/node.mdx +++ b/src/pages/cli/node.mdx @@ -33,9 +33,13 @@ Flags grouped by function: | Flag | Description | | --- | --- | | `--consensus.signing-key ` | Path to validator signing key | -| `--consensus.fee-recipient ` | Address to receive validator fees | +| `--consensus.fee-recipient ` | Deprecated validator fee-recipient flag. Migrate to on-chain fee-recipient management via Validator Config V2. | | `--consensus.datadir ` | Separate volume for consensus data | +:::warning +`--consensus.fee-recipient` is deprecated as of `v1.5.2` and will be removed in an upcoming release. See [Validator Config V2](/guide/node/validator-config-v2). +::: + ### Observability | Flag | Description | diff --git a/src/pages/guide/node/network-upgrades.mdx b/src/pages/guide/node/network-upgrades.mdx index 6a3ee29b..f56cd48f 100644 --- a/src/pages/guide/node/network-upgrades.mdx +++ b/src/pages/guide/node/network-upgrades.mdx @@ -15,6 +15,7 @@ For detailed release notes and binaries, see the [Changelog](/changelog). | Release | Date | Network | Description | Priority | |---------|------|---------|-------------|----------| +| [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, and validator fee-recipient migration support. | 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 | | [v1.5.0](https://github.com/tempoxyz/tempo/releases/tag/v1.5.0) | Mar 26, 2026 | Moderato + Mainnet | Required for T2; implements compound transfer policies (TIP-1015), permit support for TIP-20 (TIP-1004), ValidatorConfig V2 (TIP-1017), and 14 audit-driven bug fixes (TIP-1036) | Required | | [v1.4.3](https://github.com/tempoxyz/tempo/releases/tag/v1.4.3) | Mar 18, 2026 | Moderato + Mainnet | Fixes gas price oracle poisoning that caused inflated fee estimates for wallet transactions | Recommended | @@ -24,6 +25,10 @@ For detailed release notes and binaries, see the [Changelog](/changelog). | [v1.3.1](https://github.com/tempoxyz/tempo/releases/tag/v1.3.1) | Feb 22, 2026 | Testnet + Mainnet | Fixes high-load issues and finalizes T1A/T1B hardening for expiring nonce replay protection and keychain precompile gas handling | Required | | [v1.2.0](https://github.com/tempoxyz/tempo/releases/tag/v1.2.0) | Feb 13, 2026 | Mainnet only | Fixes validation bug rejecting transactions with gas limits above ~16.7M, blocking large contract deployments | Required | +:::warning +`--consensus.fee-recipient` is deprecated as of `v1.5.2` and will be removed in an upcoming release. Validators should migrate fee-recipient management to [Validator Config V2](/guide/node/validator-config-v2). +::: + --- ## T3 diff --git a/src/pages/guide/node/validator.mdx b/src/pages/guide/node/validator.mdx index 777d7872..2f9b9495 100644 --- a/src/pages/guide/node/validator.mdx +++ b/src/pages/guide/node/validator.mdx @@ -32,6 +32,10 @@ tempo node --datadir \ --telemetry-url ``` +:::warning +`--consensus.fee-recipient` is deprecated as of `v1.5.2` and will be removed in an upcoming release. Validators should migrate fee-recipient management to [Validator Config V2](/guide/node/validator-config-v2). +::: + ### Optional flags | Flag | Description | @@ -71,7 +75,7 @@ The telemetry endpoint does **not** collect any ambient information about the ho The data is strictly limited to the node's own operational metrics and logs. -The notable difference between RPC nodes and validator nodes is the omission of the `--follow` argument and the addition of the `--consensus.signing-key` and `--consensus.fee-recipient` arguments. The fee recipient is the address that will receive transaction fees in your validators' proposed blocks. +The notable difference between RPC nodes and validator nodes is the omission of the `--follow` argument and the addition of the `--consensus.signing-key` argument. Validator fee recipients are moving to on-chain management via Validator Config V2, and the legacy `--consensus.fee-recipient` flag is deprecated. Once your node is up, it may not start syncing immediately. This is because your node might not be part of the active set. In most cases, your validator will enter the active set in under 6 hours after the on-chain addition of the validator identity.