Tempo shipped critical transaction re-validation fixes for policy changes and removed the enable-subblocks CLI flag, signaling subblocks are now the default consensus behavior.

> impact

Tempo merged three targeted changes this week: a bug fix ensuring transactions are re-validated whenever a policy change occurs (PR #3532), a companion fix correcting fee token resolution logic during policy update checks, and a refactoring commit that removes the `enable-subblocks` CLI flag from the consensus module (PR #3510). Together, these changes tighten the correctness guarantees around transaction validation and simplify the node operator experience. The re-validation fix addresses a subtle but important edge case. Previously, transactions that had already passed validation could remain in the pool even after a policy update rendered them invalid. This could lead to inconsistent state or failed transactions at execution time. The companion fix ensures that during policy update checks, the *resolved* fee token is used rather than a potentially stale or incorrect token reference — a distinction that directly affects fee calculation correctness and transaction processing reliability. Both fixes were authored by Arsenii Kulikov and target the core transaction pipeline. The removal of the `enable-subblocks` CLI flag is a clear signal that subblocks are graduating from an opt-in experimental feature to the default (and only) consensus behavior in Tempo. This is a breaking change for node operators who explicitly set this flag in their configuration files or startup scripts. If you're running a Tempo node, audit your launch configuration now — the flag will no longer be recognized, and its presence may cause startup errors depending on your CLI parser behavior.

> Try this now

try this

# Tempo transaction re-validation & policy change walkthrough
# ============================================================
# If you're building on Tempo and submitting transactions programmatically,
# here's how these changes affect your workflow.

# 1. Policy changes now trigger automatic re-validation of pooled transactions.
#    Previously, a transaction submitted *before* a policy update could linger
#    in the mempool even if the new policy invalidated it.
#
#    Before (buggy behavior):
#    submit_tx(tx_a)          # tx_a validated against policy_v1 ✅
#    update_policy(policy_v2) # policy changes — tx_a NOT re-checked ❌
#    # tx_a could fail at execution time
#
#    After (PR #3532):
#    submit_tx(tx_a)          # tx_a validated against policy_v1 ✅
#    update_policy(policy_v2) # tx_a re-validated against policy_v2 ✅ or evicted

# 2. Fee token resolution is now consistent during policy checks.
#    If your dapp specifies a fee token, ensure you're referencing the
#    canonical resolved token address, not an alias or wrapper.
#
#    # Example: submitting a transaction with explicit fee token
#    tx = build_transaction(
#        sender=my_account,
#        payload=call_data,
#        fee_token="0xResolvedFeeTokenAddress"  # use the resolved address
#    )
#    # The node will now correctly match this against policy rules

# 3. Node operators: remove the deprecated CLI flag.
#    # Old startup command (will break):
#    # tempo-node --enable-subblocks --rpc-port 9933 --chain mainnet
#
#    # Updated startup command:
#    # tempo-node --rpc-port 9933 --chain mainnet
#    #
#    # Subblocks are now enabled by default — no flag needed.
#    # Grep your scripts and systemd units:
#    # grep -r "enable-subblocks" /etc/tempo/ ~/.tempo/ scripts/