Hello – yes I’ve got an example of that… somewhere… I’ll push it a github repo as it’s a useful example Thanks Matthew

There aren’t any specific tutorials on that – it’s a large topic and really beyond of the scope of either a tutorial or mailing list. The best advice is to treat HLF as a backend system-of-record (SOR

Hello; this could be an issue with how node itself was installed. Depending on how node was installed sometimes there are permissions issues with install packages globally (as in this case) Check how

Hi - not sure with LevelDB - CouchDB if configured can be connected to directly. However it's not something I'd suggest as doing as a routine thing - as the chaincode is there to help enforce access c

Hi – the problem is with the `DOCKER_SOCK` not being set – this is the path to the socket used to connect to the docker daemon and this is mounted as a volume within some of the containers. I’d sugges

Thank you for raising the issue; the mistake is in documentation – and I’ve raised https://github.com/hyperledger/fabric/pull/3656 for resoultion. When support for using podman was added, we needed to

Hello – you can return bytes if you wish; What errors did you encounter? Thanks Matthew

Hello; In terms of parsing the history really would need to be parsed to find specific values; depending on the size you could always put the data into a different data structure, so it becomes a clas

#fabric-chaincode #chaincode #database #fabric-questions

Hello, The label is packaged with the chaincode, and is used to prefix a sha hash of the packaged file this makes the “packageid” (aka “chaincodeid”). The chaincode name isn’t in the packaged code, an

Hello; Could you just confirm which chaincode builder you are using? There are a few different ones 😊 Essentially I think you’ve two options Use the same chaincode docker image, but when it’s launched

Hello; Upfront I’ll say that I’m not familiar with the details or subtlies of 835/837 data (being from the UK); but understand they are healthcare records that would need a certain quality of handling

#chaincode

Hello; The Ansible Collection at https://ibm-blockchain.github.io/ansible-collection/ will stand up and configure an IBM Blockchain Platform and whatever peers/orderers etc you want. This though needs

#production #tools #deployment

Hello; I can focus on the last two points The current Ansible playbooks can be used with the OpenSource Operator, AND the OpenSource Console. Though the playbooks are named ‘IBM Blockchain Platform’ t

#production #tools #deployment

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