- Add get_swap_expired_timelock endpoint to return expired timelock if one exists. Fails if bitcoin lock tx has not yet published or if swap is already finished.
- Rename current_epoch to expired_timelock to enforce consistent method names
- Add blocks left until current expired timelock expires (next timelock expires) to ExpiredTimelock struct
- Change .expect() to .unwrap() in rpc server method register because those will only fail if we register the same method twice which will never happen
After careful consideration, I've concluded that it's not practical/possible to ensure that the previous behaviour (one log file per swap) is preserved due to limitations of the tracing-subscriber crate and a big in the built in JSON formatter
1423: Release version 0.12.2 r=delta1 a=comit-botty-mc-botface
Hi `@delta1!`
This PR was created in response to a manual trigger of the release workflow here: 5794466350.
I've updated the changelog and bumped the versions in the manifest files in this commit: 94febeca03.
Merging this PR will create a GitHub release and upload any assets that are created as part of the release build.
Co-authored-by: COMIT Botty McBotface <botty@coblox.tech>
1422: ci: add rustfmt to draft-new-release r=delta1 a=delta1
fixing the draft new release action, churn in dprint means that now rustfmt is run separately so it needs to be installed at this step
previous failure: 1568323870
Co-authored-by: Byron Hambly <bhambly@blockstream.com>
1421: ci: fix dprint version for draft action r=delta1 a=delta1
This should fix the dprint issue in the draft release action - [link to failing action](1562456196)
Co-authored-by: Byron Hambly <bhambly@blockstream.com>
1417: feat(asb): allow asb to register with mulitple rendezvous nodes r=binarybaron a=delta1
implements #633
This PR updates the ASB to be able to register with multiple rendezvous nodes. A unit test is added that checks this behaviour. I also tested it manually overnight and it repeatedly reregistered with the specified nodes.
The config file option is left as `rendezvous_point` for backwards compatibility, but now uses the same deserialization as introduced in #1231 so that multiple addresses can be specified in a comma separated string, or as a toml array of strings.
Co-authored-by: Byron Hambly <bhambly@blockstream.com>
