Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 26 March 2021 11:00am to 12:00pm (GMT-04:00) America/New

Thank you Vitalii, sounds good. Based on our side conversation, I've scheduled you for April 14th on the contributor meeting page -

Hi Mark, Thank you for your response and for your helpful direction! The explicit designation of endorsing peer at transaction submit was exactly what I was looking for. After

Hi Nik, Thanks for answering. I confirm the chaincode has been committed to the channel: peer lifecycle chaincode commit -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com

Hi, Can you confirm that the chaincode has been committed to the channel? Or can you do a docker ps to confirm that the chaincode containers have started. This error looks like the chaincode may not

Using the default configuration I can run all the functions inside the application folder of commercial paper on test-network without any problem If I edit the default signature policy in the

Thank you for your time. I just ran the test-network (after your contribution) but the error remains. My steps were: make docker clean, make docker, make native, copy the bin into fabric samples.

Hi David and all! I would like to propose one more item for March 31st agenda. We would like to open a discussion on our RFC: https://github.com/hyperledger/fabric-rfcs/pull/44 I am planning to attend

You might need to set some discovery interests for the private data collections you are using. See the "using chaincode to chaincode calls and collections" section on this page for

Hi Indirajith, Yes it is better to use dedicated MSP for the ordering orgs. This means a business organization may use multiple MSPs to run peers or orderers. You can find details on the MSP concept

Reminder: Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 26 March 2021, 11:00am to 12:00pm, (GMT-04:00) America/New

Hello Fabric community, I am encountering a couple issues when accessing/writing data to a Fabric (2.3) network from a Node.js client. I have a 4-org network running on 4

This is working as expected. You updated the size field but not the version field. The read set check only checks the version field. It is up to the chaincode to check other fields such as asset

Hi, I was trying to test out the endorsement policy feature of Fabric with the Running a Fabric Application tutorial and I have encountered a few questions/issues. Instead of using LevelDB, I up the

I had some time this morning so I played around with the peer image created on linux/aarch64 (linux/arm64). To get to the bottom of why the program was dying during initialization, I commented out all

Dear Fabric Community, I would like to know what is the best practice or prefered method to design a fabric network in 2.x versions? Shall we have orderers in the same organization as peers or should

Hi guys I looked at several git branch prefix release-1.4-BFT, what is the difference between them? What is the correct version for docker https://hub.docker.com/r/smartbft/fabric-peer?

The RFC draft has been submitted, here: https://github.com/hyperledger/fabric-rfcs/pull/44 Please review! -- // Vitalii Demianets @ norbloc AB

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

Yeah, they’re all my commits so I’m very familiar with them. The change you’re referencing this time was required to get through the link phase in the alpine containers but the binaries in the