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

Figure out how to communicate on-chain fees to the user #55

Closed
tnull opened this issue Mar 29, 2023 · 1 comment
Closed

Figure out how to communicate on-chain fees to the user #55

tnull opened this issue Mar 29, 2023 · 1 comment

Comments

@tnull
Copy link
Collaborator

tnull commented Mar 29, 2023

We currently have no good way of communicating what on-chain fees the user could expect, e.g., for channel opens. It's however not immediately clear to me how we want to expose to-be-expected fees without just dumping the whole complexity of fee estimation on the user.

We probably don't want to complicate the connect_open_channel interface with yet another parameter, but maybe a combination of giving some visibility into our current fee estimate cache and the capability to set a fee rate upper bound via Config might be an option here,

@tnull
Copy link
Collaborator Author

tnull commented Feb 20, 2024

Closing as duplicate of #176

@tnull tnull closed this as completed Feb 20, 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

1 participant