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

While I hold that those changes do in fact make building Fabric for ARM64 possible, as Matt mentioned it's not officially supported. I can say that I've tested that change on PI4 and when done right

Sorry I misclick the commit link. The correct one is this. Also, this answer made me believe that raspberry pi4 is supported (even at an early stage). I can take a look on

Nikos, the Fabric team doesn’t do anything to support Raspberry Pi. The commit you’re referencing enables _development_ of Fabric on the new arm64 based M1 macs using the code in the core Fabric

In latest commits you added support for fabric in raspberry as described here. I am trying so many days to build fabric-chaincode-java without success (the help in the chats or the list

Hello,When I am running docker run --rm hyperledger/fabric-peer:latest peer version the command does not return anything. Why?The command docker run --rm hyperledger/fabric-orderer:latest orderer