automatically when organizations are added or removed from the channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode if you’d like to track different types of assets in their own ‘copy’ of the chaincode. Chaincode packages do not need to be identical across channel members Organizations can extend a chaincode for their with no downtime. The upgrade docs have been significantly expanded and reworked, and now have a standalone home in the documentation: Upgrading to the latest release. Here you’ll find documentation on Upgrading

when organizations are added or removed from the channel. • Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode you’d like to track different types of assets in their own ‘copy’ of the chaincode. • Chaincode packages do not need to be identical across channel members Organizations can extend a chain- code for their with no downtime. The upgrade docs have been significantly expanded and reworked, and now have a standalone home in the documen- tation: Upgrading to the latest release. Here you’ll find documentation on

automatically when organizations are added or removed from the channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode if you’d like to track different types of assets in their own ‘copy’ of the chaincode. Chaincode packages do not need to be identical across channel members Organizations can extend a chaincode for their with no downtime. The upgrade docs have been significantly expanded and reworked, and now have a standalone home in the documentation: Upgrading to the latest release. Here you’ll find documentation on Upgrading

when organizations are added or removed from the channel. • Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode you’d like to track different types of assets in their own ‘copy’ of the chaincode. • Chaincode packages do not need to be identical across channel members Organizations can extend a chain- code for their with no downtime. The upgrade docs have been significantly expanded and reworked, and now have a standalone home in the documen- tation: Upgrading to the latest release. Here you’ll find documentation on

automatically when organizations are added or removed from the channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode if you’d like to track different types of assets in their own ‘copy’ of the chaincode. Chaincode packages do not need to be identical across channel members Organizations can extend a chaincode for their with no downtime. The upgrade docs have been significantly expanded and reworked, and now have a standalone home in the documentation: Upgrading to the latest release. Here you’ll find documentation on Upgrading

9 hyperledger-fabricdocs Documentation, Release master • Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode you’d like to track different types of assets in their own ‘copy’ of the chaincode. • Chaincode packages do not need to be identical across channel members Organizations can extend a chain- code for their with no downtime. The upgrade docs have been significantly expanded and reworked, and now have a standalone home in the documen- tation: Upgrading to the latest release. Here you’ll find documentation on

responses from many applications. It orders each transaction relative to other transactions, and packages batches of transactions into blocks ready for distribution back to all peers connected to the orderer orderer O1. In parallel, Application A2 sends transaction T2 endorsed by E1 to the orderer O1. O1 packages transaction T1 from application A1 and transaction T2 from application A2 together with other transactions packaged in a block – the orderer makes no judgement as to the value of a transaction, it simply packages it. That’s an important behavior of Hyperledger Fabric – all transactions are marshalled into in

automatically when organizations are added or removed from the channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode if you’d like to track different types of assets in their own ‘copy’ of the chaincode. Chaincode packages do not need to be identical across channel members Organizations can extend a chaincode for their with no downtime. The upgrade docs have been significantly expanded and reworked, and now have a standalone home in the documentation: Upgrading to the latest release. Here you’ll find documentation on Upgrading

responses from many applications. It orders each transaction relative to other transactions, and packages batches of transactions into blocks ready for distribution back to all peers connected to the orderer orderer O1. In parallel, Application A2 sends transaction T2 endorsed by E1 to the orderer O1. O1 packages transaction T1 from application A1 and transaction T2 from application A2 together with other transactions packaged in a block – the orderer makes no judgement as to the value of a transaction, it simply packages it. That’s an important behavior of Hyperledger Fabric – all transactions are marshalled into in

automatically when organizations are added or removed from the channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode if you’d like to track different types of assets in their own ‘copy’ of the chaincode. Chaincode packages do not need to be identical across channel members Organizations can extend a chaincode for their with no downtime. The upgrade docs have been significantly expanded and reworked, and now have a standalone home in the documentation: Upgrading to the latest release. Here you’ll find documentation on Upgrading