You need to use Go 1.13 to build the master branch of fabric ca. ----------------------------------------- Gari Singh Distinguished Engineer, CTO - IBM Blockchain IBM Middleware 550 King St Littleton,

Thanks for pointing this out. This should be resolved now via https://github.com/hyperledger/fabric-amcl/pull/6 which I just merged ----------------------------------------- Gari Singh Distinguished E

Assuming the TLS errors are between the peer(s) and the ordering nodes, then you might need to break things into two steps: 1) Update the user and system channel configs like you did 2) Do not enable

If you look carefully at the configtxgen documentation ( https://hyperledger-fabric.readthedocs.io/en/release-1.4/commands/configtxgen.html#configtxgen), you'll notice the following: -outputAnchorPeer

#configtxgen #hyperledger-fabric

You can use one of the SDKs to build a server application which is specific to your chaincode, etc. The backend of your application will actually communicate with Fabric and you’d create REST APIs spe

#hyperledger-fabric

The Node, Java and Go SDKs all have the ability to use HSMs. The Go SDK uses a similar config to the peer as it basically embeds the bccsp code. The Node SDK allows you to pass in a PKCS11 crypto suit

#hsm #fabric-sdk-node #fabric

The peer CLI currently uses the same config as the peer. If you point the peer CLI at a core.yaml file which uses PKCS11 for the BCCSP (same as you would do for the peer), then things should work. If

#hsm #fabric-sdk-node #fabric

Environment variables act as override for the config persisted in core.yaml (or orderer.yaml for the orderer) and are not persisted. ----------------------------------------- Gari Singh Distinguished

The fabric-ca-client will always store things in the MSP folder structure you have below: msp ├── admincerts ├── cacerts ├── keystore ├── signcerts └── tlscacerts So you can either reference the TLS c

I'm honestly a bit tired of your tone. It is unclear to me what you are looking for here. People responded to the salt / hash issue and the documentation has been updated. You offer no alternatives an

#fabric #fabric-questions #fabric-dstorage

2+10000000000 ----------------------------------------- Gari Singh Distinguished Engineer, CTO - IBM Blockchain IBM Middleware 550 King St Littleton, MA 01460 Cell: 978-846-7499 garis@... -----

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

#kafka #fabric

I too believe that the documentation belongs with the code. I also do not believe that every person who contributes should become a maintainer ... especially when they do not have a history of actuall

Hi Atsushi - Thanks for sharing your efforts to date. Overall, I like the idea of providing a utility to do this as generally we tell people that they can do this but don't provide any tools for doing

There's not actually a flag ... you simply specify the full path to the package (e.g. ./mypackage.cds) as an argument (e.g. after all the flags). peer chaincode install -n mycc -v 1.0 -p github.com/my

You can actually specify the package as an argument to the command: peer chaincode install [flags] pkg ----------------------------------------- Gari Singh Distinguished Engineer, CTO - IBM Blockchain

It was not really a Node SDK limitation but rather a node-gyp issue. We require node-gyp as we use native modules. The latest versions of npm ship with versions of node-gyp which support Python 3.5, 3

#fabric-sdk-node

If you run "install" with the package option on two different machines then instantiation can fail due to the mismatch issue. Did you try packaging first and then installing the same package on both p

#fabric-chaincode

Looks like you were actually not persisting the storage for your peers (ledger, installed chaincode, etc). It seems the orderer was still running so the channel already considered the chaincode to be

#fabric-chaincode

Private keys are never sent anywhere. Only public keys are included with transactions. If you are using the fabric-ca-client or any of the SDKs, by default privates keys are created on the local file