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
Some people have offered to run "altruistic relays" for iroh-net. However, in order to run such an altruistic relay, you would need a way to throttle all connections that don't switch to direct after some time, otherwise there would be a chance that the operator of an altruistic relay would end up with a huge bandwidth bill.
This is something we ourselves might need at some point, e.g. if a heavy app that builds on iroh-net goes viral. So it might be a good idea to build this in proactively.
The text was updated successfully, but these errors were encountered:
For context (albeit out of the scope of this issue):
An altruistic relay would be discoverable from a Mainline hardcoded topic (like content-discovery example).
By default, Mainline returns ~20 random addresses so you get the load-balancing you need.
But that topic might be spammed, so the ultimate solution might be a separate DHT (using the rust's Mainline library) so that only "good" relays are kept in the routing table, so nodes would test each other's for holepunching, and not just responsiveness for ping requests.
Some people have offered to run "altruistic relays" for iroh-net. However, in order to run such an altruistic relay, you would need a way to throttle all connections that don't switch to direct after some time, otherwise there would be a chance that the operator of an altruistic relay would end up with a huge bandwidth bill.
This is something we ourselves might need at some point, e.g. if a heavy app that builds on iroh-net goes viral. So it might be a good idea to build this in proactively.
The text was updated successfully, but these errors were encountered: