Are you setting up the peer and orderer to communicate with the external CA's HSM? Did you generate the CSR yourself, and thus you have the private key and you provided it to them for import, or did

Hi everyone, I'm trying to use a certificate issued by an external CA trough an HSM integration but it's not working. The peer node (v1.4.7) doesn't start and gives the following output

Hello all, I'm building a university course on Hyperledger Technologies, with focus on Hyperledger Fabric. This course is open source and will be exposed as an Hyperledger Lab. In particular, this

We try to ensure that we do not do anything which would prevent the code from compiling on platforms supported by Golang. That being said, the official open source Fabric deliverable is the source

I am using the following Fabric Versions: 1. Fabric binaries: 1.4.4. 2. Fabric Node SDK version: 1.4.9 (fabric-network, fabric-client, fabric-ca-client). 3. Node.js version: v8.10.0 I wish to perform

Hi, I'm trying to register a user via Fabric Java SDK but I get the error: "Registration of 'UserToRegister' failed: Error adding identity 'UserToRegister' to the database: attempt to write a readonly

Hi Ethan, You can check out a pull request we had recently around this same request with regard to supporting arm64 which has a lot of information and feedback from the Fabric maintainers:

Hi all, I am Ethan. Recently I was working on a MIPS-64 based system. The operation system is Debian like os which runs on MIPS-64 based virtual machine. I am going to run fabric on this

I just wanted to say, this thread is such a stellar example of Doing Open Source Right - a clear explanation of an issue & decision needing to be made, followed by a call for

Hello David, We are also trying to leverage the chaincode as an external service feature since it brings new possibility of deployment model for chaincode... I'm also interested in contributing to

Thank you Pancham and Taku for offering to help with the integration test. Sounds like there is interest to keep the feature moving forward. I've sent you both a note with some additional background

Hello, We started to try the chaincode server feature because we consider the server model is more suitable when HLF is used with Kubernetes. I recently contributed to the implementation of the

I had started to play with this feature sometime back and had a brief chat with you on this topic at Hyperledger conference in Phoenix earlier this year. I am interested in completing the integration

As many of you know, Fabric v2.0 introduced external builders and launchers for chaincode: https://hyperledger-fabric.readthedocs.io/en/latest/cc_launcher.html. This feature is seeing adoption from

dear Fabric ApplicationDeveloper, the next FabricApplication Developer community call is: Thursday25th June - 3pm UTC, 4pm UK time (+1), 11am ET (-5 hrs), 8am PT (-8hrs) - othertime zoneshere. It

Thanks Adhav, I think you've assessed correctly. If the client gets two endorsements back it may randomly pick one of the responses to submit and apply both peer endorser signatures. In this case one

Hello Hritik, 1) As you mentioned about PDC configuration: { "name": "collectionCarPrivateDetails", "policy": "OR('Org1MSP.member')", "requiredPeerCount": 0,

Right, if the chaincode only writes to the collection namespace, you only need to meet the collection endorsement policy. Turning on full debug may provide a hint as to why a signature may be

Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 19 June 2020 4:00pm to 5:00pm (GMT+01:00)

I haven't mentioned any chaincode endorsement policy during deployment thinking that the collection level endorsement policy overrides the chaincode level policy. The collection level policy is: