1. Upload
POST api/v1/chaincodeschaincodeRepo
The front end will allow uploading a chaincode package, which is a .tar.gz format file.Install a chaincode: peer lifecycle install
Body Parameters | Type | Note | name | string | the name of chaincode
|---|---|---|---|
| chaincode_package | string | The base64-encoded contexts of the chaincode package | |
| chaincode_label | string | The label that will be used to identify the installed chaincode package | |
| version | string | The version of the uploaded chaincode | |
, including the json metadata file: { | language | string | The programming language |
| description | string (optional) | version | string
2. Perform chaincode operations → Install
2. Perform chaincode operations →
...
Approve (may by several orgs), Commit
POST api/v1/chaincodes/<chaincode_name>chaincodeDefinitions/?operaionsoperations=<install/approve<approve/commit>
Query Parameters | Type | Note |
|---|---|---|
| operations | string | HLF lifecycle command that deploys, approves, and commits a chaincode with several organizations |
Body Parameters | Type | Note |
|---|---|---|
| name | ||
| chaincode_label | string(optional) | The label that will be used to identify the installed chaincode package |
| package_id | string(optional) | The package id of the chaincode package that will be installed. |
| channel_id | string(optional) | The channel on which this command should be executed. |
| version | string (optional) | the version of the chaincode definition to be approved |
| signature_policy | string (optional) | Use a policy inside the channel configuration as the chaincode endorsement policy. |
| peers | string array (optional) | The array of the id of the peer nodes. For commit only |
| init-required | bool flag |
3. List chaincodes
Get api/v1/chaincodes
...