...
Chaincode Management Page
Workflow
upload chaincode→install chaincode→ approve→ commit
1. Upload chaincode: Each organizational user uploads the packaged chaincode compressed package to their respective cello;
2. Install chaincode: Each organizational user installs the chain code on their respective nodes;
3. Approve: Each organization performs licensing operations on the chain code separately;
4. Commit: When the number of licensed organizations meets the policy, one of the organizations performs the submission operation.
APIs
- Get chaincode information list
- Submit chaincode
...
| Name | Label | Version | PackageId | Operation |
|---|---|---|---|---|
| Cc1 | V1 | sha2sum | Install | Approve | Commit | Delete (if chaincode not used yet) | |
| Cc2 | V1 | sha2sum | Install | Approve | Commit | Delete (if chaincode not used yet) | |
Upload Chaincode UI
| Chaincode Name: | |
| Description: | |
Version: | |
| Choose File: | |
| Chaincode language: | |
Chaincode hash: (maybe calculated by backend depending on performance) |
Chaincode Installation Page
...
| Choose the node to install chaincode (current org) |
|---|
Approvement Page
APIs
- Get all orgs' approvement status
- Approve current org's chaincode
...
The backend checks if approvement is successful or not and returns the result to frontend (it's better to include failure info). Frontend then prompts the response.
