Scribd
Upload
2 views

Hyperledger_Presentation

Hyperledger is an open-source collaborative project aimed at advancing enterprise-grade permissioned blockchain solutions, distinct from public blockchains like Bitcoin and Ethereum. Key components include Hyperledger Fabric, Sawtooth, and Indy, which offer modular architectures for various use cases such as supply chain, healthcare, and finance. The framework emphasizes security, scalability, and customization, supported by a strong community and tools for performance benchmarking and deployment.

Uploaded by

2229016
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

Hyperledger_Presentation

Hyperledger is an open-source collaborative project aimed at advancing enterprise-grade permissioned blockchain solutions, distinct from public blockchains like Bitcoin and Ethereum. Key components include Hyperledger Fabric, Sawtooth, and Indy, which offer modular architectures for various use cases such as supply chain, healthcare, and finance. The framework emphasizes security, scalability, and customization, supported by a strong community and tools for performance benchmarking and deployment.

Uploaded by

2229016
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 23

Hyperledger – An Open-Source

Blockchain Ecosystem
Agenda
• Introduction to Hyperledger
• Hyperledger vs. Public Blockchains
• Key Hyperledger Projects (Fabric, Sawtooth, Indy, etc.)
• Hyperledger Fabric Architecture
• Use Cases of Hyperledger
• Benefits & Challenges
• Future of Hyperledger
• Conclusion
Introduction to Hyperledger
• Definition: Hyperledger is an open-source
collaborative effort hosted by the Linux Foundation
to advance cross-industry blockchain technologies.
• Goal: Enable enterprise-grade permissioned
blockchain solutions.
• Not a cryptocurrency, unlike Bitcoin or Ethereum.
• Modular & Scalable framework for businesses.
• Fabric , Sawtooth, Indy, Besu, Iroha
Hyperledger vs. Public Blockchains
Hyperledger Public Blockchains
Feature
(Permissioned) (Bitcoin/Ethereum)

Private, known
Access
Feature Hyperledger (Permissioned) Public, anonymous
Public Blockchains

Access
participants
Private, known participants
(Bitcoin/Ethereum)
Public, anonymous
Consensus Flexible (PBFT, Raft, etc.) PoW, PoS
Speed High throughput Slower due to decentralization
Use Case Flexible (PBFT, Raft,
Enterprise solutions Cryptocurrencies, DeFi
Consensus PoW, PoS
etc.)

Slower due to
Speed High throughput
decentralization

Use Case Enterprise solutions Cryptocurrencies, DeFi


Hyperledger Fabric Architecture
Components:
• Peers:
– Endorsing peer: Validate the transaction
– Committing Peer: Update the ledger
• Ordering Service:The mechanism by which applications and peers interact
with each other to keep the ledger updated and consistent across a channel.
This is done by special nodes called orderers.
• Membership Service Provider (MSP): Each participant has a unique digital
identity that is verified by the MSP. Also the degree of authorisation.
• Channels: Channels are a way to create private sub-networks within the
Hyperledger Fabric network.
• Chaincode: Chaincode is a smart contract that runs on the Hyperledger Fabric
network. It is written in a programming language such as Go, Node.js or Java
and is responsible for implementing the business logic of the application.
Chaincode is deployed on the network and can be invoked by authorized
parties to update the ledger.
Hyperledger Fabric Architecture
Hyperledger Fabric Architecture
Hyperledger Fabric Architecture
Hyperledger Fabric Architecture
Hyperledger Fabric Architecture
How it works?
Phase 1

Transaction Transaction Transaction


proposal execution endorsement

Phase 2

Transaction Transaction
submission ordering

Phase 3
Transaction Transaction Commit event
validation commitment
How it works?
• Phase 1 - Transaction Proposal and Endorsement:

• a) Transaction proposal — The client application(A) submits a signed


transaction proposal by connecting to the gateway service of a
peer(P1).
• b) Transaction execution — The selected peer executes the chaincode
(S1) specified in the proposal and generates a proposal response. The
selected peer signs the proposal response and returns it to the
gateway.
• c) Transaction endorsement — The gateway repeats transaction
execution (step-b) for each organization required by the chaincode
(smart contract) endorsement policies. The gateway service collects
the signed proposal responses and creates a transaction envelope —
which it returns to the client for signing.
How it works?
• Phase 2 - Transaction Submission and Ordering:

• a) Transaction submission — The client sends the signed


transaction envelope to the gateway service. The gateway
forwards the envelope to an ordering node and returns a
success message to the client.

• b) Transaction ordering — The ordering node (O1) verifies


the signature. The ordering service orders the transaction
and packages it with other ordered transactions into blocks.
The ordering service then distributes the block to all peers
in the channel for validation and commitment to the ledger.
How it works?
• Phase 3 - Transaction Validation and Commitment:

• a) Transaction validation — Each peer checks that the client signature


on the transaction envelope matches the signature on the original
transaction proposal. Each peer also checks the endorsements from
all peers match and that the endorsements satisfy the endorsement
policies. Each peer then marks each transaction as valid or invalid for
commitment to the ledger.
• b) Transaction commitment — Each peer commits the ordered block
of transactions to the channel ledger (L1). The commit is an
immutable ledger update (write) to the channel ledger. The world
state (essentially, the sum of all valid transactions) of the channel is
updated with results of valid transactions only.
• c) Commit event — Each peer that commits to the ledger sends the
client a commit status event with proof of the ledger update.
Use Cases of Hyperledger
• Supply Chain: Walmart’s food traceability.
• Healthcare: Secure patient records.
• Finance: Cross-border payments (e.g.,
we.trade).
• Government: Digital identity (e.g., Sovrin).
• IoT: Device authentication.
Why Hyperledger?
• • Permissioned Networks: Controlled
participation.
• • Scalability: High transaction throughput.
• • Modular Design: Customizable components.
• • Enterprise-Focused: Designed for business
use cases.
Hyperledger Tools
• • Hyperledger Caliper: Performance
benchmarking tool.
• • Hyperledger Cello: Simplifies blockchain
deployment as a service.
• • Hyperledger Explorer: Web application for
viewing blockchain data.
• • Hyperledger Aries: Toolset for building
interoperable identity solutions.
Hyperledger Libraries
• • Hyperledger Ursa: Shared cryptographic
library.
• • Hyperledger Quilt: Enables cross-chain
transactions with Interledger Protocol.
Hyperledger Fabric Architecture
• • Peer Nodes: Maintain the ledger and
execute smart contracts.
• • Orderer Nodes: Ensure transaction
consistency.
• • Channels: Private communication paths.
• • Chaincode: Smart contracts written in Go,
Node.js, or Java.
Use Cases of Hyperledger
• • Supply Chain: Enhances transparency and
traceability.
• • Finance: Streamlines cross-border payments
and trade finance.
• • Healthcare: Securely manages patient
records.
• • Digital Identity: Decentralized identity
verification.
Benefits of Hyperledger
• • Security & Privacy: Granular access control.
• • Efficient Consensus: Supports pluggable
mechanisms.
• • Strong Community Support: Backed by
industry leaders.
• • Interoperability: Allows integration with
enterprise systems.
Conclusion
• • Enterprise Adoption: Provides scalable and
secure blockchain solutions.
• • Future Growth: Continuous development for
broader industry adoption.
• • Getting Started: Explore projects and
contribute at hyperledger.org.
Q&A
• • Any Questions?
• • Contact: [Your Email/Website]

You might also like