dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full [2020/05/07 18:07] nick ↷ Page moved from dido:public:ra.1.intro:1_views:3_taxonomic:3_node_tax:full to dido:public:ra.1.intro:2_views:3_taxonomic:3_node_tax:full |
dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full [2022/05/27 20:09] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 2.3.3.1 Full Node ====== | ====== 2.3.3.1 Full Node ====== | ||
| - | [[dido:public:ra.1.intro:1_views:3_taxonomic:3_node_tax|return to Node Taxonomy ]] | + | [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:start|return to Node Taxonomy ]] |
| - | **Full Nodes** keep a full copy of the blockchain transactions(( | + | **[[dido:public:ra:xapend:xapend.a_glossary:f:full|Full nodes]]** keep a full copy of the [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]] transactions(( |
| Osita Chibuike, 21 May 2018, Legobox, | Osita Chibuike, 21 May 2018, Legobox, | ||
| [[https://dev.to/legobox/how-to-setup-an-ethereum-node-41a7]] | [[https://dev.to/legobox/how-to-setup-an-ethereum-node-41a7]] | ||
| - | )). There can be any number of Full Nodes within the Node Network, all acting as redundant data sources. Some of the activities of a Full Node maintaining consensus between other nodes, verification of transactions, and storing the Ledger. | + | )). There can be any number of full nodes within the [[dido:public:ra:xapend:xapend.a_glossary:n:node_network|node network]], all acting as redundant data sources. Some of the activities of a full node are maintaining consensus between other [[dido:public:ra:xapend:xapend.a_glossary:n:node|nodes]], verification of transactions, and storing the [[dido:public:ra:xapend:xapend.a_glossary:l:ledger|ledger]]. |
| - | In many ways the Full Nodes' functionality is analogous to those of servers in decentralized networks. However, there is no centralized "truth" or final judge. Instead, the "truth" is determined by consensus amongst the full nodes. However, this consensus based methodology is not without its pitfalls. When more than 51% of the Full Nodes cannot reach consensus (i.e., agree with a transaction or a proposition), the proposed change is skipped. This can lead to a [[dido:public:xapend.glossary:h:hard_fork]] in the Ledger and the opposing groups diverge, creating two or more chains (( | + | In many ways, the full nodes' functionality is analogous to those of servers in decentralized networks. However, there is no centralized "truth" or final judge. Instead, the "truth" is determined by consensus among the full nodes. However, this consensus-based methodology is not without its pitfalls. When more than 51% of the full nodes cannot reach a consensus (i.e., agree with a transaction or a proposition), the proposed change is skipped. This can lead to a [[dido:public:ra:xapend:xapend.a_glossary:h:hard_fork]] in the ledger and the opposing groups diverge, creating two or more chains (( |
| "Blockchain Nodes: An In-Depth Guide", [[https://nodes.com/]] | "Blockchain Nodes: An In-Depth Guide", [[https://nodes.com/]] | ||
| - | )). Sometimes the 51% problem can be part of an orchestrated effort, referred to as a 51% Attack (( | + | )). Sometimes the 51% problem can be part of an orchestrated effort, referred to as a 51% attack (( |
| - | "51% Attack", Jake Frankenfield, 6 May, 2019, | + | "51% Attack", Jake Frankenfield, 6 May 2019, |
| [[https://www.investopedia.com/terms/1/51-attack.asp]] | [[https://www.investopedia.com/terms/1/51-attack.asp]] | ||
| - | )). The more Nodes in the Node Network, the harder it is to successfully launch a 51% Attack. | + | )). The more nodes in the node network, the harder it is to successfully launch a 51% attack. |
| - | A well-known example of this kind of Ledger divergence, leading to a hard fork, was the Bitcoin Cash Fork.(( | + | A well-known example of this kind of ledger divergence, leading to a hard fork, was the [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]] Cash Fork.(( |
| "Bitcoin Cash’s Scheduled Hard Fork Tripped Up By Software Bug", Christine Kim, 15 May 2019, | "Bitcoin Cash’s Scheduled Hard Fork Tripped Up By Software Bug", Christine Kim, 15 May 2019, | ||
| [[https://www.coindesk.com/bitcoin-cash-scheduled-hard-fork-tripped-up-by-software-bug]] | [[https://www.coindesk.com/bitcoin-cash-scheduled-hard-fork-tripped-up-by-software-bug]] | ||
| Line 20: | Line 20: | ||
| Full node contains: | Full node contains: | ||
| - | * [[dido:public:ra.1.intro:1_views:3_taxonomic:3_node_tax:full:pruned]] | + | * [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:pruned]] |
| - | * [[dido:public:ra.1.intro:1_views:3_taxonomic:3_node_tax:full:archival]] | + | * [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:archival]] |
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/1.2_views/3_taxonomic/3_node_tax/full.1588889277.txt.gz · Last modified: 2020/05/07 18:07 by nick
