writing a key to that collection), the receiving parties can utilize the GetPrivateDataHash() chaincode API to verify that the private data matches the on-chain hashes that were created from private data in the default behavior builds and runs chaincode in the same manner as prior releases using the Docker API. Eliminate Docker daemon dependency Prior releases of Fabric required peers to have access to a Docker immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections

writing a key to that collection), the receiving parties can utilize the GetPrivateDataHash() chaincode API to verify that the private data matches the on-chain hashes that were created from private data in the default behavior builds and runs chaincode in the same manner as prior releases using the Docker API. Eliminate Docker daemon dependency Prior releases of Fabric required peers to have access to a Docker immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections

writing a key to that collection), the receiving parties can utilize the GetPrivateDataHash() chaincode API to verify that the private data matches the on-chain hashes that were created from private data in the default behavior builds and runs chaincode in the same manner as prior releases using the Docker API. Eliminate Docker daemon dependency Prior releases of Fabric required peers to have access to a Docker immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections

writing a key to that collection), the receiving parties can utilize the GetPrivateDataHash() chaincode API to verify that the private data matches the on-chain hashes that were created from private data in the default behavior builds and runs chaincode in the same manner as prior releases using the Docker API. Eliminate Docker daemon dependency Prior releases of Fabric required peers to have access to a Docker immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections

writing a key to that collection), the receiving parties can utilize the GetPrivateDataHash() chaincode API to verify that the private data matches the on-chain hashes that were created from private data in the default behavior builds and runs chaincode in the same manner as prior releases using the Docker API. Eliminate Docker daemon dependency Prior releases of Fabric required peers to have access to a Docker immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections

writing a key to that collection), the receiving parties can utilize the GetPrivateDataHash() chaincode API to verify that the private data matches the on-chain hashes that were created from private data in the default behavior builds and runs chaincode in the same manner as prior releases using the Docker API. Eliminate Docker daemon dependency Prior releases of Fabric required peers to have access to a Docker immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections

nodes. Metrics can also be pushed to StatsD. As of v1.4.4, the /version endpoint allows operators to query the release version of the peer and orderer and the commit SHA from which the release was cut. Improved immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections Some features of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database)

nodes. Metrics can also be pushed to StatsD. As of v1.4.4, the /version endpoint allows operators to query the release version of the peer and orderer and the commit SHA from which the release was cut. Improved immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections Some features of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database)

nodes. Metrics can also be pushed to StatsD. As of v1.4.4, the /version endpoint allows operators to query the release version of the peer and orderer and the commit SHA from which the release was cut. Improved immutable, shared ledger encodes the entire transaction history for each channel, and includes SQL-like query capability for efficient auditing and dispute resolution. Privacy — Channels and private data collections Some features of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database)

ing a key to that collection), the receiving parties can utilize the GetPrivateDataHash() chaincode API to verify that the private data matches the on-chain hashes that were created from private data in the default behavior builds and runs chaincode in the same manner as prior releases using the Docker API. • Eliminate Docker daemon dependency Prior releases of Fabric required peers to have access to a the consistent update of information — and to enable a whole host of ledger functions (transacting, query- ing, etc) — a blockchain network uses smart contracts to provide controlled access to the ledger