-
Notifications
You must be signed in to change notification settings - Fork 92
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
Clarification of the snapshots #348
Comments
Basically, you are right, I can update these clarification into the FAQ. |
@zzzckck Which snapshot shall I use if I want to access more than 128 blocks live state? Or is that possible? |
right now, I am afraid only Erigon archive node can support it, PBSS only keeps the most recent 128+1 state. |
Cool, thanks for the explanation. Will the hash-based scheme be deprecated finally? |
It is not determined yet, currently we just make sure hash-based function will not be broken, but in long run, if it could be deprecated if it needs too much effort to maintain it. |
I'm trying to understand what these snapshots contain. Although there are already many discussions on this, I don't see a clarification or comparison and thus I'm trying to do it. My understanding of geth is limited so please correct me if anything is wrong.
=========
Some definitions:
state
: Contract state variables valueblock
: Bodies, contains the properties of a transaction likefrom
,to
...receipts
: Execution results and logsheader
: Properties of blocks, likehash
,number
...=========
Full node snapshots of this repo (2.4T roughly):
From #340
state
: Only recent 90k blocksblock
: Full chainreceipts
: Full chainheader
: Full chainFull node snapshots of 48Club (800G roughly):
state
: Only recent 128 blocks. <---- Just confirmed with this. But with--tries-verify-mode=none
, state beyond 128 blocks will return missing trie node.block
: Only recent 90k blocksreceipts
: Only recent 90k blocksheader
: Only recent 90k blocksFast node snapshots of 48Club (200G roughly):
state
: Only recent 128 blocks. <----- I'm running a fast node indeed and find this. And most importantly, if the state is not available, RPC won't report an error and returns 0!block
: Only recent 90k blocksreceipts
: Only recent 90k blocksheader
: Only recent 90k blocksErigon Snapshots (~8T):
state
: Full chainblock
: Full chainreceipts
: Full chainheader
: Full chainPlease clarify if these understand is correct.
=======
cc
@du5
@zzzckck
The text was updated successfully, but these errors were encountered: