Hi Qing, There was a bug in the cache management logic. It got fixed in v2.2 (what version are you using?) You can find more details on https://github.com/hyperledger/fabric/pull/1909

Hi, Thank you for reading this mail! We are using hyperledger fabric 2.2 on CentOS 8.2. Follow the steps below, we got json2. ------ 1. Invoke the chaincode just PutState json1. The parameters of

Hi all, Could I please ask you guys for help? When starting the orderer I'm getting the following error: 2021-01-20 22:57:02.487 UTC [orderer.common.server] Main -> PANI 113 Failed validating

Fabric Contributor Meeting When: Wednesday, 20 January 2021 9:00am to 10:00am (GMT-05:00) America/New

Hyperledger Fabric Contributor Meeting When: Every other Wednesday 9am US Eastern, 14:00 UTC Where: https
://zoom.us/j/51849
47650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Agendas and Recordings:

Private Chaincode Lab When: Tuesday, 19 January 2021 8:00am to 9:00am (GMT-08:00) America/Los

Very helpful, thanks Sincerely yours, Samyak Jain

No. If you are referring to the members of the system channel as the "consortium", being removed from the system channel does not remove you from channels that a peer or ordering organization has

This tutorial also discusses channel policies: Channel policies — hyperledger-fabricdocs master documentation (hyperledger-fabric.readthedocs.io)

To answer your question specifically, the /Channel/Application/Admins policy determines who must sign to add or remove an application organization on a channel. More generally you may find

Correct! With HLF v2.x external builders and chaincode as an external service, we can easily migrate to remove the dependency on usage of docker socket. That is definitely one of the ways! Apart from

Chintan, HLF 2.x introduced external chaincode builders and chaincode as an external service. With minimal changes to your chaincode package, you can deploy your chaincode as a separate pod within a

Hi Team, With us marching slowly towards end-of-life for Docker as a runtime environment in Kubernetes, and containerd turning out to be default for latest Kubernetes version on most cloud providers,

That's right, implicit collections always use blockToLive=0, the private data is never purged. You would need to create an explicit collection per org if you'd like to set the property values such as

That's right. But you don't have to use the provided implementation, you can simply use it as an example for how to set policies in your own implementation. Look at the provided policyFromMSPIDs() and

As of v2 of Fabric, the packages we expect applications and chaincode to build and link against have been extracted to `hyperledger/fabric-chaincode-go` and `hyperledger/fabric-protos-go`. Fabric is

So are you simply saying that let's say if I use state-based endorsement policy which only requires the creator of the transaction and one governing member in the consortium to validate a transaction,

On Mon, Jan 18, 2021 at 05:48 AM, Yacov wrote: Brett Logan I would then like to ask that what is the recommended way of setting up a common channel to share data between N organizations? Or do we

What is blockToLive fori implicit private data collection? Looking at the code, it appears to be 0, i.e. never purged. Can someone please confirm?

Just because Fabric does exhaustive search,doesn't mean the problem is really NP hard. If you have an endorsement policy thatis satisfied by any k organizations out of n organizations,then