diff --git a/Contents/blockchain/Hyperledger/assets/ecosystem.png b/Contents/blockchain/Hyperledger/assets/ecosystem.png new file mode 100644 index 000000000..9967375ef Binary files /dev/null and b/Contents/blockchain/Hyperledger/assets/ecosystem.png differ diff --git a/Contents/blockchain/Hyperledger/readme.md b/Contents/blockchain/Hyperledger/readme.md index 6d3c1e7eb..09737af60 100644 --- a/Contents/blockchain/Hyperledger/readme.md +++ b/Contents/blockchain/Hyperledger/readme.md @@ -61,13 +61,14 @@ In `Fabric`, an application-specific endorsement policy specifies which peer nod Hyperledger Fabric, enables confidentiality through its `channel` architecture and private data feature. In channels, participants on a Fabric network establish a `sub-network` where every member has visibility to a `particular set` of transactions. Thus, only those nodes that participate in a channel have access to the chaincode and data transacted, preserving the privacy and confidentiality of both. Private data allows collections between members on a channel, allowing much of the same protection as channels without the maintenance overhead of creating and maintaining a separate channel. -## Technology +## Ecosystem -Hyperledger Fabric is written in `Go`. It uses `CouchDB` as its state database. and `etcd` as its key-value store. +![Docker-based deployment environments](./assets/ecosystem.png) ## Reference * * +* * *