search

hyperledger / fabric

Hyperledger Fabric is an enterprise-grade permissioned distributed ledger framework for developing solutions and applications. Its modular and versatile design satisfies a broad range of industry use cases. It offers a unique approach to consensus that enables performance at scale while preserving privacy.
https://wiki.hyperledger.org/display/fabric
Apache License 2.0
15.79k stars 8.86k forks source link

Multi organization and multi-channel contract version conflicts bug #4252

Open yaofeiliang opened 1 year ago

yaofeiliang commented 1 year ago

Description

Two organizations A、B are deployed on channel 1 and org B is deployed on channel 2 separately. Both channels have the same contract (and the contract name is also the same). When the version of channel 2 contract is upgraded, the contract with the same name in channel 1 cannot be used properly and endorsement errors will occur (in this case, only channel 1 contract can be upgraded to the same version)

Two organizations, A、B, are both in channel 1 and org A、org B are also in channel 2. Both channels deploy the same contract (and the contract name is the same). After the version upgrade of channel 2 contract, the contract with the same name in channel 1 can be used normally.

Steps to reproduce

No response

denyeart commented 1 year ago

Please provide exact reproduction steps. e.g. are you using v2.x chaincode lifecycle? What are the series of lifecycle calls made? What client is invoking? What invoke calls are made?