PoS_EVM
/
woop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
The core protocol of WoopChain
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
5620 Commits
46 Branches
191 Tags
64 MiB
 
 
 
Tag: Branch: Tree: f338c9a8fa
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f338c9a8fa'
${ noResults }
woop/api/proto/discovery
History
Leo Chen 0ddcbdca1a
[pingpong] remove pong messages from discovery service 		5 years ago
..
pingpong.go [pingpong] remove pong messages from discovery service 5 years ago
pingpong_test.go [pingpong] remove pong messages from discovery service 5 years ago
readme.md [pingpong] remove pong messages from discovery service 5 years ago

readme.md

Ping

Ping message sent by new node who wants to join in the consensus. The message is broadcasted to the shard. It contains the public BLS key of consensus and the peerID of the node. For backward compatibility, it still contains the IP/Port of the node, but it will be removed once the full integration of libp2p is finished as the IP/Port is not needed.

It also contains a Role field to indicate if the node is a client node or regular node, as client node won't join the consensus.

TODO

The following two todo should be worked on once we have full libp2p integration. For network security reason, we should in general not expose the IP/Port of the node.

-[] remove peer info in Ping message, only keep peerID, which should be sufficient for p2p communication.