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

Fee structure #587

Closed
Johnstedt opened this issue Mar 7, 2019 · 2 comments
Closed

Fee structure #587

Johnstedt opened this issue Mar 7, 2019 · 2 comments

Comments

@Johnstedt
Copy link

Johnstedt commented Mar 7, 2019

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

@C-Otto
Copy link
Contributor

C-Otto commented May 12, 2021

Could you provide your document in some accessible format? Maybe host the PDF yourself? I'd be happy to help, if necessary.

@t-bast
Copy link
Collaborator

t-bast commented Sep 18, 2024

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.

@t-bast t-bast closed this as completed Sep 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

No branches or pull requests

3 participants