The issue is that a prebuilt binary for protoc-gen-grpc-java is NOT available for the Arm architecture ( https://repo.maven.apache.org/maven2/io/grpc/protoc-gen-grpc-java/1.23.0/ ). You will need to b

#fabric-chaincode

Adding usages does not limit the usages; it increases the potential usages. Of course usages are only relevant for consumers which honor usages. ----------------------------------------- Gari Singh Di

#fabric-questions #fabric

Why do you want to add additional (extended) key usages to the enrollment certificates? They currently contain the minimum set for their intended purpose: digital signatures. And we intentionally do n

#fabric-questions #fabric

The core requirement for certificates for Fabric nodes is that they be EC (Elliptic Curve) certificates. You can use any tool you like as the certificate authority for issuing these certificates. open

https://stackoverflow.com/a/63191241/6160507 ----------------------------------------- Gari Singh Distinguished Engineer, CTO - IBM Blockchain IBM Middleware 550 King St Littleton, MA 01460 Cell: 978-

#fabric-ca #tls #ssl

You should not be using `ca-cert.pem` as the TLS server certificate. If you do not specify a TLS key/cert, Fabric CA generates `tls-cert.pem` which will include the SANS configured via ```FABRIC_CA_SE

There is no support for authenticating to a Docker registry within the peer. Iy your private registry requires authentication, then you will need to pull the images on the host where the Docker daemon

#fabric-chaincode #docker #hyperledger-fabric

First, you really should no longer be using Fabric 1.2. We are not doing any bug fixes on it. We currently have Fabric 1.4 which is an LTS release although it's now starting the end of its lifecycle.

#fabric-ca #fabric-ca-client #fabric #hyperledger-fabric

Have a look at https://hyperledger-fabric.readthedocs.io/en/release-2.2/raft_configuration.html#configuration You'll see that each channel has its own Consenters section. All Raft nodes must currently

Currently, you'd add Node D to the system channel. The system channel essentially tracks all potential cluster members for application channels. We have an RFC approved and development underway to rem

The easiest thing to do is to find the CKA_ID attribute of the private key stored in the HSM and then set the AltID property for the PKCS11 BCCSP. AltID was added in 1.4.6 as I recall to help facilita

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 cod

The desired solution for this is to allow peers to join channels starting from the latest config block rather than requiring starting from the genesis block. The checkpoint/archive feature will also h

#fabric-orderer #raft #hyperledger-fabric

You are really asking two separate questions here. 1. ORDERER_GENERAL_TLS_ROOTCAS Strictly speaking, you don't necessarily have to set this at all. This config parameter is used by the orderer to dete

There is a config value for each channel named "HashingAlgorithm". This is not currently configurable and it set to SHA256. ----------------------------------------- Gari Singh Distinguished Engineer,

What are you trying / hoping to do? There is no "policy" per se and strictly speaking there is no guarantee that the transactions will be ordered in the exact order in which they were sent. That being

It's not necessarily that it's not a best practice, it's just that it's not really a complete solution for overall channel lifecycle management. Plus some people prefer to have a little more control a

#configtxgen

Adding an organization to the consortium serves two purposes: 1) The consortium has the policies which allow channels to be created. Typically any organization that is a member of the consortium has t

How are you creating the root CA certificate? Are you having Fabric CA autogenerate it's root or are you generating the root yourself? Both fabric-ca-server and fabric-ca-client set the validity perio

#fabric #fabric-questions

Your certificate Common Name: peer0.trustedchain.it Issued By: trustedchain.it Issuing Certificate: ca.trustedchain.it Serial Number: 1283279491DA9E086A360570DBD9C5FC67B61833 Signature: ecdsa-with-SHA

#fabric #fabric-questions