Hyperledger Fabric v1.3 - Consensus
up vote
0
down vote
favorite
I have a technical doubt related to the HL Fabric consensus.
Does anyone know which is the current consensus algorithm implemented in v1.3? Can you describe it?
Where I can find more documentation about this topic?
hyperledger-fabric
asked Nov 19 at 17:21
Leonardo Carraro
291210
add a comment |
up vote
0
down vote
favorite
I have a technical doubt related to the HL Fabric consensus.
Does anyone know which is the current consensus algorithm implemented in v1.3? Can you describe it?
Where I can find more documentation about this topic?
hyperledger-fabric
asked Nov 19 at 17:21
Leonardo Carraro
291210
for a consensus roadmap also see this, they are implementing raft. jira.hyperledger.org/browse/FAB-6135?jql=labels%20%3D%20raft - "It allows us to have an ordering service without Kafka/ZK depedencies, and It helps with the BFT development as well, since it gives us a chance to hook into Fabric a leader-based consensus protocol and carry those lessons over when writing the BFT plugin."
– Paolo
Nov 21 at 1:45
1
maybe have a look to this one too arxiv.org/pdf/1809.00554.pdf where it starts with "Hyperledger Fabric implements a pluggable consensus on the order of transactions in the..."
– Paolo
Nov 24 at 20:36
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a technical doubt related to the HL Fabric consensus.
Does anyone know which is the current consensus algorithm implemented in v1.3? Can you describe it?
Where I can find more documentation about this topic?
hyperledger-fabric
asked Nov 19 at 17:21
Leonardo Carraro
291210
I have a technical doubt related to the HL Fabric consensus.
Does anyone know which is the current consensus algorithm implemented in v1.3? Can you describe it?
Where I can find more documentation about this topic?
hyperledger-fabric
hyperledger-fabric
asked Nov 19 at 17:21
Leonardo Carraro
291210
asked Nov 19 at 17:21
Leonardo Carraro
291210
asked Nov 19 at 17:21
Leonardo Carraro
291210
asked Nov 19 at 17:21
Leonardo Carraro
291210
asked Nov 19 at 17:21
Leonardo Carraro
291210
291210
for a consensus roadmap also see this, they are implementing raft. jira.hyperledger.org/browse/FAB-6135?jql=labels%20%3D%20raft - "It allows us to have an ordering service without Kafka/ZK depedencies, and It helps with the BFT development as well, since it gives us a chance to hook into Fabric a leader-based consensus protocol and carry those lessons over when writing the BFT plugin."
– Paolo
Nov 21 at 1:45
1
maybe have a look to this one too arxiv.org/pdf/1809.00554.pdf where it starts with "Hyperledger Fabric implements a pluggable consensus on the order of transactions in the..."
– Paolo
Nov 24 at 20:36
add a comment |
for a consensus roadmap also see this, they are implementing raft. jira.hyperledger.org/browse/FAB-6135?jql=labels%20%3D%20raft - "It allows us to have an ordering service without Kafka/ZK depedencies, and It helps with the BFT development as well, since it gives us a chance to hook into Fabric a leader-based consensus protocol and carry those lessons over when writing the BFT plugin."
– Paolo
Nov 21 at 1:45
1
maybe have a look to this one too arxiv.org/pdf/1809.00554.pdf where it starts with "Hyperledger Fabric implements a pluggable consensus on the order of transactions in the..."
– Paolo
Nov 24 at 20:36
for a consensus roadmap also see this, they are implementing raft. jira.hyperledger.org/browse/FAB-6135?jql=labels%20%3D%20raft - "It allows us to have an ordering service without Kafka/ZK depedencies, and It helps with the BFT development as well, since it gives us a chance to hook into Fabric a leader-based consensus protocol and carry those lessons over when writing the BFT plugin."
– Paolo
Nov 21 at 1:45
for a consensus roadmap also see this, they are implementing raft. jira.hyperledger.org/browse/FAB-6135?jql=labels%20%3D%20raft - "It allows us to have an ordering service without Kafka/ZK depedencies, and It helps with the BFT development as well, since it gives us a chance to hook into Fabric a leader-based consensus protocol and carry those lessons over when writing the BFT plugin."
– Paolo
Nov 21 at 1:45
1
1
maybe have a look to this one too arxiv.org/pdf/1809.00554.pdf where it starts with "Hyperledger Fabric implements a pluggable consensus on the order of transactions in the..."
– Paolo
Nov 24 at 20:36
maybe have a look to this one too arxiv.org/pdf/1809.00554.pdf where it starts with "Hyperledger Fabric implements a pluggable consensus on the order of transactions in the..."
– Paolo
Nov 24 at 20:36
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Consensus can be broken into three phases in fabric from v1.0
- Endorsment Policy - For a transaction to be valid, it has to be
endorsed by respective participants. This phase is even before going
to orderer service. - Ordering - Order the transaction in chronological order
- Validation(Commiting peer) - Validate the correctness of state
(Comparison between the transaction state and world state)
A more detail read can be found here https://www.skcript.com/svr/consensus-hyperledger-fabric/
answered Nov 20 at 4:53
Rangesh
58811024
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Consensus can be broken into three phases in fabric from v1.0
- Endorsment Policy - For a transaction to be valid, it has to be
endorsed by respective participants. This phase is even before going
to orderer service. - Ordering - Order the transaction in chronological order
- Validation(Commiting peer) - Validate the correctness of state
(Comparison between the transaction state and world state)
A more detail read can be found here https://www.skcript.com/svr/consensus-hyperledger-fabric/
answered Nov 20 at 4:53
Rangesh
58811024
add a comment |
up vote
1
down vote
Consensus can be broken into three phases in fabric from v1.0
- Endorsment Policy - For a transaction to be valid, it has to be
endorsed by respective participants. This phase is even before going
to orderer service. - Ordering - Order the transaction in chronological order
- Validation(Commiting peer) - Validate the correctness of state
(Comparison between the transaction state and world state)
A more detail read can be found here https://www.skcript.com/svr/consensus-hyperledger-fabric/
answered Nov 20 at 4:53
Rangesh
58811024
add a comment |
up vote
1
down vote
up vote
1
down vote
Consensus can be broken into three phases in fabric from v1.0
- Endorsment Policy - For a transaction to be valid, it has to be
endorsed by respective participants. This phase is even before going
to orderer service. - Ordering - Order the transaction in chronological order
- Validation(Commiting peer) - Validate the correctness of state
(Comparison between the transaction state and world state)
A more detail read can be found here https://www.skcript.com/svr/consensus-hyperledger-fabric/
answered Nov 20 at 4:53
Rangesh
58811024
Consensus can be broken into three phases in fabric from v1.0
- Endorsment Policy - For a transaction to be valid, it has to be
endorsed by respective participants. This phase is even before going
to orderer service. - Ordering - Order the transaction in chronological order
- Validation(Commiting peer) - Validate the correctness of state
(Comparison between the transaction state and world state)
A more detail read can be found here https://www.skcript.com/svr/consensus-hyperledger-fabric/
answered Nov 20 at 4:53
Rangesh
58811024
answered Nov 20 at 4:53
Rangesh
58811024
answered Nov 20 at 4:53
Rangesh
58811024
answered Nov 20 at 4:53
Rangesh
58811024
58811024
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379723%2fhyperledger-fabric-v1-3-consensus%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
for a consensus roadmap also see this, they are implementing raft. jira.hyperledger.org/browse/FAB-6135?jql=labels%20%3D%20raft - "It allows us to have an ordering service without Kafka/ZK depedencies, and It helps with the BFT development as well, since it gives us a chance to hook into Fabric a leader-based consensus protocol and carry those lessons over when writing the BFT plugin."
– Paolo
Nov 21 at 1:45
1
maybe have a look to this one too arxiv.org/pdf/1809.00554.pdf where it starts with "Hyperledger Fabric implements a pluggable consensus on the order of transactions in the..."
– Paolo
Nov 24 at 20:36