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
I've been thinking about the current fee structure and there may be some problems with it.
If my understanding of it is correct, there isn't any natural way to incentivize balanced channels.
I've summarized my thinking and a potential solution in this document .
In the large scheme of things it may be early to discus details like this one, but these small incentive may be quite important for the overall health of the network.
If you all believe there might be some merit in this line of thinking I can spend some more time formalizing a more proper implementable proposal and run some simulations to verify it's impact on throughput and robustness.
// John-John Markstedt
The text was updated successfully, but these errors were encountered:
Closing this outdated issue: feel free to re-open with concrete proposed changes. Backwards-compatibility requirements will probably make it a no-go to change the existing fee structure (and we should challenge the fact that channels have to be balanced, this is an assumption, not a general truth), but proposals like inbound fees are trying to tackle this.
I've been thinking about the current fee structure and there may be some problems with it.
If my understanding of it is correct, there isn't any natural way to incentivize balanced channels.
I've summarized my thinking and a potential solution in this document .
In the large scheme of things it may be early to discus details like this one, but these small incentive may be quite important for the overall health of the network.
If you all believe there might be some merit in this line of thinking I can spend some more time formalizing a more proper implementable proposal and run some simulations to verify it's impact on throughput and robustness.
// John-John Markstedt
The text was updated successfully, but these errors were encountered: