Hi Manu, Looks like I overlooked this in the documentation here. By organizations' peers I thought it is specific peers that can be fine grained. Apologies for the confusion. policy: The private data

Refer to Chaincode namespace — hyperledger-fabricdocs main documentation for cross chaincode access Regards, Satheesh

#fabric-chaincode

Hello Manu, Yes, using policy attribute in collection json, peers that are participating in the private data collection can be specified. Regards, Satheesh

Hello Nitish, I don't think fabric has this capability out of box. You can write your own service say for e.g., Node.js rest service to invoke chaincode and use that for integration with UI. Regards,

Hello Eshaan, From my limited knowledge, Have you considered creating Organizational unit within organization. I believe attribute based access control is possible based on your usecase. Membership Se

Dear Harsha, I assume "id" would be different for a new project, right ? If not, you include projname as well to check if Asset exists. Regards, Satheesh

From what I understand, only "query" (read only) transactions work cross-invoking in different channels. If state is modified by chaincode, then channel has to be same as callers chaincode. In the exa

#fabric-chaincode

Any clue in bootstrap/build logs ? -Satheesh

Errors seen when setting logspout with fabric 2.2 Any pointers is appreciated. Following steps described here to setup logspout: https://hyperledger-fabric.readthedocs.io/en/release-2.2/deploy_chainco