- Webinar Recording: https://www.youtube.com/watch?v=elWRmHqRoww
Watch this on-demand webinar to learn how to get a Hyperledger Fabric network up and running with the Hedera Consensus Service. The Hedera team walks through how to create a Hyperledger Fabric network with the IBM Blockchain Platform using HCS for ordering transactions.
Developer resources mentioned in the webinar:
- Official IBM Blockchain Platform tutorial: https://github.com/IBM/Create-BlockchainNetwork-IBPV20
- HCS Hyperledger Fabric plugin repo: https://github.com/hyperledger-labs/pluggable-hcs/blob/master/first-network/README.md
- Hedera Getting Started tutorial: https://docs.hedera.com/guides/tutorials/getting-started-with-the-hedera-consensus-service-fabric-plugin
3. Public vs. Private
Advantage Disadvantage
Private
• Privacy configuration
• Governance
• Centralization
• Scale
• Vendor lock in
Public
• Decentralization • Performance
• Anonymity
• Regulatory concerns
4. The Hedera Consensus Service
Hedera: Providing decentralization of a public network with privacy
and compliance controls of a private network.
5. PRIVACY
FINALITY
TRUST
AVAILABILITY
HEDERA
CONSENSUS
PRIVATE NETWORK PRIVATE NETWORK
CUSTOMIZATION
DATA ENCRYPTION
PERFORMANCE
IDENTITYMANAGEMENT
Encrypted
transaction
Transaction
timestamp
Pluggable Consensus with HCS
Hedera Consensus Service provides auditable
log of transaction for distinct tokens.
Permissioned networks now share a single
consensus engine, enabling:
• Custom data access and encryption
• Custom token definitions
• Verifiable timestamps
• Decentralized, shared service
• Finality of transaction order
• High performance
Hedera supports integrations between the
Hedera Consensus Service, Hyperledger Fabric,
and R3’s Corda
9. Lifecycle of a transaction
1
Transaction proposed to
Fabric peer
2
Client application
broadcast transaction to
orderer
Client
Fabric peer
Fabric orderer
HCS plug-in
Consensus nodes
Mirror nodes
Hedera Hashgraph
10. Lifecycle of a transaction
3
Transaction fragmented
into messages,
associated with topicID
4
Messages submitted to
topic using HCS
Client
Fabric peer
Fabric orderer
HCS plug-in
Hedera Hashgraph
Consensus nodes
Mirror nodes
11. Lifecycle of a transaction
5
Event reaches
consensus,
receiving
consensus
timestamp and
state proof
Client
Fabric peer
Fabric orderer
HCS plug-in
Hedera Hashgraph
Consensus nodes
Mirror nodes
12. Lifecycle of a transaction
6 Notify of message order
Client
Fabric peer
Fabric orderer
HCS plug-in
Consensus nodes
Mirror nodes
Hedera Hashgraph
13. Lifecycle of a transaction
Client
Fabric peer
Fabric orderer
HCS plug-in
Consensus nodes
Mirror nodes
7
Transaction
reassembled,
put in block
8
Ordered
transactions
given to peers
9
Endorsed
responses
collected
Hedera Hashgraph
14. HCS-based Orderer
Orderer
Hedera SDK
Common
HCS Plug-in
Config handling Channel mgmt
Common txn
handling
Block cutter
AtomicBroadcast
Config
handling
Channel
mgmt
Txn handling
Consenter Chain
Broadcast transaction to orderer Deliver ordered blocks
Notify of consensus messages from
mirror node
Submit messages to mainnet
Editor's Notes
Hey good afternoon everybody! I’m excited to talk to you all today about Hedera Hashgraph — we’re an enterprise-grade public network for decentralized applications.
In September of 2019, Hedera launched it global public network – the mainnet. A network that everyone in the world can leverage. A public ledger where the nodes operate at the highest known level of trust - – Asynchronous Byzantine Fault Tolerence – or ABFT for short. Attack resistant and able to come to consensus independently in a matter of seconds. Since the launch of the network - anyone anywhere has been able to create accounts and build decentralized applications.
CLICK
Importantly, unlike other networks, Hedera does not store state. Data does not reside on the network for more than a few minutes. Therefore Hedera - and several third parties – have launched mirror nodes so that transaction history can be managed. While Mirror nodes do not participate in consensus, mirror nodes can provide a public record of transactions and the state. In addition, mirror nodes offer flexibility for the owner to choose what to store and for how long. So the mirror node is a means for storing and retrieving transaction history long after the record has ceased to exist on the Hedera mainnet.
CLICK
And finally we have the concept of an application network – or appnet for short. An appnet is simply software that is executed collectively across Hedera’s global public network. These applications interact in order to achieve a specific common goal or task – settlement between airlines for example, or payments between two organizations or individuals. Importantly, the party’s that interact do not need to trust one another as they inherit the trust from Hedera. Trust in the order of transactions, the time they happen and proof that they occurred.
In September of 2019, Hedera launched it global public network – the mainnet. A network that everyone in the world can leverage. A public ledger where the nodes operate at the highest known level of trust - – Asynchronous Byzantine Fault Tolerence – or ABFT for short. Attack resistant and able to come to consensus independently in a matter of seconds. Since the launch of the network - anyone anywhere has been able to create accounts and build decentralized applications.
CLICK
Importantly, unlike other networks, Hedera does not store state. Data does not reside on the network for more than a few minutes. Therefore Hedera - and several third parties – have launched mirror nodes so that transaction history can be managed. While Mirror nodes do not participate in consensus, mirror nodes can provide a public record of transactions and the state. In addition, mirror nodes offer flexibility for the owner to choose what to store and for how long. So the mirror node is a means for storing and retrieving transaction history long after the record has ceased to exist on the Hedera mainnet.
CLICK
And finally we have the concept of an application network – or appnet for short. An appnet is simply software that is executed collectively across Hedera’s global public network. These applications interact in order to achieve a specific common goal or task – settlement between airlines for example, or payments between two organizations or individuals. Importantly, the party’s that interact do not need to trust one another as they inherit the trust from Hedera. Trust in the order of transactions, the time they happen and proof that they occurred.