-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add payment expiry #622
Add payment expiry #622
Conversation
75c048f
to
4dbfe3b
Compare
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.
Looks good. Some small comments.
4dbfe3b
to
944211e
Compare
13a4b72
to
812b31f
Compare
812b31f
to
35f41bb
Compare
1db033b
to
a081d15
Compare
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.
The tests and Notfication Plugin also need updating to accommodate the get_info()
response changes
lib/bindings/langs/swift/Sources/BreezSDKLiquid/Task/SwapUpdated.swift
Outdated
Show resolved
Hide resolved
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.
Other than @dangeross's comments, utACK
a081d15
to
1db411d
Compare
1db411d
to
617a070
Compare
a609502
to
e9e9c6b
Compare
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.
LGTM
e9e9c6b
to
6ddddb1
Compare
Seems like the |
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.
LGTM. Just needs a rebase
We should note its a breaking change in the release @roeierez
fix(clippy): use `clone_if_set` for sync destination fix: revert rebase changes feat: add `expiration_block` to payment details feat: add `blockchain_details` to `GetInfoResponse` fix: rename fields to `<chain>_expiry_blockheight` fix: update `GetInfoResponse` structure fix: address review comments taken from #622 (review) fix: use better error handling for get_info fix: bindings tests fix: ensure blockchain_info is optional in query
e3c89d5
to
c74d8f0
Compare
@hydra-yse we need a following PR in misty breez and change the docs accordingly. Let's hold the merge at least until we have the misty breez change which should be straight forward otherwise the misty build will be broken. |
fix(clippy): use `clone_if_set` for sync destination fix: revert rebase changes feat: add `expiration_block` to payment details feat: add `blockchain_details` to `GetInfoResponse` fix: rename fields to `<chain>_expiry_blockheight` fix: update `GetInfoResponse` structure fix: address review comments taken from #622 (review) fix: use better error handling for get_info fix: bindings tests fix: ensure blockchain_info is optional in query
c74d8f0
to
287746d
Compare
This PR:
liquid/bitcoin_expiration_blockheight
field in the Lightning/Bitcoin type payment details, based on the swap'stimeout_block_height
fieldGetInfoResponse
structure to include two fields only, the wallet information (pubkey, fingerprint etc.) and the blockchain information (tips), so that clients may compare the current tip to the payment's expiration block heightFixes #415