Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node health indicator on liquidity page #33

Closed
rolznz opened this issue Jun 27, 2024 · 1 comment
Closed

Node health indicator on liquidity page #33

rolznz opened this issue Jun 27, 2024 · 1 comment
Assignees

Comments

@rolznz
Copy link
Contributor

rolznz commented Jun 27, 2024

Link to an Alby guide with suggestions to increase node resiliency and payment reliability

Factors:

  • Number of unique channel partners with active channels. 1 = bad, 2 = good, 3+ = great
  • Summed channel balance - completely balanced = great, one sided = bad
  • Average? Channel size - < 1M sats = bad, > 1M sats = good
  • Percent of channels within 20-80% capacity (therefore, hopefully usable for both sending and receiving)

image

@MoritzKa
Copy link
Contributor

MoritzKa commented Jun 27, 2024

I think it is a great start and we should be very transparent about it (e.g. linking to a detailed guide outside of the app). So users can get actionably insights and can even suggest changes to the score.
One important factor for payment success is liquidity along the route. So I thought about including the factor of "Channel Peer quality" according to some ranking (e.g. Lightning Terminal). But that's a very fuzzy approximisation. So I'd leave that out for now.

@rolznz rolznz self-assigned this Jul 1, 2024
@im-adithya im-adithya transferred this issue from getAlby/nostr-wallet-connect-next Jul 5, 2024
@rolznz rolznz closed this as completed Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants