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

Reminder: Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 21 February 2020, 4:00pm to 5:00pm, (GMT+00:00)

I tried to register & enroll a user with the name 苏南 on Fabric-CA. The registration is getting successful but getting below error during enrollment.error: [FabricCAClientService.js]: Failed to

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

Hello! We will hold thedocumentation workgroup call this Friday, but there will only be a Westernhemisphere call because Anthony is travelling, and without network access.Apologies to our Eastern

Hyperledger Fabric and Fabric CA v1.4.5 are now available. See details of the included fixes in the release

Hi all, My setup has two peer orgs and one orderer org. I am trying to commit a chaincode after getting approvals from two orgs. But the commit fails due to endorsement policy failure. I have gone

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

hi all, please note thatthe Community call will not run this Thursday - the next scheduled communitycall is Thursday 5th March.. best regards Paul O'Mahony Community Lead- Hyperledger Fabric

Hello everyone, I'd like to propose new metric to monitor certificates expiration. https://jira.hyperledger.org/browse/FAB-17497 Thanks for the "FAB-17000: Warn when certificates are about to

Cancelled: Hyperledger Fabric Chaincode EVM This event has been cancelled. When: Wednesday, 19 February 2020 8:00am to 9:00am (UTC-08:00) America/Los

With NodeSDK v2 beta.3 you will get the required admin `User` object instance for calling the `register` of fabric-ca-client from the fabric-network `Wallet` rather than from the underlying Client

I did more checks and it looks like fabric-ca-client was used before and now a Gateway is used. It also looks like getClient does not work with the instance of Gateway. This looks like a coding error

I email yesterday about an error in 2.0 and registeruser. I understand it is now under peer review. What is the recommended course of action to register a user in 2.0? I checked 1.4 and saw the code

Yes, I have defined Endorsement policies for my peer orgs. But not for the orderer org. Endorsement: Type: Signature Rule: "OR('org1MSP.peer')" Endorsement: Type:

Hi, Your logs say zero of the endorsement sub-policies were defined. Did you define the endorsement sub policies in configtx.yaml for your organizations? See here:

Thank you David Enyeart, As you have suggested, the problem was with credentials and I have fixed them. Now the problem is during the commit stage. Even though both Orgs approved the CC package and

Is there a work around for this?

Hi, I figured out that it's quite difficult to estimate maximum size in advance to align metadata size on each orderer. So we've decided to change to handle archive data at block level, not at

We have a PR in review to fix the following issue Failed to register user "user1": TypeError: gateway.getClient is not a function See https://github.com/hyperledger/fabric-samples/pull/117