Hello, I'm trying to change a chaincode policy using lifecyles. I'm using the following

Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 12 June 2020 4:00pm to 5:00pm (GMT+01:00)

Reminder: Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 12 June 2020, 4:00pm to 5:00pm, (GMT+01:00) Europe/London Where:https://zoom.us/j/6223336701 View

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 12 June 2020 6:00am to 7:00am (GMT+01:00)

For two reasons: 1) At channel creation time, the peers necessarily are not joined to the channel (since the channel doesn't exist yet) and therefore cannot act as anchors. So, from a workflow

I'm writing an RESTful API application to interact with a chaincode deployed on a network, using fabric-sdk-go and the gateway package. My chaincode is successfully building and deploying to the

Why does it not do it as part of channel create transaction?

Hey Antoni, As pointed out by the output of CheckCommitReadiness, with your current network configuration, the peer is looking at both Org1 and Org2 for approvals before the chaincode definition can

Hello, Im stuck at the peer lifecycle chaincode commit command. I execute the following commands until I get an error on the above command. export

Hi All, We will hold thedocumentation workgroup calls this Friday -- with both an Eastern hemisphereand Western hemisphere call. Please feel free to come along, you're alwaysvery welcome. You can

Hello, Does anyone know what this error is about? we get this error when trying to submit a transaction using the fabric-network:2.1.0 library const result =await

thanks for the clarification. From: Tiffany Harris <Tiffany.Harris@...> Sent: Thursday, June 11, 2020 8:49 AM To: siddjain@... <siddjain@...> Cc: fabric@... <fabric@...> Subject: Re: [Hyperledger

Matt, All: As discussed in the thread below, I have raised a draft PR https://github.com/hyperledger/fabric/pull/1392 to decouple "viper" from getKeysRecursive() function. Attached below the test

Hi David, thanks for the reply, I've recreated the network and now it seems to work, I'll save save your hint for possible future problems. Mattia IFIN SISTEMI S.R.L. a socio unico Via G. Medici

Some additional peer logging would help to troubleshoot it: FABRIC_LOGGING_SPEC=info:statecouchdb,couchdb=debug Dave Enyeart "Mattia Bolzonella" ---06/11/2020 05:37:49 AM---Hi, i'm trying to start a

The connection-org1.yaml is copied to the gateway directory from the test-network when the network-starter.sh is run.

Hi, i'm trying to start a peer but I get the error reportet in the below log dump. I can't figure out how to solve it. 2020-06-05 08:41:17.126 UTC [peer] getLocalAddress -> INFO 002 Auto-detected peer

Hello; The Wasm Smart Contracts RFC was discussed on the Contributors Call yesterday. I've added a couple of comments to the Wasm Smart Contract RFC from the discussion. Based on this can ask the

Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 12 June 2020, 6:00am to 7:00am, (GMT+01:00) Europe/London Where:https://zoom.us/j/6223336701 View

Hi, we are looking at the fabric-samples https://github.com/hyperledger/fabric-samples/blob/v2.1.0/commercial-paper/organization/digibank/application/buy.js#L41 let connectionProfile =