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
In use of gRPC. In order to better process block data, methodGetBlock should include some info related to the proposer entity address or proposer nodes address.
Now I use this method
methodGetBlock = serviceName.NewMethod("GetBlock", int64(0))
got the result :
From the rusult, we can see block proposer only has node's consensus public key: is "hOwR6glpRGOpwtaO4x6CAfgDyAg=", No entity address information, no node address information. There is no way to related them.
The text was updated successfully, but these errors were encountered:
The proposer address corresponds to (in case of the Tendermint consensus backend) a Tendermint address computed from the node's consensus key. This information is available in .Consensus.ID in the node descriptor.
So all the information is already there you only need an index from consensus addresses to node IDs. Such an index exists internally, but is currently not exposed and it may be a good idea to expose a way to query this information (until then you could build the index yourself).
kostko
changed the title
methodGetBlock need include proposer entity address or nodes address.
Registry query for nodes by consensus address
Jun 1, 2020
it would be very good to have a way to know which entity proposed each block. appreciate having an api that allows me to query all blocks and determine the entity. will help flag issues with given entities
In use of gRPC. In order to better process block data, methodGetBlock should include some info related to the proposer entity address or proposer nodes address.
Now I use this method
methodGetBlock = serviceName.NewMethod("GetBlock", int64(0))
got the result :
From the rusult, we can see block proposer only has node's consensus public key: is "hOwR6glpRGOpwtaO4x6CAfgDyAg=", No entity address information, no node address information. There is no way to related them.
The text was updated successfully, but these errors were encountered: