This is a maintenance release that updates the reth dependency and deprecates the --consensus.fee-recipient flag. The flag will be deprecated ~2 weeks, we ask validators to migrate the recipient to the validator contract before the flag is removed.
Update Priority
This table provides priorities for which classes of users should update to this release.
| User Class | Priority |
|---|---|
| Validators | Not Recommended * |
| RPC Nodes | Low |
*Validators have reported issues with the telemetry endpoint, we ask validators to skip this release and wait for a patch.
Upcoming Breaking Changes
Validators
As part of the Validator Config v2 migration on Tempo testnet and mainnet, fee-recipient configuration will be migrated to the onchain validator configuration. This release includes the supporting node changes so proposers read the fee recipient from validator contract state. The --consensus.fee-recipient flag will be removed in about two weeks.
After migration, fee-recipient updates should be made through the validator contract. See: https://docs.tempo.xyz/guide/node/validator-config-v2
What's Changed
- Reth dependency update: Pulls in the latest upstream reth fixes and improvements across payload building, trie and state handling, RPC behavior, and overall execution-path stability and performance.
- Payload builder and consensus correctness: Improves payload construction on non-canonical ancestors, aligns fee-recipient handling with the validator configuration changes, and tightens validation of end-of-block system transaction ordering.
- RPC and operator ergonomics: Adds the
tempo_forkScheduleRPC endpoint and improves telemetry labeling and CLI behavior around telemetry URL configuration. - Validation and mempool hardening: Strengthens transaction validation and pool rechecks with fixes for wildcard fee-token spending-limit handling, paused-token precedence, and P256 signature edge cases.
Full Changelog: v1.5.1...v1.5.2