You need to use -e true flag when you setup network Sent from my Galaxy Tab® S2

Hi, Thank you for reading this mail! We are using hyperledger fabric 2.2 on CentOS 8.2. In our environment, there are some peers and orderers use TLS to communicate each otherand it works

I am using minifabric and I am unable to connect to peer from cli container. Below is the error message that I get: bash-5.0# peer channel list Error: error getting endorser client for channel:

Hi, When I join a new peer or the peer is offline and lags behind the maximum ledger, they are not able to recover. In the next image, I have a channel with 6 peers; the first one is the anchor peer;

Reminder: Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 11 December 2020, 11:00am to 12:00pm, (GMT-05:00) America/New

Yes, check this out: https://hyperledger-fabric.readthedocs.io/en/release-2.2/test_network.html#interacting-with-the-network It is asked to set following env. variables: # Environment variables for

Thanks Prasanth. How can I tell peer to use admin identity, I do not see any command line option to specify the identity to use. Is this driven by an environment variable. It is also not clear which

Yes, Lifecycle operations should be carried out by admin identity.

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

I am logged on a peer container. When I execute any peer command, I get an ACL error. Below is an example: peer lifecycle chaincode querycommitted --channelID mychannel --name basic --cafile

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

Hello; Please check this document for the options.https://hyperledgendary.github.io/docs/goodpractice/nodejs_building_limited_access.html Regards, Matthew. Matthew B White IBM Blockchain

Do we have a way to instantiate nodejs chaincode without internet access?

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:

The recommendation, and defaults as of v2.2, is for all peers to get blocks from an ordering node. You will have more options in terms of permission management if you use separate orgs. "Carlos

Hi All, In a simple case of data dissemination from one to many: there is one entity (must be an Org) that is the only Tx proponent/endorser/orderer and there are other entities that just want to

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

Dear Kai, Beside that chaincode chain call capability, in SDK-node level I prepared a compensational tool in https://github.com/davidkhala/fabric-common/blob/master/nodejs/admin/QSCCProposal.js This

However it limit capability of smart contract, could it support snapshot read or order the lock to resolve this deadlock bug？

User chaincode cannot invoke QSCC, i.e., cross-chaincode invocation, as there is a danger of deadlock, and system chaincode was never meant to be queried in this way. You can still query it directly