* rescan_onchain_swaps: separate internal (scheduled) from external (manual) call
* Add TODOs for supporting more utxos in BtcSwapTx::new_refund
* Update boltz-client to build refund tx with all utxos
* list-refundables: show refundable amount, not swap amount
* Chain swap cooperative refund: fix "Liquid chain used for Bitcoin operations" error
* Revert "Chain swap cooperative refund: fix "Liquid chain used for Bitcoin operations" error"
This reverts commit 8a325e3c13b7e9b54b9f5256bea206989eac53b6.
* Bump boltz-rust to include sign_refund fix
* Bump boltz-rust to include sign_refund fix for non-coop refund
* Fix state handling when incoming chain swaps are refunded
* Move swap state change inside refund_incoming_swap
* Bump to latest boltz-client branch version
* v0.4.0:
Fix SDK checkout (#528)
update version to 0.4.0-rc3
update version to 0.4.0-rc2
Fix details fields error
Add notification plugin CI
update version to 0.4.0-rc1
* Flutter uniffi
* Set on-demand resources
* Do not build non-uniffi libraries
* Change iosLibName
* Add BreezSDKLiquid as on demand resources
* Use downloaded framework
* Add Sources to published flutter package
* Set OTHER_LDFLAGS
* Add logging
* Refactor library initialization logic and throw an error if initialization fails
* Do not statically link framework on production
* Use uniFFI headers to generate FlutterBreezLiquidBindings
* Re add frb header
* Correct the library name
* Remove static_framework
* Move source header files
* Copy iOS podspecs to macOS folder
* Update version of macOS podspecs
* Remove Windows & Linux support
* Remove CMake scripts
* Remove breez_sdk_liquid.podspec from version script
* Cleanup older build scripts used by melos & just recipes
* Remove softlink & copy recipes
Add recipe descriptions
* Rename link-uniffi recipe to link-headers
Make sure headers are linked after uniffi is built
- Remove just gen recipe
Add recipe descriptions
* Set package versions on production files as well when publishing
* Include bindings project on melos script hooks
* Flutter uniffi
* Set on-demand resources
* Do not build non-uniffi libraries
* Change iosLibName
* Add BreezSDKLiquid as on demand resources
* Use downloaded framework
* Add Sources to published flutter package
* Set OTHER_LDFLAGS
* Add logging
* Refactor library initialization logic and throw an error if initialization fails
* Do not statically link framework on production
* Use uniFFI headers to generate FlutterBreezLiquidBindings
* Re add frb header
* Correct the library name
* Remove static_framework
* Move source header files
* Copy iOS podspecs to macOS folder
* Update version of macOS podspecs
* Remove Windows & Linux support
* Remove CMake scripts
* Remove breez_sdk_liquid.podspec from version script
* Cleanup older build scripts used by melos & just recipes
* Remove softlink & copy recipes
Add recipe descriptions
* Rename link-uniffi recipe to link-headers
Make sure headers are linked after uniffi is built
- Remove just gen recipe
Add recipe descriptions
* Set package versions on production files as well when publishing
* Include bindings project on melos script hooks
* chore: just version
* fix: remove unused files on "Set package version" step
* copy FFI header files
* [WIP] Add macOS support
* remove example app on Flutter plugin
* Link headers before running ffigen on CI workflow
* macOS: add macos/Sources folder to .gitignore
.
* macOS: Copy iOS sources to macOS sources after downloading bindings
* macOS: copy sources & framework file to macos folder on build-uniffi-swift script
* import breez_sdk_liquidFFI header on plugin file
Update flutter_breez_liquid.c
* cleanup header file artifacts
---------
Co-authored-by: Ross Savage <hello@satimoto.com>
* prepare-pay-onchain: add option for drain in req
* Fix clippy
* ChainSwapStateHandler: gracefully handle building both drain and non-drain lockups
* Send Chain swap: use standard feerate when estimating lockup tx fee
* UDL: move new drain field above the last PreparePayOnchainRequest optional field
* UDL: move new drain field optional
* prepare-pay-onchain: treat normal payment as drain if receiver amount is high enough
If the receiver amount is as high as it would be in case of drain, treat the current prepare-pay-onchain as drain, even if the drain flag is not set.
* build_drain_tx: add optional amount validation
* Add PayOnchainAmount enum to cover amount types (drain, receiver)
* Add ability to find max_receiver_amount_sat for non-drain sends
* Revert "Add ability to find max_receiver_amount_sat for non-drain sends"
This reverts commit 60ee1c768021810f72bc64a8ada69d35b638185e.
* prepare_pay_onchain: treat drain and non-drain cases separately
If the non-drain case is chosen with a receiver_amount equivalent to what drain would have calculated, it results in an error. For drain, the caller has to explicitly choose PayOnchainAmount::Drain.
* CLI: send-onchain-payment accepts optional amount
* CLI: add docs for send-onchain-payment drain arg
* SDK: expand docs for prepare_pay_onchain
* Re-generate RN bindings
* Re-generate flutter bindings
* Integrate webhooks
* Make hash_swap_id optional
* Hash and store the swap id
* Add webhook status include lists
* Remove superfluous webhook statuses
* Verify and fetch user_lockup_tx_id if missing
* Fix tests
* Use bitcoin sha256
* Fix flutter CI
* List payments in reverse chonological order
* Add payment filtering and paging
* Fix examples
* Apply suggestions from code review
Co-authored-by: Erdem Yerebasmaz <erdem@yerebasmaz.com>
* Set timestamp for pseudo payments
* Filter by the first non-null timestamp from the join query
---------
Co-authored-by: Erdem Yerebasmaz <erdem@yerebasmaz.com>
