Documente Academic
Documente Profesional
Documente Cultură
for Business
Enterprise adoption patterns
Use case examples from practice
Hyperledger Meetup
Frankfurt, 11. Mai 2017
Page 4
www.hyperledger.org
© 2017 IBM Corporation
Strategic Client Blockchain Adoption Journey
A multi-stage approach, delivering incremental and new business value at each milestone
Transformational Innovation
New Business Models
New/Adjacent SCM Partners
New Revenue Streams
Deploy
Deploy Shadow
Shadow Blockchain
Blockchain
Deploy Deploy
Production Production
Blockchain Blockchain
Trade Execution
and Confirmation
Example: A Bank B Bank
Importers and
Banks Carriers Forwarders Ports Authorities
Exporters
Manual, paper- Excess No single Manual Data Collection and False Positives
based Inventory version of ”the Collection Delivery Black
Lack of visibility
processes Manual, paper- Truth” Holes
Manual, pre-manifest
based Sub-optimal
Lack of Real- Manual, paper- Lack of visibility
processes paper-based stack
Time based into land move-
information Duplication of processes processes placement
Administrative ment before /
Process Manual Data after ocean
Collection transport
Root Causes:
Multiple data formats Point-to-point interactions Absence of messaging standards
© 2017 IBM Corporation
Embedded video: MAERSK Blockchain can be found at
https://www.youtube.com/watch?v=tdhpYQCWnCw
Into v1
©©2017
2017IBM
IBMCorporation
Corporation
Embedded Video Hyperledger v0.6 Lessons
Learned Video can be found at
https://www.youtube.com/watch?v=EKa5Gh9whgU
membership
ECA, TCA, TLS-CA
peer
SDK
Consensus
keys Ledger
Events
Chaincode
state
membership
No SPoF
No SPoT
peer
Source : https://jira.hyperledger.org/browse/FAB-37
Event
© 2017 IBM Corporation 16
Ledger representation
Replaceable
Transaction Log
State Database
tx array
Latest written key/values for
CouchDB (external option)
TX
use in transaction simulation supports keyed queries,
block
E0 P3 P4 Endorsement policy:
A A • “E0, E1 and E2 must sign”
B D
• (P3, P4 are not part of the policy)
S
Client application submits a transaction
Client
Application D E1 proposal for chaincode A. It must target
K
A
B
O O the required peers {E0, E1, E2}
Key:
Ap
E2 O O Endorser Ledger
A
B
Ordering-Service Committer Application
Orderier
S
Each execution will capture the set of
Client
Application D E1 Read and Written data, called RW sets,
K
A
B
O O which will now flow in the fabric.
Key:
Ap
E2 O O Endorser Ledger
A
B
Ordering-Service Committer Application
Orderier
S
Client
Application
D
K
E1
A
B
O O
Key:
Ap
E2 O O Endorser Ledger
A
B
Ordering-Service Committer Application
Orderier
S
Ordering happens across the fabric in
Client
Application
D
K
E1 parallel with transactions submitted by
A
B
O O other applications
Key:
Ap
E2 O O Endorser Ledger
A
B
Ordering-Service Committer Application
Orderier
Orderier
S
Transactions are written to the ledger
Client
Application
D
K
E1 and update caching DBs with validated
A
B
O O transactions
Key:
Ap
E2 O O Endorser Ledger
A
B
Ordering-Service Committer Application
Orderier
!
E0 ! P3 ! P4 Applications can register to be notified
A A when transactions succeed or fail, and
B D
when blocks are added to the ledger
S
Applications will be notified by each peer
Client
Application
D
K
! ! E1 to which they are connected
A
B
O O
Key:
Ap
! E2 O O Endorser Ledger
A
B
Ordering-Service Committer Application
Orderier
Client
App
SDK E0 E2
Z A
• Peers E0 and E3 connect to the red
Y
O O B
Orderer
Chaincode
• Support for Docker images for easy deployment for Hyperledger-fabric 1.0.
Docker images will be available for all major components to run a network (peers, solo
orderer, CLI, CA, Kafka, CouchDB). A “Getting started” section will be available in the
Hyperledger-fabric publications. Getting started will help a developer or user to start
the network, run a simple application , and learn the basics of running v1. See:
http://hyperledger-fabric.readthedocs.io/en/latest/
• Support for a tool that helps bootstrap a network. The bootstrap network tool is
available and called the Configuration Transaction Generator (configtxgen). The tool is
designed to configure the network with organizations included in the ordering service
genesis block and generates the configuration transaction artifacts used for channel
creation.
© 2017 IBM Corporation 29
Thank You! Thomas Hartmann
Expert Consultant
© 2017
© 2017 IBM Corporation
IBM Corporation Page 30