dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:pruned
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:pruned [2021/08/11 10:45] murphy |
dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:pruned [2022/05/27 20:12] (current) nick grammar |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| A **pruned node** is a [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full|full node]] for all intents and purposes with one major difference: in order to save space on the [[dido:public:ra:xapend:xapend.a_glossary:n:node|node]], the pruned node begins downloading blocks from the beginning of the [[dido:public:ra:xapend:xapend.a_glossary:l:ledger|ledger]] and when a preset threshold on space is exceeded, the oldest transactions are deleted, retaining only the headers and placement within the [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]]. | A **pruned node** is a [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full|full node]] for all intents and purposes with one major difference: in order to save space on the [[dido:public:ra:xapend:xapend.a_glossary:n:node|node]], the pruned node begins downloading blocks from the beginning of the [[dido:public:ra:xapend:xapend.a_glossary:l:ledger|ledger]] and when a preset threshold on space is exceeded, the oldest transactions are deleted, retaining only the headers and placement within the [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]]. | ||
| - | For example, a size limit threshold of 550MB allows storage of the latest blocks that fit within the 550MB threshold. However, to retain the integrity of the ledger, all the transactions must be processed and checked for validity in the order of their creation. At the end of the load, the state of the data is correct and only the history is of the transactions is lost.(( | + | For example, a size limit threshold of 550MB allows storage of the latest blocks that fit within the 550MB threshold. However, to retain the integrity of the ledger, all the transactions must be processed and checked for validity in the order of their creation. At the end of the load, the state of the data is correct and only the history of the transactions is lost. (( |
| "Blockchain Nodes: An In-Depth Guide", [[https://nodes.com/]] | "Blockchain Nodes: An In-Depth Guide", [[https://nodes.com/]] | ||
| )) | )) | ||
dido/public/ra/1.2_views/3_taxonomic/3_node_tax/full/pruned.1628693148.txt.gz · Last modified: 2021/08/11 10:45 by murphy
