Skip to content

fix: archive detection for chains with late EVM activation - #322

Merged
EugeneDrpc merged 2 commits into
mainfrom
bittensor-archive-detection
Aug 5, 2026
Merged

fix: archive detection for chains with late EVM activation#322
EugeneDrpc merged 2 commits into
mainfrom
bittensor-archive-detection

Conversation

@EugeneDrpc

Copy link
Copy Markdown
Contributor

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.

  • eth archive detector: chain-specific earliest block for Bittensor, same as Arbitrum Nitro / Optimism Bedrock
  • gold bounds: support block-only STATE gold bound - state present at the gold block reports bound 1 (mirrors the tx/receipts short-circuit)

Mirrors the same fix in dshackle.

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
EugeneDrpc force-pushed the bittensor-archive-detection branch from 0e088bb to e3a2a99 Compare August 5, 2026 13:09
@EugeneDrpc EugeneDrpc changed the title wip: fix: archive detection for chains with late EVM activation fix: archive detection for chains with late EVM activation Aug 5, 2026
@EugeneDrpc
EugeneDrpc merged commit b4c326a into main Aug 5, 2026
4 of 5 checks passed
@EugeneDrpc
EugeneDrpc deleted the bittensor-archive-detection branch August 5, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants