HI Team, We are using HLF 1.4.2 , and getting below error on our couchDB. Please suggest any solution to mitigate this issue. [error] 2021-06-27T10:51:21.242416Z nonode@nohost emulator -------- Too

Sure.... https://docs.google.com/document/d/1O5UCzf8H_kN4iqMgHm8haDhqacsCBEWNY-dhDG7qgYc/edit# Regards, Matthew. Matthew B White IBM Blockchain Solutions Architect Email me at

Hi Matt, Can you please share the design doc you have found? Best, Artem Barger

Hello; Just an FYI note to the community that I'm starting to actively look at https://jira.hyperledger.org/browse/FAB-5097 On-demand removal of private data to support making a solution using

Hi, Thank you very much for your response. ChaincodeA only makes use of GetState calls, so I'm not modified the ledger. I can't install chaincodeA in channel-2, I need to keep it isolated in another

I'm trying to invoke a chaincode function that sets details about a crop. This function doesn't use date/time, and is logically deterministic. I've checked that the chaincode is successfully installed

Hi David, Thanks so much for your quick turnaround. Apologies I couldn't respond sooner. The solution that you've suggested is what we have implemented now and seems to be working so far as there are

1. I think that NFT is future work. Thetoken SDK is an active project and it is extended on a daily basis. 2. It is up to the system configurationto decide. When you select the "dlog" driver in

Thank you very much for your inputs!

Hi , Had a few questions about fabric token sdk. 1. Can you create non fungible token in fabric token sdk if yes how? And can you extend the tokens to include other characteristics? 2. Fabric token

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

LMDWG to BCC Hi, Amitansu Patnaik. Have you tried with minifabric? My guess is that the docker images for Fabric on M1 have not been pushed. This is what I see: Ry -- Ry Jones Community Architect,

You were the one asking for alternatives to the submitTransaction() approach! In a nutshell, if you don't know or don't care who the endorsers are, use submitTransaction(). If you know the endorsing

So why is useful no to use service discovery for automatic selection of endorsers? I mean why not to use this type of code

Good explanation Mark. In terms of a code sample, here is a sample of a Node SDK gateway application that doesn't use service discovery for automatic selection of

The transaction endorsement and submit process is the same whether you are using a client application that deals with protobuf / gRPC messages directly, the old low-level SDK, the current Gateway SDK,

Hmm, I am a bit confused. As I see here https://github.com/hyperledger/fabric-samples/blob/main/asset-transfer-basic/application-java/src/main/java/application/java/App.java using the gateway

Currently the client application must gather the endorsements from the required number of peers. The 'gateway' functionality within the client SDK can manage this for you. There is work ongoing to

Hey guys, as I understand, the client application proposes transactions to the peers. Is the client application sending it to only one peer or all the peers (as defined in endorsement policy)? Or is

The sample demonstrates how to track block event progress so that your processing logic can resume where it left off if it is interrupted. Also the block events are replayable so you can re-process