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

move min/max payment size into opening fee params #193

Closed
wants to merge 1 commit into from

Conversation

JssDWt
Copy link
Collaborator

@JssDWt JssDWt commented Feb 23, 2024

Fixes #186

This PR requires the operator to update their new_channel_params table to contain the min_payment_size_msat and max_payment_size_msat fields. They are deprecated in the node configuration (however, still good to set the values there as well until they are removed from the code).

@JssDWt JssDWt force-pushed the jssdwt-min-max-payment-size branch 2 times, most recently from 7c60e65 to 8893e7a Compare February 23, 2024 13:10
@JssDWt
Copy link
Collaborator Author

JssDWt commented Feb 23, 2024

Generating an opening fee params hash that includes min/max payment size won't work, because the current clients won't send back these fields yet. So the hash has to exclude these fields. But then we can't trust these fields to be correct when passed in by the client.

@JssDWt
Copy link
Collaborator Author

JssDWt commented Feb 26, 2024

Closing, because these fields will only be included in LSPS2. Will add another PR to replace this one.

@JssDWt JssDWt closed this Feb 26, 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 this pull request may close these issues.

Move {min,max}_payment_size_msat into opening fee params
1 participant