-
Notifications
You must be signed in to change notification settings - Fork 138
[custom channels]: enforce minimum amounts #1252
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
4db4b15
rfq+rfqmath+tapchannel: move on-chain carry amount const to rfqmath pkg
guggero f99ab64
rpcserver+taprpc: rename AssetAmount->AssetMaxAmount in buy quote
guggero 2e8bf3d
rfqmath: add MinTransportableUnits helper function
guggero 1ec0ed6
taprpc: add MinTransportableUnits to buy quote
guggero 9e0a325
rpcserver: restrict invoice minimum asset unit amount
guggero 4e1979c
rfqmath: add MinTransportableMSat helper function
guggero f148369
taprpc: add MinTransportableMSat to sell quote
guggero ddd99db
rpcserver: refactor invoice parsing for re-use
guggero 5fcff90
rpcserver+taprpc: reject small invoice payments
guggero File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we have to send out 354 sats? Or does this only apply while we push 354 sats each time?
Assuming that's lifted, then we only push an asset value, allowing the routing node to send any amount outgoing, since we don't need to anchor any assets to that outgoing HTLC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this calculation only applies until we add the symmetric HTLC trick. Then we can delete both of these functions (I think).