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
Peers are identified by ENR or by p2p peer IDs. These are super long hex numbers which can contain common prefixes/suffixes and hard for humans to parse.
It is very hard for humans to know which peer is having issues (from the logs), or to communicate about specific peers to other humans.
Proposed solution
Generate deterministic human friendly names (adjective+noun) for each peer from its p2p public key. Use these names throughout when referring to peers.
Add a getName method to each operator in the cluster definition.
Infer the name from the peer p2p public key (inside the ENR).
Add a Name field to the p2p.Peer struct, populate this with the getName method.
Replace all p2p.ShortID() logs with ("peer_name", peer.Name)
The text was updated successfully, but these errors were encountered:
1. Add deterministic function for peer names by running a polynomial hash function on peerID string.
2. Replace all `p2p.ShortID(pID)` with `p2p.PeerName(pID)`
category: feature
ticket: #585
Problem to be solved
Peers are identified by ENR or by p2p peer IDs. These are super long hex numbers which can contain common prefixes/suffixes and hard for humans to parse.
It is very hard for humans to know which peer is having issues (from the logs), or to communicate about specific peers to other humans.
Proposed solution
Generate deterministic human friendly names (adjective+noun) for each peer from its p2p public key. Use these names throughout when referring to peers.
getName
method to eachoperator
in the cluster definition.Name
field to the p2p.Peer struct, populate this with thegetName
method.p2p.ShortID()
logs with("peer_name", peer.Name)
The text was updated successfully, but these errors were encountered: