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:archival:1_authority [2020/05/07 18:56] nick ↷ Links adapted because of a move operation |
dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:archival:1_authority [2021/11/09 15:51] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:archival|return to Archival Node]] | [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:archival|return to Archival Node]] | ||
| - | The Network Nodes traditionally join a network and perform tasks without anyone or anything granting permission to join the Node Network. Having permissionless access to a Node Network is one of the original guiding principles that is integral to the decentralized nature of DIDOs(( | + | Traditionally, the participation in [[dido:public:ra:xapend:xapend.a_glossary:n:node_network| DIDO node networks]] to perform tasks is [[dido:public:ra:xapend:xapend.a_glossary:p:permissionless|permissionless]], requiring no outside authority from anyone or anything. Having permissionless access to a [[dido:public:ra:xapend:xapend.a_glossary:n:node|node]] network is one of the original guiding principles that is integral to the decentralized nature of DIDOs(( |
| S. Nakamoto, "Bitcoin: A Peer-to-Peer Electronic Cash System," 24 May 2009. [Online]. Available: [[https://bitcoin.org/bitcoin.pdf]]. | S. Nakamoto, "Bitcoin: A Peer-to-Peer Electronic Cash System," 24 May 2009. [Online]. Available: [[https://bitcoin.org/bitcoin.pdf]]. | ||
| )). | )). | ||
| - | :**Note:** | + | :**Note:** Unfortunately, there are drawbacks to this approach. Solutions involving a level of centralization for granting permission can provide benefits like increased speed because there is no need for the costly, time consuming consensus algorithms such as [[dido:public:ra:xapend:xapend.a_glossary:d:delegated_proof_of_stake_dpos]], [[dido:public:ra:xapend:xapend.a_glossary:d:delegated_byzantine]], [[dido:public:ra:xapend:xapend.a_glossary:p:proof_of_authority_poa]] and others. However, centralized permissioned systems are vulnerable to malicious attacks such as denial of service, thereby undermining many of the "democratizing" aspects of the DIDO. |
| - | : Unfortunately, there are drawbacks to this approach; solutions involving a level of centralization for granting permission can provide benefits like increased speed. **<todo>Not sure I interpreted and fixed this correctly. The way it was written made no sense. Are we saying that solutions based on consensus are inherently slower than those which centralize the permission granting process? I would think that reaching consensus is inherently a slow complicated process because who in the end declares that consensus has been reached? are the algorithms listed here used in place of a centralized authority? </todo**>Consensus algorithms include [[dido:public:ra:xapend.glossary:d:delegated_proof_of_stake_dpos]], [[dido:public:ra:xapend.glossary:d:delegated_byzantine]], [[dido:public:ra:xapend.glossary:p:proof_of_authority_poa]] and others. | + | |
| - | Networks making use of [[dido:public:ra:xapend.glossary:p:proof_of_authority_poa]] Networks define a fixed number of **Authority Nodes**. The number of Nodes and associated PoA designation is voted on by the PoA community or defined by the development team. Authority Nodes are similar to [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full|Full Nodes]] and can create and validate blocks. All other Nodes in the Node Network run as [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:lite|Lightweight Nodes]], depending on broadcasted data to participate in the blockchain.(( | + | Networks making use of PoA networks define a fixed number of **authority nodes**. The number of nodes and associated PoA designation is voted on by the PoA community or defined by the development team. Authority nodes are similar to [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full|full nodes]] and can create and validate blocks. All other nodes in the node network run as [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:lite|lightweight nodes]], depending on broadcasted data to participate in the [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]].(( |
| "Blockchain Nodes: An In-Depth Guide", [[https://nodes.com/]] | "Blockchain Nodes: An In-Depth Guide", [[https://nodes.com/]] | ||
| )) | )) | ||
| - | [[dido:public:ra:xapend.stds:defact:iota| Iota]] refers to Authority Nodes as **Permanodes** ([[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:perma|definition]]) because they keep all transaction data even after [[dido:public:ra:xapend.glossary:s:snapshot| snapshots]] are made (concept introduced by Iota (("Full node vs permanode", Helmar, 5 January 2018, [[https://iota.stackexchange.com/questions/782/full-node-vs-permanode/783]]))) | + | [[dido:public:ra:xapend:xapend.b_stds:defact:iota:start| Iota]] refers to authority nodes as **permanodes** ([[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:perma|definition]]) because they keep all transaction data even after [[dido:public:ra:xapend:xapend.a_glossary:s:snapshot| snapshots]] are made (concept introduced by Iota (("Full node vs permanode", Helmar, 5 January 2018, [[https://iota.stackexchange.com/questions/782/full-node-vs-permanode/783]]))) |
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||