Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blocks zero and one become inaccessible after the first root is set #23853

Closed
steveluscher opened this issue Mar 22, 2022 · 0 comments · Fixed by #24760
Closed

Blocks zero and one become inaccessible after the first root is set #23853

steveluscher opened this issue Mar 22, 2022 · 0 comments · Fixed by #24760
Assignees

Comments

@steveluscher
Copy link
Contributor

Problem

Starting with db9826c the first two blocks become inaccessible after we set the first root. 32 confirmations after starting the test validator, solana first-available-block returns 2.

@t-nelson confirmed this by querying for blocks 0 and 1 in a loop after starting up the test validator (logs).

After ~13s, those blocks become inaccessible.

Error: RPC response error -32001: Block 1 cleaned up, does not exist on node. First available block: 2
Error: RPC response error -32001: Block 0 cleaned up, does not exist on node. First available block: 2

Proposed Solution

@t-nelson suggested that genesis should be implicitly rooted (discord); that this code needs to consider querying genesis (link).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants