1. Messages
  2. Peer communication during chaincode execution

Re: Peer communication during chaincode execution

Kimheng SOK
 

Hi,

My usecase is chaincode need to call external program, in the case of multiple peers, each peer could produce non-deterministic result and the invoke function will return Error: Could not assemble transaction. So all peers need to communicate with each other about the result and compute deterministic result so that the error will not happen. 

This feature could open the possibility to avoid all peers just passively receiving the deterministic result from a client or central entity.
For sure the computation time will increase, because the more peers we have, the more communication need to be done just like gossip protocol. So it is a trade-off .
The good news is hyperledger is a permission blockchain, so the number of peers is limited depend on the use case, so some applications could be useful to have this feature.

Bests,


On Thu, Jan 30, 2020 at 6:14 AM Yacov Manevich <YACOVM@...> wrote:
See https://jira.hyperledger.org/browse/FAB-11980

May I ask why do you need it? what's your use case?



From:        "Kimheng SOK" <sok.kimheng@...>
To:        hyperledger-fabric@...
Date:        01/29/2020 11:57 PM
Subject:        [EXTERNAL] [Hyperledger Fabric] Peer communication during chaincode execution
Sent by:        fabric@...



Dear all,

I wonder is it possible for peers to pass message to each other on the channel during the chaincode execution in the context of chaincode developer level not the protocol level? Or we need to modify the gossip protocol it self.

Appreciate for answering the question.
Join fabric@lists.hyperledger.org to automatically receive all group messages.