dido:public:ra:1.4_req:1_func:access
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.4_req:1_func:access [2021/08/11 13:15] murphy |
dido:public:ra:1.4_req:1_func:access [2022/01/15 18:22] (current) nick |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[dido:public:ra:1.4_req:1_func:access | Return to Functional Requirements]] | [[dido:public:ra:1.4_req:1_func:access | Return to Functional Requirements]] | ||
| - | A major functional requirement is to provide a classifications of allowable [[dido:public:ra:xapend:xapend.a_glossary:n:node|nodes]] within the DIDO network. A detailed explanation of DIDO networks is provided by in [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll | Network Access Control]]. | + | A major functional requirement is to provide a classifications of allowable [[dido:public:ra:xapend:xapend.a_glossary:n:node|nodes]] within the DIDO network. A detailed explanation of DIDO networks is provided by in [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:start| Network Access Control]]. |
| Within each of these two classifications it is possible to have | Within each of these two classifications it is possible to have | ||
| Line 47: | Line 47: | ||
| [[https://medium.com/@akadiyala/nuances-between-permissionless-and-permissioned-blockchains-f5b566f5d483]] | [[https://medium.com/@akadiyala/nuances-between-permissionless-and-permissioned-blockchains-f5b566f5d483]] | ||
| )). | )). | ||
| - | * **Permissioned** - Transparency is not a driving force in permissioned networks and is often a major factor in the business decision to choose permissioned over permissionless networks. Most permissioned blockchains do not use cryptoeconomic [[dido:public:ra:xapend:xapend.a_glossary:c:coins|coins]] incentive or tokens. The primary incentive of permissioned blockchain participants is to minimize the transparency, cost, time, and ease of sharing information3). | + | * **Permissioned** - Transparency is not a driving force in permissioned networks and is often a major factor in the business decision to choose permissioned over permissionless networks. Most permissioned blockchains do not use cryptoeconomic [[dido:public:ra:xapend:xapend.a_glossary:c:coins|coins]] incentive or [[dido:public:ra:xapend:xapend.a_glossary:t:tokens|tokens]]. The primary incentive of permissioned blockchain participants is to minimize the transparency, cost, time, and ease of sharing information3). |
| </WRAP> | | </WRAP> | | ||
| ^ Privacy/Anonymity | | <WRAP> | ^ Privacy/Anonymity | | <WRAP> | ||
| Line 64: | Line 64: | ||
| </WRAP> | | </WRAP> | | ||
| ^ Governance | | <WRAP> | ^ Governance | | <WRAP> | ||
| - | * **Permisionless** - As a general rule, permissionless networks rely on [[dido:public:ra:xapend:xapend.a_glossary:o:oss|open source software]], which is ruled by open source communities (see [[dido:public:ra:xapend:xapend.b_stds:defact:todo]]). The governance of the network is by consensus. [[dido:public:ra:xapend:xapend.a_glossary:c:consensus_algorithm| Consensus]] is different for many of the permissionless networksm(i.e., [[dido:public:ra:xapend:xapend.a_glossary:p:proof_of_work]], [[dido:public:ra:xapend:xapend.a_glossary:p:proof_of_stake_pos]], [[dido:public:ra:xapend:xapend.a_glossary:p:proof_of_authority_poa]], etc). (( | + | * **Permisionless** - As a general rule, permissionless networks rely on [[dido:public:ra:xapend:xapend.a_glossary:o:oss|open source software]], which is ruled by open source communities (see [[dido:public:ra:xapend:xapend.b_stds:defact:todo:start]]). The [[dido:public:ra:xapend:xapend.a_glossary:g:governance]] of the network is by consensus. [[dido:public:ra:xapend:xapend.a_glossary:c:consensus_algorithm| Consensus]] is different for many of the permissionless networksm(i.e., [[dido:public:ra:xapend:xapend.a_glossary:p:proof_of_work]], [[dido:public:ra:xapend:xapend.a_glossary:p:proof_of_stake_pos]], [[dido:public:ra:xapend:xapend.a_glossary:p:proof_of_authority_poa]], etc). (( |
| "Nuances Between Permissionless and Permissioned Blockchains", | "Nuances Between Permissionless and Permissioned Blockchains", | ||
| Anant Kadiyala, | Anant Kadiyala, | ||
| Line 70: | Line 70: | ||
| [[https://medium.com/@akadiyala/nuances-between-permissionless-and-permissioned-blockchains-f5b566f5d483]] | [[https://medium.com/@akadiyala/nuances-between-permissionless-and-permissioned-blockchains-f5b566f5d483]] | ||
| )) | )) | ||
| - | * **Permissioned** - There are fundamental differences between [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:permisionless| permissionless]] and permissioned network governance. Permissioned governance is decided and agreed upon by members of the business network. Economic incentives, code quality, code changes, and power allocation among peers are based on the business dynamics and the common purpose and goals of the permissioned members. This allows for agile and responsive networks desired by businesses(( | + | * **Permissioned** - There are fundamental differences between [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:permisionless| permissionless]] and permissioned network [[dido:public:ra:xapend:xapend.a_glossary:g:governance]]. Permissioned governance is decided and agreed upon by members of the business network. Economic incentives, code quality, code changes, and power allocation among peers are based on the business dynamics and the common purpose and goals of the permissioned members. This allows for agile and responsive networks desired by businesses(( |
| "Nuances Between Permissionless and Permissioned Blockchains", | "Nuances Between Permissionless and Permissioned Blockchains", | ||
| Anant Kadiyala, | Anant Kadiyala, | ||
| Line 92: | Line 92: | ||
| </WRAP> | | </WRAP> | | ||
| ^ Scalability & Performance | | <WRAP> | ^ Scalability & Performance | | <WRAP> | ||
| - | * **Permisionless** - For all the value blockchains bring to modern business processes, their Achilles heel often involves scalability and performance. Both Bitcoin and [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum|Ethereum]] blockchains suffer from poor scores in this area. For example, a recent blockchain game called Crypto kittles clogged the Ethereum network. Having said that, these are just early teething troubles, and startups are experimenting with various strategies to address this issue. Hopefully it is only a matter of time before this issue becomes a non-entity.(( | + | * **Permisionless** - For all the value blockchains bring to modern business processes, their Achilles heel often involves [[dido:public:ra:xapend:xapend.a_glossary:s:scalable|scalability]] and [[dido:public:ra:xapend:xapend.a_glossary:p:performance|performance]]. Both Bitcoin and [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum|Ethereum]] blockchains suffer from poor scores in this area. For example, a recent blockchain game called Crypto kittles clogged the Ethereum network. Having said that, these are just early teething troubles, and startups are experimenting with various strategies to address this issue. Hopefully it is only a matter of time before this issue becomes a non-entity.(( |
| "Nuances Between Permissionless and Permissioned Blockchains", | "Nuances Between Permissionless and Permissioned Blockchains", | ||
| Anant Kadiyala, | Anant Kadiyala, | ||
| Line 112: | Line 112: | ||
| </WRAP> | | </WRAP> | | ||
| ^ Ledger Is Distributed | | <WRAP> | ^ Ledger Is Distributed | | <WRAP> | ||
| - | * **Public** - The database is not centralized like in a [[dido:public:ra:xapend:xapend.a_glossary:c:client-server|client-server]] approach, and all nodes in the blockchain participate in the transaction validation.(("Public Vs Private Blockchain In A Nutshell", | + | * **Public** - The database is not centralized like in a [[dido:public:ra:xapend:xapend.a_glossary:c:client-server|client-server]] approach, and all nodes in the blockchain participate in the transaction [[dido:public:ra:xapend:xapend.a_glossary:v:validation|validation]].(("Public Vs Private Blockchain In A Nutshell", |
| Demiro Massessi, 12 December 2018, | Demiro Massessi, 12 December 2018, | ||
| [[https://medium.com/coinmonks/public-vs-private-blockchain-in-a-nutshell-c9fe284fa39f]] | [[https://medium.com/coinmonks/public-vs-private-blockchain-in-a-nutshell-c9fe284fa39f]] | ||
| Line 160: | Line 160: | ||
| </WRAP> | | </WRAP> | | ||
| ^ Private Transactions | | <WRAP> | ^ Private Transactions | | <WRAP> | ||
| - | * **Hybrid** - Transaction are private but verifiable using the ledger's immutable data objects (i.e., leverage its public state). In its public state, each transaction gets approved by a massive network and is essentially secure and trustworthy. Hence, there is no need for a central governing body or an exhaustive chain of intermediaries to supervise things. So, any change done to a transaction will undergo a "kindred" approval process, making it next to impossible for a single actor to meddle with the transaction or entries(( | + | * **Hybrid** - Transaction are private but verifiable using the ledger's immutable data objects (i.e., leverage its public state). In its public state, each transaction gets approved by a massive network and is essentially secure and trustworthy. Hence, there is no need for a central [[dido:public:ra:xapend:xapend.a_glossary:g:gov_body]] or an exhaustive chain of intermediaries to supervise things. So, any change done to a transaction will undergo a "kindred" approval process, making it next to impossible for a single actor to meddle with the transaction or entries(( |
| "If you Thought Blockchain was Amazing, Wait till You Read about Hybrid Blockchain", Atul Khekade, 20 January 2018, | "If you Thought Blockchain was Amazing, Wait till You Read about Hybrid Blockchain", Atul Khekade, 20 January 2018, | ||
| [[https://www.entrepreneur.com/article/307794]]. This article uses the term "agnate approval" rather than "kindred approval"; however, [[https://www.dictionary.com/browse/agnate | agnate]] limits a [[https://www.thesaurus.com/browse/agnate|kindred]] relationship to males only. Thus, we prefer the term "kindred" over "agnate" | [[https://www.entrepreneur.com/article/307794]]. This article uses the term "agnate approval" rather than "kindred approval"; however, [[https://www.dictionary.com/browse/agnate | agnate]] limits a [[https://www.thesaurus.com/browse/agnate|kindred]] relationship to males only. Thus, we prefer the term "kindred" over "agnate" | ||
dido/public/ra/1.4_req/1_func/access.1628702152.txt.gz · Last modified: 2021/08/11 13:15 by murphy
