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
If you only rely on what already happened on your channels, people with very little to no routing activity are left in the dark.
Having outside sources like the known graph of nodes or a list of potential channel partners would help to kick start this a little.
Online communities help people with setting up new nodes and share knowledge.
If we could import lists of nodes (optionally with the amount of sats people are willing to put in) and have them rated by LNDG would help to make the most of these offerings.
The text was updated successfully, but these errors were encountered:
yoshimo
changed the title
Make reccomendations for new channels not only based on recent routing
Make recommendations for new channels not only based on recent routing
Oct 18, 2022
I think starting with the LNDg list and validating against an outside source would be best. Currently you could query if a random peer from outside source has been part of your payment history with /routes?=<peer_pubkey>.
It might be an interesting idea to have a page where you can query and see this data more easily.
What if there is no payment history to seed connections with? There are people that want to help the network but have not enough TX or none on their routing yet and want to change that.
If you only rely on what already happened on your channels, people with very little to no routing activity are left in the dark.
Having outside sources like the known graph of nodes or a list of potential channel partners would help to kick start this a little.
Online communities help people with setting up new nodes and share knowledge.
If we could import lists of nodes (optionally with the amount of sats people are willing to put in) and have them rated by LNDG would help to make the most of these offerings.
The text was updated successfully, but these errors were encountered: