* Implement Chain Swaps for receiving
* Send: validate if we have sufficient funds (#321)
* Implement Chain Swaps for receiving
* Fix rebase of flutter_rust_bridge version
* Send: validate if we have sufficient funds
* Re-generate FRB
---------
Co-authored-by: Ross Savage <hello@satimoto.com>
* Chaim swap claim: remove refund_tx arg (#328)
---------
Co-authored-by: ok300 <106775972+ok300@users.noreply.github.com>
* feat: switch to pending state when receive lockup is in the mempool
* rebasing
* fix: move socket update logic to sub-crate
* Update payments query, to avoid duplicate Receive Swaps
This can happen if the app is stopped before the temporary lockup tx is removed from the DB. The Receive Swap would then forever result in two payments in list_payments.
* Add comments to clarify use of temp lockup txid
* Re-generate flutter bridge bindings
* feat: set Payment `tx_id` as optional and change `list_payments` logic
* fix: debug typo
* fix: undo `remove_temporary_tx` changes
* fix: switch to full join rather than manual filtering
* fix: bindings
* fix: improve error handling when tx data is not present
* fix: RN bindings
* fix: exclude Created receives from the list
* fix: fixing nits
* Re-generate FRB bindings
---------
Co-authored-by: ok300 <106775972+ok300@users.noreply.github.com>
* feat: add random keypair generation
* Encapsulate decode_keypair in SendSwap::get_refund_keypair()
* Add refund_tx_id and refund_tx_amount_sat to Payment
* fix: remove blocking on refund
* fix: change `refund_private_key` order
* fix: rebasing
* fix: set `next_unused_address` as refund output
* Handle refunds in `get_info`, `list_payments` (#226)
* Exclude refund txs from payment list
* Adjust balance calculation to account for refunds
* fix: revert boltz changes and fix locktime
* Replace subquery with LEFT JOIN to get refund data
* Rewrite locktime check for more clarity
* Rewrite locktime check for more clarity
* Fix select_payment_query in case of refunds
* Include boltz-client fixes (handling of unwraps for failed broadcasts)
* Cargo.toml: Use boltz-client branch instead of commit
---------
Co-authored-by: ok300 <106775972+ok300@users.noreply.github.com>
* Rename swap tables: remove ongoing_ prefix
* Add swap status enums and filtering
* Swap-in: add claim_txid
* Swap-out: add claim_txid
* resolve_swap: Don't remove swap when complete
* Fixups after rebase
* Remove unused method
* Consider payment as pending based on confirmations
An onchain payment with no confirmations is considered
pending. The previous logic of converting pending swaps
into pending payments is removed, since we may have
pending swaps that should not result in pending
payments (for example on Receive, before the invoice
is paid).
* Fix swap-in query
* GetInfoResponse: fix balance, include pending
* Remove unused method
* Re-generate flutter bridge files
* Re-generate RN bindings
* Fix payment_type detection in list_payments
* Send: persist to DB when claim tx is seen
* Receive: fix occasional error when broadcasting claim
* Remove fixed TODO
* Receive: only rescan on testnet, where Electrum is used to broadcast
* Log more details when broadcasting fails
* Improve AlreadyClaimed error detection and handling
* Rename SubmarineSwapStatus::Initial to Created
* Split pending payment types into separate field status
* Rename swap status enums
* Fix INSERT query
* Bump lwk libraries
* Simplify Receive try_handle_reverse_swap_status loop
* Change resolve_swap to insert_or_update_payment
* Refactor payment data persistence
* Remove unused dependency
* Bump LWK dependencies
* Rename reconcile_payments_with_onchain
* Rename try_claim_v2
* Rename address() to next_unused_address()
* Move all claim persistence writes in try_claim
* Flatten Payment struct
* Re-generate bindings
* Expose sync() in service interface
* Set Send ws stream as nonblocking, use singleton stream
* Send_payment: sync() before handling new state
* Sync() on sdk.connect()
* Remove unused args from list_payments()
* Receive: rename DB field redeem_script to response JSON
* Convert to and from internal structs to persist CreateResponse JSON
* De-duplicate internal CreateResponse structs to prevent storing same field twice
* Schedule a periodic sync() thread on startup
* Persist swap states and add methods to transition between them
* Handle unwrap() when subscribing for WS updates
* Status Stream: handle remaining unwraps() and TODOs
* Consolidate status transitions into two SDK methods
* Status Stream: reconnect and resume tracking on disconnect
* Remove superfluous TODO
* Send swaps: correctly transition to Complete even if app killed during send_payment()
* State transitions: Move SQL queries to persistence layer
* Send: handle edge TransactionClaimed edge-case
* Send: mark as Complete after we check the preimage
* Send: remove marking as Complete on TransactionClaimed
