ch1bo
commented
2 weeks ago @Trymyrt Would you be interested in naming nodes or rather the opened heads?
About the what: the hydra-node does have a --node-id argument which has a default, making this more compulsory to define could result in people using it .. or not as they would put generic names like "node-1" or "mynode" anyways. So I'd say the key question here really is: How could we get people to give us metadata about their project which we can put on-chain do track it via the explorer?
Could be related to #1655 too. i.e. that we could re-use this "tag" for identifying what head a script gets committed to.
Why
For purposes of monitoring adoption, number of entities involved with Hydra usage and simplifying classification of the data, an opt-in naming protocol for Hydra nodes would be very useful. This will be very useful for the Hydra explorer to help identify, group and compare statistics from different projects using Hydra. It could also conceivably be used for P2P protocols as well, similar to how ADA handles are ubiquitous for wallet identification; as it could perhaps be used in a new standard to specify the nodes with which you want to connect, or verify the identity of the nodes with which you are about to interact, using a human-readable tag.
What
TBD by team
How
TBD by team