centex asked about 1 year ago
Feature Request: Improve Rating Function
Add ability to rate a receiving peer if a channel close is detected.
In a recent triangle swap I was node "B".
Node "A" closed early to both "B" and "C".
Node "C" adjusted their rating to negative I assume because they did not understand their rating is for the node that opened to them.
I have been in similar situations as "C" in other swaps where the peer I opened too closed early and there is no way of rating them.
Obviously not a big deal, but it would be a nice function.
Or alternatively, add a notice when changing your rating to indicate what peer is receiving the rating.
Thanks,
-centex
In a recent triangle swap I was node "B".
Node "A" closed early to both "B" and "C".
Node "C" adjusted their rating to negative I assume because they did not understand their rating is for the node that opened to them.
I have been in similar situations as "C" in other swaps where the peer I opened too closed early and there is no way of rating them.
Obviously not a big deal, but it would be a nice function.
Or alternatively, add a notice when changing your rating to indicate what peer is receiving the rating.
Thanks,
-centex
5 Comments
LN+ Admin wrote about 1 year ago
OK, this has been requested before. I will definitely consider it and work on it. Thank you!
centex wrote about 1 year ago
Cool, thanks!
EnduraUmb-I wrote about 1 year ago
Just a comment on the closing too early. For normal closures easy - you can see who triggered the closure.
Due to automatic forced close it is not always that easy to decide which party has caused the issue. Yes you can see which node did the auto-close but it could be since the partner node was offline / instable while transactions are running. Then the "guilty" node is not the one who did the closure but the node being instable.
... but maybe I did not fully understand all the forced closure mechanisms.
Due to automatic forced close it is not always that easy to decide which party has caused the issue. Yes you can see which node did the auto-close but it could be since the partner node was offline / instable while transactions are running. Then the "guilty" node is not the one who did the closure but the node being instable.
... but maybe I did not fully understand all the forced closure mechanisms.
LN+ Admin wrote 7 months ago
This has been implemented:
https://lightningnetwork.plus/posts/552
https://lightningnetwork.plus/posts/552
centex wrote 7 months ago
Awesome!
Please login to post comments.