Hi Nikhil, In response to your following comment, I re-ran the commit readiness command with those options but still get the same result: Command: peer lifecycle chaincode checkcommitreadiness -o

Hi, I have a network of 2 orgs - Org1 and Org2. I am getting the same error when checking commit readiness using following even though I ran approveformyorg on both Orgs: Executed the approveformyorg

Hi All, Is there any swagger documentation or any pointers to access the REST API exposed by each ordering node? This is referenced

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

I compose the system with the following structure. Mobile App <-> Api Server <-> Fabric Network(Peer, Orderer) I want to manage the user's key and certificate in the mobile app. In this case, what

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 25 December 2020 6:00am to 7:00am (GMT+00:00)

Hi I have been trying to get Hyperledger Fabric (v2.0.1) to connect to SoftHSM2 (v2.5.0), but haven't been successful at that. The main purpose is to create a secret key for symmetric

Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 25 December 2020, 6:00am to 7:00am, (GMT+00:00)

Fabric Contributor Meeting When: Wednesday, 23 December 2020 9:00am to 10:00am (GMT-05:00) America/New

It looks like a compound word of c, auth and dsl i guess but don't know what does c stand for

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

Block data can be retrieved invoking the QSCC using its, e.g. GetBlockByNumber(), functions. However, qscc cannot be invoked from other chaincodes (line 96 of

I see that fabric-chaincode-go implementation limits GetStateByRange to only simple keys. However, it would be nice if I can get a set of composite keys by range and then fetch corresponding state

Hello again, We released a new version of the Hyperledger Fabric Operator which includes: New Kubectl plugin to create a network with a few commands Parametrization for the peer and ordering

I am trying to deploy a three-orderer two-peer network in Docker swarm, but somehow I keep seeing TLS handshake errors logged in only the first peer. I'm working with Fabric 1.4.9, and these are the

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 18 December 2020 6:00am to 7:00am (GMT+00:00)

Hello there, I wanted to know if there is a document somewhere about the question of hardware requirements for a network, for example RAM, type of disk, bandwidth for one peer, for one orderer etc

Hello, thank you for your answer, here is an example of the logs inside the docker container : 2020-11-13 23:13:34.057 UTC [orderer.consensus.etcdraft] Save -> WARN ce8 slow fdatasync

The Raft protocol, and pretty much everyother consensus protocol, writes data to the disk during its runtime. Fabric uses the etcd implementationof Raft, and it is single threaded, so while it writes

Hello there everyone, like many I am coming here to seek help from support. I was wondering if you are familiar with the following warnings and errors inside orderers containers' logs : "slow fdata