Thank you guys so much, it's really helpful!

Great!!! Em sex., 17 de dez. de 2021 17:34, David Enyeart <enyeart@...> escreveu:

Hyperledger Fabric v2.4.1 is now available! v2.4.1 introduces a "Chaincode as a service" sample builder into the fabric-peer docker image, making it easier to manage smart contracts in Kubernetes and

Hello, I am working with a team and we are trying to use an _existing_ deployment of a Hyperledger Fabric 1.4 network that is private (this becomes important later), as configured on the AWS Managed

Hi everyone, fabric-sdk-java v2.2.10 and v1.4.14 have been published to Maven Central. They update the Log4J dependency to 2.16.0 to address both CVE-2021-44228 (Log4Shell, which was already patched

Hi! The chaincode has a unique identifier in the network when it is running. If a chaincode calls itself (another function) using invokeChaincode method, an error will occur. You have to call the

Thanks for your attention: https://github.com/hyperledger/fabric-chaincode-java/issues/218

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

Environment: fabric release-2.2 My chaincode named vulnerable is as follows: When I invoke helloworld directly, it gives me responce "helloworld", everything works fine. But when I invoke

Hi, thanks for your reply. I'm using fabric release-2.2, and deployed a test network on a clean environment. I have the following phenomena: (1) When I use cmd docker exec peer0.org1.example.com peer

You're right, the private data collection should have nothing to do with that error. That error typically means state is not identical across the peers and therefore the chaincode results do not

Scenario: 1. I have a chaicode named vulnerable with a collection-config as follows: and transaction functions as follows But I didn't give any endorsement policy to this chaincode, which means its

Extending the previous question. How can I use the scripts to deploy a second channel with an other chaincode (the asset-transfer-basic but with an other name in avoid problems in the peers). I tried

Hi, Gourav. I've forwarded this to the Fabric mailing list, which is the best place to get an answer. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones Calendar

I am aware of companies that use validation plugins to complement the built-in endorsement policy checks because they have an atypical adversary model. I also think that endorsement plugins are useful

The work item that removed BCCSP plugin support explains the rationale and points to a Go issue about plugin restrictions: https://jira.hyperledger.org/browse/FAB-15338 In a nutshell, nobody was using

Hi, Sam. I've added the Fabric list so that the other maintainers can see it. Ry-- Ry Jones Community Architect, Hyperledger Chat: @rjones Calendar

Private Chaincode Lab When: 12/14/2021 8:00am to 9:00am (UTC-08:00) America/Los Angeles Where: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Organizer: Marcus

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;

Hello, Older discussion on that topic: https://lists.hyperledger.org/g/fabric/topic/74860557#8508 In one of the threads above David Enyeart shared a nice section regarding PDC vs