Skip to content

Add archive node description #114

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Nov 20, 2023
Merged

Add archive node description #114

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b6b9cbc
Add archive node description
IkerAlus Nov 20, 2023
07a242d
Change full node description as suggested
IkerAlus Nov 20, 2023
8c907be
accept tomaka's suggestion
IkerAlus Nov 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/grouping-functions-and-node-capabilities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This JSON-RPC interface is intended to be implemented on various types of nodes:

- 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, bodies, and storage of every past block.
- Plain databases that aren't actually connected to the peer-to-peer network of the blockchain.

These various node implementations have different capabilities, and it is normal for some implementations to only support some functions and not others. It doesn't make sense for example for a light client to support a function that rotates keys.
Expand Down