dido:public:ra:1.2_views:3_taxonomic:3_node_tax:full:archival:1_authority
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:archival:1_authority [2020/11/13 02:50] 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]] | ||
| - | Traditionally, the participation in [[dido:public:ra:xapend:xapend.a_glossary:n:node_network| DIDO node networks]] to perform tasks is permissionless, requiring no outside authority from anyone or anything. 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]]. | ||
| )). | )). | ||
| Line 8: | Line 8: | ||
| :**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. | :**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. | ||
| - | 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 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:xapend.b_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: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]]))) | + | [[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~~ | ||
dido/public/ra/1.2_views/3_taxonomic/3_node_tax/full/archival/1_authority.1605253830.txt.gz · Last modified: 2020/11/13 02:50 by nick
