Feature Request: Specify LockupTx confirmation target in reversesubmarine swap

[joemphilips]

When performing reverse submarine swap, it seems that intended behavior of the client is to claim from the lockuptx after 0 or 1 conf.

But I want to wait more for the sake of the security (especially when the on-chain asset is the one likely to reorg often), is it possible to specify a longer value?

In a loopout of the lightning loop, there is a parameter called htlc_confirmations
I could not find anything equivalent in a reverse submarine swap in the boltz.

Of course, I can still just wait for the confirmation without telling the boltz-backend server anything, but the invoice might expire in that case. So I want the server to change the expiration time of the invoice

(If I understand correctly, this is a reason that lightning loop imposes their acceptable range of the CLTV-delta for its invoice in case of a loop out, which can be seen in loop-cli terms command)

[michael1011]

Our BTC/BTC reverse swaps have a 24 hour expiry as of right now but we don't expose that information via an API endpoint (yet; might be a good idea to do that). So waiting for a higher number of confirmations is surely possible.

Would an endpoint that shows you the expiration times of our swaps solve your issue?

[joemphilips]

Would an endpoint that shows you the expiration times of our swaps solve your issue?

I think so. It is certainly better because I can just quit the swap before starting if the expiration is not acceptable.

It is nice if the value is set for each currency pairs, since how long we want to wait depends on how it is likely the on-chain asset is to reorg.