you need to pass orderer details as well: for e.g., -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

orderer host need to be fully qualified with domain name. And if orderer is running on a different host, you need to provide that instead of locallhost along with port number where orderer is listenin

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

As a application owner and contract developer, you have the flexibility to define the structure of ledger data. You can handle it based on application needs in the contract/chaincode method which is m

#database

Yes, docker directory is present inside compose directory. You can check if specifying path as compose/docker/docker-compose-org3.yaml works. -Satheesh

You might want to check if Fabric CA server is up and listening on port 7054

One option is to have these functions as separate chaincode with respective endorsement policy. Regards, Satheesh On Saturday, February 18, 2023 at 12:11:57 PM GMT+5:30, Mayank Agrawal <agrawalmayank0

For permission control at user level, attribute based access control can be used. https://github.com/hyperledger/fabric-samples/tree/main/asset-transfer-abac -Satheesh On Monday, February 20, 2023 at

#hyperledger-fabric #fabric

If u1 and u2 are part of organizations in both channels c1 and c2, then org level policies can be defined in channel configuration. But if you are looking for user level policy, I doubt if that is pos

#hyperledger-fabric #fabric