Skip to content
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

Ideation: Emergency refund of user lockups via presigned transations #813

Open
kilrau opened this issue Feb 7, 2025 · 0 comments
Open
Labels
question Further information is requested

Comments

@kilrau
Copy link
Member

kilrau commented Feb 7, 2025

Since we have some funds locked in swap addresses probably forever either due to loss of refund data OR just out of oversight (funds weren't claimed and users never bothered to take care of it) @michael1011 and I just came up with the idea of swap clients waiting for the lockup transaction to happen and then creating presigned transaction(s) refunding the swap back to the input address(es) with a timelock of e.g. 14 days, sign the transactions and send them to a new boltz endpoint.

Like this Boltz could "return funds to sender" after the timelock without ever taking custody. Major problem is that we can't be sure the input addresses are under users control (exchanges etc) and especially if lockup transactions have multiple (potentially hundreds of inputs). Then the swap client would need to create a presigned refund tx for each of them and rely on the user contacting Boltz to tell us which to broadcast. Creating these transactions will be resource intensive in a browser, especially with hundreds. This is not pretty and definitely just an idea for now but I'd absolutely love to avoid having funds stuck forever in Boltz lockup addresses.

@kilrau kilrau added the question Further information is requested label Feb 7, 2025
@kilrau kilrau changed the title Ideation: Emergency refund of users lockups via presigned transations Ideation: Emergency refund of user lockups via presigned transations Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant