Skip to content

Conversation

@IkerAlus
Copy link
Contributor

@IkerAlus IkerAlus commented Nov 20, 2023

The description for archive nodes was missing.

The description for archive nodes was missing.
- Full nodes, which hold in their database all block headers and bodies, plus the storage of recent blocks.
- Light clients, which only know the headers of recent blocks.
- Archive nodes, which hold.
- Archive nodes, which hold in their database all block headers and bodies, plus the storage of every past block.
Copy link
Contributor

@josepot josepot Nov 20, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for noticing this @IkerAlus !

However, I'm afraid that the explanation of "Full nodes" is also off. It should probably say something more or less like:

  • Full nodes, which hold in their database all headers from the genesis block to the most recent block, plus the bodies and storage of the most recent blocks (typically the latest 256).

Basically, I'm quite certain that it's not true that "full nodes" hold all the bodies from genesis. I'm pretty sure that they only store the headers, which is what it's needed to validate that the state is correct.

Then IMO the "Archive nodes" description should read something more or less like this:

  • Archive nodes, which hold in their database all block headers, bodies, and storage of every past block.

Copy link
Contributor Author

@IkerAlus IkerAlus Nov 20, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I think you are right respect to full nodes description.

I will change it as you suggest in this PR. Thanks!

Co-authored-by: Pierre Krieger <pierre.krieger1708@gmail.com>
@josepot josepot merged commit f4b1019 into main Nov 20, 2023
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.

4 participants