Chaincode Deployment

The Hyperledger Fabric chaincode lifecycle is a sequence of actions performed by organizations to agree on the parameters that define a chaincode (such as name, version, endorsement policy, etc.) and deploy the chaincode to a channel for collaborative use. Channel members come to an agreement via the steps below.

Chaincode Deployment Steps

Package a chaincode

Every organization that wants to call chaincode functions obtains the source code of a chaincode and packages it in an appropriate format.

Install the chaincode package

The chaincode should be installed on every organization’s peer that is supposed to execute or endorse chaincode transactions.

Approve a chaincode definition

Every organization that is going to use the chaincode composes and submits a chaincode definition―a set of configuration parameters considered to be acceptable by an organization.

Commit the chaincode definition to a channel

Once a required number of channel participants have approved the same chaincode definition, the definition can be committed to a channel. The commit transaction is performed once and can be triggered by any organization.

Last updated

Was this helpful?