Details
-
Bug
-
Status: Complete
-
Medium
-
Resolution: Done
-
None
-
None
-
None
Description
With reference to below Jira we can see the implementation approach taken for this method
https://jira.hyperledger.org/browse/BE-750
From Fabric end we have two different system chaincodes to handle the 1.x(install-instantiate model) and 2.x(lifecycle)model
lscc: manages the chaincode lifecycle for the 1.x releases of Fabric.
_lifecycle: implements the Fabric chaincode lifecycle process
For Explorer connected to Fabric with 1.x channel application capability "lscc" chaincode is contacted and "GetChaincodes" inside it retrieves all the instantiated chaincodes
whereas
For Explorer connected to Fabric with 2.x channel application capability "_lifecycle" chaincode is contacted and "QueryInstalledChaincodes" inside fails from fabric end itself to fetch the list of installed chaincodes
Can we update this method to display list of committed chaincodes on the network, instead of fetching installed chaincodes