Consensus in Hyperledger Fabric

The first role of an ordering node is to package proposed ledger updates. In this example, application A1 sends a transaction T1 endorsed by peers E1 and E2 to the orderer O1. In parallel, Application A2 sends transaction T2 endorsed by peer E1 to the orderer O1. O1 packages transaction T1 from application A1 and transaction T2 from application A2 together with other transactions from other applications in the network into block B2. We can see that in B2, the transaction order is T1,T2,T3,T4,T6,T5 — which may not be the order in which these transactions arrived at the orderer!

--

--

--

Engineer

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

📗PROJECT OVERVIEW — REMNANT LABS👘

Creator’s new interface updated with more functions focusing on users

From The First Industrial Revolution to The NFT

$DUET Vesting Voucher: Staking Reimagined

Cardashift announces the premiere of its Launchpad on Thursday 14th, 2022

AI, Big Data and Blockchain technologies on Healthcare

About Plutos Network

Advisor Spotlight — Chi Tran

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Victor Yeo

Victor Yeo

Engineer

More from Medium

Deploying a smart contract in Blockchain — Ethereum with Remix

Data exchange between organizations in Hyperledger Fabric

Upgradability patterns in Solidity — Part 4

Consortium blockchain solution on Hyperledger Fabric with 3 organizations