These are neither design flaws nor vulnerabilities. We have various configuration parameters for private data collection. For example, the following is a configuration of a private data collection. {

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 Regards, Senthil

Have you tried https://github.com/hyperledger/blockchain-explorer? Regards, Senthil

Trevor, ledgerData/chains/chains/{channelName}/ -- keeps the chain of blocks ledgerData/stateLeveldb/ -- keeps the world state (more of a cache to provide faster access to the world state as reading t

Trevor, Wouldn't either of the following work? get into the existing peer container, kill the peer, run the peer node pause, start the peer again. stop the existing peer container, start another conta

Hi, The peer has to be offline before running peer node pause, resume, rollback, and reset commands. Otherwise, we would get the above error. Given that `peer node start` is also part of the node sub-

If couchdb returned an error status code while processing the index, we do log the error but chaincode upgrade would succeed irrespective of that. I would suggest to search for the term index to see w

#couchdb #fabric-chaincode

Do you have the peer logs? Regards, Senthil

#couchdb #fabric-chaincode

the above error seems to match your old definition -- "endorsementPolicy": { "signaturePolicy": "OR('Org1MSP.member'), OR('Org2MSP.member')" } Anyway, I do not have expertise in this. If Yacov looks a

As the memberOnlyWrite is set to false by default (not configured in the collection config as well), all peers are authorized to write if it can satisfy the endorsement policy. Is the endorsement poli

Wouldn't the doc https://hyperledger-fabric.readthedocs.io/en/release-2.0/operations_service.html help? Regards, Senthil

#raft

If you need to expose all features of a database, changes are needed at the database as well as peer code. if you need to plugin a database that is compatible with what currently Fabric offers, then y

Yes, it is not in the roadmap (may change in the future if some drawbacks with go-plugins are addressed by the go team) Yes. Let's say chaincode exposes Put() to update a kv pair. Based on this assump

As discussed/decided in https://jira.hyperledger.org/browse/FAB-8665, pluggable stateDB is not going to be supported anytime soon. If you are okay to fork the Fabric, you can find a high level impleme

A small clarification on this statement. We still validate all reads made by the CouchDB rich query to ensure repeatable read isolation. If any read version is not the same as the committed version ev

As per the documentation, I understood that the support for SQL is very limited in the forked/proprietary oracle's Fabric (I believe it is not open-sourced). In other words, whatever we can do with Co

I will add a few more things on top of what Dave said. Yes, it is dependent on the application requirements. When a chaincode doesn't use rich queries, it archives serializable isolation. When a chain

Hi Santiago, To add further, the channel is always superior in terms of performance. It allows a peer to process blocks in parallel. Difficult to achieve a similar performance using a public or privat

Hi Santiago, I have performed a benchmarking of private data collections. Once I talk with the team, I can share more details. For now, I can say that the performance is low and I have implemented a f

Hi Santiago, What is your requirement? At a high level, it can be differentiated based on privacy, performance, data silos, and development/management complexity. Channels Private Data Collections Pri