Blockchain
Blockdaemon completes Arc node upgrade after a fix for stale reads
The operator marked its maintenance complete on November 14 at 00:30 UTC. Version 0.8.5 of the node software fixes a case in which a read could return an old state for an account recreated within the same block.

Maintenance on Blockdaemon’s nodes
On November 14, 2026, at 00:30 UTC, Blockdaemon said it had finished upgrading its Arc mainnet nodes to version 0.8.5. The maintenance window had begun at 22:30 UTC the previous day. The operator’s notice anticipated up to 15 minutes of downtime per node while applying the update. The start and end times refer to the maintenance window, while the 15 minutes refer to the possible downtime for an individual node during that window.
The notice covers nodes operated by Blockdaemon. Its completion shows where and when that provider made the transition. It provides no deployment schedule for other operators. The software repository shows the version was published on November 13. That release made the fix available, while the maintenance notice provides a record of its installation by a mainnet node operator.
The cache could retain data from before deletion
The flaw affected the execution layer’s cache, which keeps data readily available so the software can avoid reading it from storage on every request. The release notes describe a specific sequence. Within a single block, an account becomes empty and is deleted under the EIP-161 rules, then recreated. In this case, earlier software could leave the account information and storage data from before deletion in its cache. A subsequent read could then return an outdated value.
The test added to the repository reproduces the sequence using an account whose balance is drained and that is then recreated through an EIP-7702 delegation. The delegated code writes a value to a storage slot. The test first caches the value from the parent block’s state and checks that the new state replaces it. It checks what the node returns after processing the block that contains the deletion and recreation.
A software update without a database migration
According to the changelog, version 0.8.5 uses Arc Reth 2.2.0-arc.2. That version incorporates the execution cache fix from the Reth project, from which Arc takes the code for this part of the software. The changelog lists no hard fork activation, meaning an incompatible change to network rules, and no database migration for this release.
The notes recommend that operators upgrade their nodes quickly and avoid running mixed versions for an extended period, because the fix affects cached state. The release, the regression test and the end of maintenance at Blockdaemon document the availability of the fix, the case covered by the test and the rollout at that provider, respectively.
