From b6b9cbc40f50943dad06c20d24684a27636479b4 Mon Sep 17 00:00:00 2001 From: IkerAlus <34474035+IkerAlus@users.noreply.github.com> Date: Mon, 20 Nov 2023 15:27:49 +0100 Subject: [PATCH 1/3] Add archive node description The description for archive nodes was missing. --- src/grouping-functions-and-node-capabilities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/grouping-functions-and-node-capabilities.md b/src/grouping-functions-and-node-capabilities.md index 60f68d7..d7ccff8 100644 --- a/src/grouping-functions-and-node-capabilities.md +++ b/src/grouping-functions-and-node-capabilities.md @@ -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 and bodies, plus the 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. From 07a242d3cfbec11ff39849724dd43b46513f199f Mon Sep 17 00:00:00 2001 From: IkerAlus <34474035+IkerAlus@users.noreply.github.com> Date: Mon, 20 Nov 2023 17:35:54 +0100 Subject: [PATCH 2/3] Change full node description as suggested --- src/grouping-functions-and-node-capabilities.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/grouping-functions-and-node-capabilities.md b/src/grouping-functions-and-node-capabilities.md index d7ccff8..ba166c1 100644 --- a/src/grouping-functions-and-node-capabilities.md +++ b/src/grouping-functions-and-node-capabilities.md @@ -8,9 +8,9 @@ The group a JSON-RPC function belongs to is indicated by the `prefix_` in its na 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. +- 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). - Light clients, which only know the headers of recent blocks. -- Archive nodes, which hold in their database all block headers and bodies, plus the storage of every past block. +- 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. From 8c907be4814e8e01696ef26b59f0f8edb7ec90ca Mon Sep 17 00:00:00 2001 From: IkerAlus <34474035+IkerAlus@users.noreply.github.com> Date: Mon, 20 Nov 2023 18:18:37 +0100 Subject: [PATCH 3/3] accept tomaka's suggestion Co-authored-by: Pierre Krieger --- src/grouping-functions-and-node-capabilities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/grouping-functions-and-node-capabilities.md b/src/grouping-functions-and-node-capabilities.md index ba166c1..beba365 100644 --- a/src/grouping-functions-and-node-capabilities.md +++ b/src/grouping-functions-and-node-capabilities.md @@ -8,7 +8,7 @@ The group a JSON-RPC function belongs to is indicated by the `prefix_` in its na This JSON-RPC interface is intended to be implemented on various types of nodes: -- 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). +- 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 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.