Hi Fabric experts, I am attempting to develop a methodology to retrieve logs from the chaincode, in order to visualize in Kibana through ELK infrastructure. At the moment, I am retrieving chaincode

I was reading about similar issues in fabric version 1.4.2 (the images I'm using on my containers are 1.4.1, so I'm not sure if it is related at all or not), and how it was related to a certain

When you submit a transaction to ordering, it is not guaranteed to get ordered into a block. If an orderer encounters an issue (as it looks like yours has due to stress), the transaction may not get

You would need to provide the full stack trace from the panic message in order to troubleshoot. Dave Enyeart "Tomás Peixinho" ---02/10/2021 01:34:13 PM---Good afternoon fellow colleagues, I'm

Good afternoon fellow colleagues, I'm developing an application using Hyperledger Fabric and I've found a weird error that I'm not sure how to fix. I'm running everything on just one machine, with two

You should not upgrade a 2nd or 3rd time. Again - 'Upgrade' is a transaction on the channel, therefore you only need to do it once for the whole channel, not per peer or per organization. The

Hi David, Thank you for your response. If you see below log, I first install on 4 peers. And then upgrade two peers with success. And third one is failed. Actually, my problem is I have only two

Actually, taking a quick look at the ECDSA CryptoSuite implementation in the Node SDK, it seems to allow 384 to be specified as a key size (which maps to the P-384 curve). So rather than implementing

Hi Alejo, I am really glad that you pinned down the problem. I think the reason is that the CLI (written on Go) is using the Go crypto support which allows it to generate a signature from a hash

Hi. My team is running a couple of stress tests over HLF 2.3.0 in a network with 3 orderers and 2 peers (each peer is of different org), sending an array of JSON data through an API developed with

Hi Fabric Community, the FPC Team is happy to announce a new release of Fabric Private Chaincode -- a framework built on (unmodified) Hyperledger Fabric to enhance data confidentiality for

It looks like you are using legacy chaincode. 'Upgrade' is a transaction on the channel, therefore you only need to do it once for the whole channel, not per peer or per organization. Dave

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

Hi Team, I have two organizations and two peers each. For some reason, we just upgraded only one peer in each organization (but installed chaincode all peers). Now I need to run all 4 peers but I have

If you update the corresponding 'parent' prefix for every transaction, you could just write it every time instead of read/write. You only receive conflicts when you read/write. e.g. write four records

Yes, that's right. Note that you can update N key/values in the 2nd transaction, if you have such a need. You don't have to update them one at a time. Dave Enyeart "Tomás Peixinho" ---02/08/2021

This could be solved by the following approach: https://www.github.com/hyperledger/fabric-samples/tree/master/high-throughput Basically, you could store all the request as it is, in its own key. Then

Thank you for your feedback, Dave! I see the value of the ranged queries now, that actually makes sense, I hadn't thought about it. It just doesn't serve me very well. However, your idea to separate

Dear Tomás, Have you seen this? Please review the following - perhaps you need to craft the solution to the problem slightly differently and side step the implementation

I don't think it's possible in my project (this is my master's thesis, the idea was defined like this by my thesis advisors, who don't know much about blockchain technology). But I can be more