Base network: scheduled maintenance for v1.5.3 node upgrade

Base completed scheduled maintenance to patch a Reth-derived bug that could cause nodes to compute an incorrect state root; the chain's state root was verified correct throughout and users were not affected. Node operators are recommended to upgrade to v1.5.3, though no resync or other action is required. Upstream incident: https://base-l2.statuspage.io/incidents/zmn7dfmyc862

Base identified a bug inherited from Reth that could cause nodes to compute an incorrect state root; the chain's actual state was verified correct and users were not impacted. Base has now released v1.5.3, which removes the halt risk, and recommends all node operators upgrade as soon as possible. Upstream incident: https://base-l2.statuspage.io/incidents/zmn7dfmyc862

Base's scheduled rollout of v1.5.3, which fixes a potential Reth-derived state root mismatch bug, is still in progress as of 17:52 UTC on November 5. The underlying issue was already mitigated at the block-builder level and Base's independent proof system confirmed no incorrect state roots were produced, so mainnet users were not impacted; upgrading is recommended for node operators but no action is required. Upstream incident: https://base-l2.statuspage.io/incidents/zmn7dfmyc862

Base published v1.5.3, a scheduled node software upgrade fixing a bug where validator nodes could fail to process a block due to a state root mismatch. The maintenance rollout is currently in progress on mainnet; no customer-facing disruption is expected while node operators upgrade. Upstream incident: https://base-l2.statuspage.io/incidents/zmn7dfmyc862

Base published v1.5.3, a scheduled node software upgrade fixing a bug where validator nodes could fail to process a block due to a state root mismatch. The maintenance rollout is currently in progress on mainnet; no customer-facing disruption is expected while node operators upgrade. Upstream incident: https://base-l2.statuspage.io/incidents/zmn7dfmyc862