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

Hello - If I am not mistaken, Fabric chaincode uses the X.509 certificate of the caller to ID the caller. But the public certificate is meant to be shared and not a secret so what prevents someone

Hello All ! I hope you are in safe and healthy. I opened an issue at https://jira.hyperledger.org/browse/FABB-147 with my considerations and log files about this problem. I will appreciate if you

Hello All ! I hope you are in safe and healthy. I opened an issue at https://jira.hyperledger.org/browse/FABB-147 with my considerations and log files about this problem. I will aprecciate if you

Hi all, I'm wondering if there's a mechanism for specifying that the hashes of private collection keys and values should not be disseminated beyond the peers of that private collection. Basically my

All, We will hold thedocumentation workgroup call this Friday -- with both an Eastern hemisphereand Western hemisphere call. Please feel free to come along, especiallyif in these difficult times you'd

Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 27 March 2020, 6:00am to 7:00am, (GMT+00:00) Europe/London Where:https://zoom.us/j/6223336701 View

Looking at the docs for fabric-ca-client Node library, it seems there are 2 ways one could register a new user. Method 1 would be to use

Thanks Gari for your quick response. Yes fabric-sdk-node release 1.4's channel class has all these methods. I am using Hyperleger fabric 2.0 with fabric-sdk-node(Beta).The channel class in beta

The are all available as methods on the Channel class: https://hyperledger.github.io/fabric-sdk-node/release-1.4/Channel.html ----------------------------------------- Gari Singh Distinguished

Chain code life cycle endorsement is not working when following changes made in configtx.yaml.LifecycleEndorsement: Type: ImplicitMeta Rule: "ANY Endorsement"Endorsement: Type: ImplicitMeta

Hi Team, In Hyperleger Fabric 2.0 - How to queries QueryInfo, QueryBlock, QueryBlockByHash, QueryBlockByTxID, QueryTransaction and QueryConfig using fabric-sdk-node client.As I can see these methods

Hi, We had the same issue in our network. To solve it, we found a way to persist the following folder in each orderer: /var/hyperledger/production/orderer/etcdraft Without it restored after a restart,

this is not a "bug", this isa natural product of messages being gossiped out of order which is howgossip works. This is a warning, not an error... ifyou see it repeatedly only then you should be

Is this fixed in the 1.4.4 version LTS as we plan to upgrade the network in the coming weeks?

Ignore it, it's a transient warning. It happens if you get a state info messagesigned from a node which you did not yet receive its certificate. You will eventually receive the certificateand be able

Environment HLF (1.4.2) Orderer (RAFT 3 Node) 2 Orgs (adding 3rd Org) Running on multiple hosts (Docker Swarm Cluster) Steps Followed Configtx.yaml file contents # Copyright IBM Corp. All Rights

We could revoke an user successfully. But, unable to update the channel with crl details. We are getting below error Unexpected error error applying config update to existing channel 'trusttrace':

Fabric supports ECDSA for signature currently. There're several non-official work to let it support other crypto standards. For chaincode/client encryption, you can choose whatever type. -- Best

> I then wonder why latest fabric-ca user guide mentions about supporting RSA? Because fabric-ca supports the management of certificates using RSA; you just can't use them with Fabric. -- Matthew