You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I need to read the docs/code a bit more, but we could possibly add a pollPeerForJoinedChannels function here so that we don't need to explicitly wait for a GET request on the server. This could be a configuration flag that we set, like 'AUTO_REGISTER_CHANNELS` or something like that.
So I need to read the docs/code a bit more, but we could possibly add a
pollPeerForJoinedChannels
function here so that we don't need to explicitly wait for a GET request on the server. This could be a configuration flag that we set, like 'AUTO_REGISTER_CHANNELS` or something like that.The
peer channel list
function does what we need:https://hyperledger-fabric.readthedocs.io/en/release-1.4/commands/peerchannel.html
The code on the CLI side invokes the
cscc
chaincode on the peer node with theGetChannels
argument:https://github.com/hyperledger/fabric/blob/release-1.4/peer/channel/list.go#L53
You can see the
cscc
chaincode here:https://github.com/hyperledger/fabric/blob/master/core/scc/cscc/configure.go#L211
Access to
cscc
requires that the Fabric Logger user have the correct ACL policy set.The node SDK is really poorly documented but I think this is the right place to look for submitted transactions:
https://fabric-sdk-node.github.io/release-1.4/tutorial-handlers.html
Originally posted by @jeffywu in #10
The text was updated successfully, but these errors were encountered: