vault backup: 2022-11-17 13:05:29

This commit is contained in:
Jet Hughes 2022-11-17 13:05:29 +13:00
parent e9b7d81c94
commit 78931e3563
4 changed files with 43 additions and 1 deletions

View File

@ -30,6 +30,9 @@ Blockchain technology falls into two distinct classes: open (permissionless) blo
- [dApps](notes/dApps.md)
- [sybil-problem](notes/sybil-problem.md)
- [smart-contracts](smart-contracts.md)
- [transaction-finality](transaction-finality.md)
- [consensus](notes/consensus.md)
- [CPR-governance](notes/CPR-governance.md)
# Reading
- https://coopahtroopa.mirror.xyz/_EDyn4cs9tDoOxNGZLfKL7JjLo5rGkkEfRa_a-6VEWw
@ -52,6 +55,7 @@ Blockchain technology falls into two distinct classes: open (permissionless) blo
- https://www.investopedia.com/news/public-private-permissioned-blockchains-compared/
- https://www.forbes.com/sites/forbestechcouncil/2019/06/11/public-vs-private-permissioned-ledgers-and-blockchain-standards/?sh=39aaa258550b
- https://www.linkedin.com/pulse/public-permissioned-blockchains-common-pool-resources-jesus-ruiz/
- https://smithandcrown.com/glossary/transaction-finality-probabilisticdeterministic/
- https://www.mas.gov.sg/schemes-and-initiatives/project-ubin
- https://alastria.io/en/what-is-alastria/

View File

@ -0,0 +1,17 @@
---
title: "consensus"
tags:
---
> The consensus algorithm takes care of the transaction verification within the network. Different blockchain systems implement different consensus algorithms which can benefit the miners directly or indirectly. Some of the popular consensus algorithms include Proof-of-Work(PoW), Proof-of-Stake(PoS), and so on.
> You can think of it as hierarchical centralization when compared to traditional governance.
> — https://101blockchains.com/blockchain-governance/
Algorithms
- PoW
- PoS
- BFT
- Paxos
- etc

View File

@ -82,5 +82,12 @@ Permissioned (public) blockchains allow "anyone to join the permissioned network
https://sovrin.org example of a public permissioned blockchain. it is a public service utility enabling self-sovereign identity on the internet. it is based on hyperledger indy. interesting but doesn't really help me.
https://www.academia.edu/41965099/Public_Permissioned_blockchains_as_Common_Pool_Resources (writtenseems like a very relevant article. It describes a public-permissioned blockchain, with decentralised governance. It likens managing a public permissionless blockchain to managing common pool resources. One of the issues with managing CPRs is developing the required trust. However, with blockchain technology, you can encode goverance rules directly into the infrastructure which are immutable, transparent and automatic. this is [On chain governance](notes/governance.md#On%20chain%20governance)
https://www.academia.edu/41965099/Public_Permissioned_blockchains_as_Common_Pool_Resources (written by the CTO of alastria) seems like a very relevant article. It describes a public-permissioned blockchain, with decentralised governance. It likens managing a public permissionless blockchain to managing common pool resources. One of the issues with managing CPRs is developing the required trust. However, with blockchain technology, you can encode goverance rules directly into the infrastructure which are immutable, transparent and automatic. this is [On chain governance](notes/governance.md#On%20chain%20governance). This can be used to implement the rules of [CPR-governance](notes/CPR-governance.md) outlined by Ostram.
[transaction-finality](notes/transaction-finality.md)
two types of nodes in a permissioned blockchain network:
- Consensus nodes**: are responsible for the execution of the consensus algorithm
- Regular nodes**: perform the maintenance of a local copy of the blockchain using the blocks generated from the set of consensus nodes.

View File

@ -0,0 +1,14 @@
---
title: "transaction-finality"
tags:
---
https://smithandcrown.com/glossary/transaction-finality-probabilisticdeterministic/
Generally, transaction finality refers to the moment when parties involved in a transaction can consider the transaction to be completed. More specifically, this is the moment when it becomes impossible to revert or alter a transaction that has been added to the [blockchain](https://smithandcrown.com/glossary/blockchain). Transaction finality can be either deterministic or probabilistic.
Probabilistic finality occurs when a transactions finality increases as more blocks are added to the blockchain after the transaction. That is, as more blocks are added, the transaction is further referenced in the blockchain and becomes increasingly difficult to revert or alter as a result (see [Double Spend](https://smithandcrown.com/glossary/double-spend)). For most protocols providing probabilistic finality, there is a recommended number of blocks to be added following the transaction until it can be considered complete. For example, it is recommended that one wait until six additional blocks have been added to the [Bitcoin](https://smithandcrown.com/projects/bitcoin) blockchain before considering a transaction to be final. The majority of major cryptoassets offer probabilistic finality.
Deterministic finality occurs when a transaction is immediately considered to be final once it is added to the blockchain. For this to happen, a “leader” must propose a block to be added, and then a specified portion of validators must approve it. Deterministic finality is less common and is only provided by Practical Byzantine Fault Tolerance-based (PBFT) protocols such as Tendermint