fix: archive detection for chains with late EVM activation - #322
Merged
Conversation
Bittensor got its EVM runtime (spec 210) at finney block 4345556, so the archive probe at block 10000 always fails, leaving true archive nodes marked non-archive. Use a chain-specific earliest block, same as Arbitrum Nitro / Optimism Bedrock. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
EugeneDrpc
force-pushed
the
bittensor-archive-detection
branch
from
August 5, 2026 13:09
0e088bb to
e3a2a99
Compare
KirillPamPam
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bittensor got its EVM runtime (spec 210) at finney block 4345556, so state bound 1 is unreachable via detection and the archive probe at block 10000 always fails, leaving true archive nodes marked non-archive.
Mirrors the same fix in dshackle.