mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-27 23:04:05 -06:00
vault backup: 2022-12-13 15:47:31
This commit is contained in:
parent
8077d6b319
commit
2da66cf206
@ -12,6 +12,12 @@ This is the algorthm used in Hyperledger Iroha.
|
||||
|
||||
# Extracts
|
||||
|
||||
1. A client forms a transaction with commands and signs it with their private key.
|
||||
2. The client sends the transaction to a peer. The peer receives the transaction, performs stateless validation (i.e., verifies that it is not malformed), and relays it to the OS.
|
||||
3. The OS generates a proposal and sends it to the peers. The proposal contains an ordered list of transactions that will be potentially added to the blockchain in this round.
|
||||
4. The proposal is sent to the voting peers. Peers enter the collaboration phase, during which they exchange votes across the network and decide on a block. More details on the collaboration phase are provided in Section V.
|
||||
5. The peer commits the block to their local block store.
|
||||
|
||||
# Notes
|
||||
Consensus [7] should guarantee liveness of the system, security, and convergence (consistency) of data stored in the ledger
|
||||
|
||||
|
||||
13
content/notes/YAC.md
Normal file
13
content/notes/YAC.md
Normal file
@ -0,0 +1,13 @@
|
||||
---
|
||||
title: YAC"
|
||||
tags:
|
||||
- algorithm
|
||||
---
|
||||
|
||||
paper: [[YAC — BFT Consensus Algorithm for Blockchain]]
|
||||
|
||||
1. A client forms a transaction with commands and signs it with their private key.
|
||||
2. The client sends the transaction to a peer. The peer receives the transaction, performs stateless validation (i.e., verifies that it is not malformed), and relays it to the OS.
|
||||
3. The OS generates a proposal and sends it to the peers. The proposal contains an ordered list of transactions that will be potentially added to the blockchain in this round.
|
||||
4. The proposal is sent to the voting peers. Peers enter the collaboration phase, during which they exchange votes across the network and decide on a block. More details on the collaboration phase are provided in Section V.
|
||||
5. The peer commits the block to their local block store.
|
||||
@ -21,6 +21,8 @@ tags:
|
||||
|
||||
**Decision problem:** In computability theory and computational complexity theory, a decision problem is a computational problem that can be posed as a yes–no question of the input values.
|
||||
|
||||
**Stateless Validation**: Verifying that a transaction is not malformed
|
||||
|
||||
**:**
|
||||
|
||||
**:**
|
||||
|
||||
@ -19,7 +19,13 @@ BFT/CFT
|
||||
Algorithms
|
||||
- PoW: Bitcoin
|
||||
- PoS: [[ethereum]]
|
||||
- YAC: [[hyperledger#Iroha]]
|
||||
- [[YAC]]: [[hyperledger#Iroha]]
|
||||
|
||||
|
||||
[^7]: L. Lamport, “Generalized consensus and paxos,” Technical Report MSR-TR-2005-33, Microsoft Research, Tech. Rep., 2005. [Online]. Available: https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/tr-2005-33.pdf
|
||||
[^7]: L. Lamport, “Generalized consensus and paxos,” Technical Report MSR-TR-2005-33, Microsoft Research, Tech. Rep., 2005. [Online]. Available: https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/tr-2005-33.pdf
|
||||
|
||||
|
||||
# Components
|
||||
- Peer
|
||||
- Ordering service
|
||||
- Client
|
||||
Loading…
Reference in New Issue
Block a user