Note: about Fabric V2

Background

When upgrading to Fabric V2, there are a number of un-certain network behaviour. Below documents the adopted approaches and configurations related.

Eventstore

• the "eventstore" chaincode is given "AND" signature policy
• Originally, the collection profile can be single org, or multiple org. However, private data's collection profile requires single org; here adopt single org collection profile. In order to obtain sufficient endorsement, we set "discovery" to true, to be implemented by fabric-cqrs library.

Discovery

• see tutorial about discovery
• in local Mac development, asLocalhost must be true.
• in Github Action's create release workflow, asLocalhost must be false.
• the asLocalhost is set true, based on NODE_ENV=production

Private Data

• use implicit collection
• the "eventstore" chaincode is given "AND" signature policy
• the connection profile is single org/single peer. If changed to 2-org in connection profile, the SDK will attempt to endorse from them; and fail. Beside, be noted that "discovery" set false, to be implemented by fabric-cqrs library.

fabric-ca

• (April 3) the fabric-ca-client does not seems to fully compatible with Fabric V2
• in "operator" package, we keep using "[email protected]" library in order to parse connection profile correctly; and hence getCertificateAuthority