Hello; So start with the Fabric Gateway SDKs (https://hyperledger.github.io/fabric-gateway/) available in Go ,Nodejs and Java This will let you connect an application to Fabric, and invoke transaction

Hello, I’d suggest looking at the `fabric-contract-api-go` that will do exactly what you want. Specifically https://github.com/hyperledger/fabric-contract-api-go/blob/main/tutorials/getting-started.md

#hyperledger-fabric

Hello, just to confirm have you looked in the container that is running the chaincode. It's a separate docker container. The Winston logger that the chaincode libraries use is also available via the c

Hello Nikos; Each organization would have it’s own connection profile – so it connected to it’s own peers. As each organization could be a separate company, it’s unlikely they would want to give out t

Could you explain a bit more about what you're doing please... are you trying to create a docker container to run chaincode-as-a-service?

#fabric

Hello… The short answer is yes if you use the ContractAPI for the smart contract; especially so if you are able to use strongly typed language such as Java TypeScript, and Go More detail: From the cli

Hello; So there are two options you can pursue here. In the core.yaml you can configure the docker image that is used as the base for these containers. For example the Node chaincode as it’s fabric-no

Hello; The external chaincode – and specifically the external chaincode-as-a-service is a very valuable feature, and makes deployment into a cloud environment so much easier. The latest Peer packaging

Hello; The external chaincode – and specifically the external chaincode-as-a-service is a very valuable feature, and makes deployment into a cloud environment so much easier. The latest Peer packaging

Hello; So for Fabric v2.4 - the node version used for the nodeenv container was updated to v16 (https://github.com/hyperledger/fabric-chaincode-node/blob/a53121f00afc309d3503f45ca6d728d0f8415677/docke

#fabric-peer #fabric #fabric-questions

Hello We wanted to get the community's views and input on possible changes to the use of docker in FabricSamples. This is in light of the recent changes to Docker Desktop's licensing model. Our concer

Hello - the short answer is "no, not really". The 1.4 SDKs did have some limited ability to do administrative actions; these were removed in v2 - though without a direct replacement. There have been c

Proof-of-concept and education - not a problem Regards, Matthew. Matthew B White IBM Blockchain Solutions Architect Email me at WHITEMAT@... Find me on StackOverflow, and generally at calanais.

Thanks for using the test-network-k8s! Not spotting anything obviously wrong with the chaincode deployments and channel creation.. Keep in mind though that the 'network' script here is just a convenie

Hello; Can I suggest that you raise an issue on the github hyperledger/fabric-chaincode-java repo? Though to check that you can call `helloworld()` directly from `invokeChaincode` without having to ca

#fabric-chaincode

Hello; On Approach #2.. > Do we still need to install the chaincode in the peer, if we are running the peer in dev mode inside a docker container ? No, the approach you are doing is basically correct;

#fabric #configtxgen #fabric-peer #fabric-orderer

Hello; The 2.3 release was an interim/development release. 2.2 being the LTS. There wasn't a docker image for farbic-javaenv:2.3 released. The quick way around this is to pul down the fabric-javaenv:2

#docker #fabric-peer

Hello For k8s information, check https://github.com/hyperledger/fabric-samples/tree/main/test-network-k8s As to why the processes in the docker containers run as root, I really don't know. It may just

Hello. version 2.2 is the current Long-term support release (LTS). So you should target this version. Regards, Matthew. Matthew B White IBM Blockchain Solutions Architect Email me at WHITEMAT@...

In addition, the chaincode-as-a-service model is also useful here, as it can be started/stopped in much the same way as dev mode. Regards, Matthew. Matthew B White IBM Blockchain Solutions Architect E