handle non-static IP for mithril + overcast #142
Description
Technically an overcast issue, but creating the tracker issue here since it directly impacts mithril.
Mithril when running in rpc fetch mode works fine without a static IP assigned to the mithril node - i.e. users can run it from home.
However, in overcast mode, we need a public IP or some way for overcast to register in the turbine tree and participate in the repair protocol etc...the scope of how much participation a node without a static IP has is yet to be decided, but at a bare minimum, they should still be able to get blocks/shreds from the overcast network. the simplest case is that they use 1) remote overcast or 2) an overcast endpoint someone else provides, but this ticket is to explore if they can have more agency in case 2 when they want to run mithril + overcast at home, and not have to rely on an endpoint being provided... its possible the solution is as simple as a peer to peer discovery and the client being resilient to overcast node "hopping", but we need some well defined and well scoped solution for users without static IPs