You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Boltz adds a script path that allows coins to be claimed to the wallet address of the user (and only to this address) by just providing the preimage. No signature required. This way we can have a 3rd party with access to swap preimages broadcast claim transactions without the possibility to steal because it can only go to the user's address. The user will see received funds next time coming online.
A mobile wallet might even use a primitive like Android's doze windows to claim instead of relying on a third party if there is a chance the 3rd party could collude with Boltz and leak preimages.
The text was updated successfully, but these errors were encountered:
kilrau
changed the title
Covenants: Trustless LNURL/Lightning Addresses
Covenants: Trustless LNURL/Lightning Addresses for Liquid Reverse Swaps
Jan 26, 2024
kilrau
changed the title
Covenants: Trustless LNURL/Lightning Addresses for Liquid Reverse Swaps
Covenants: Trustless & Offline LNURL payments
Jan 26, 2024
Background
Inspired by the Breez idea of signing payments within mobile notification device compute time and Aqua's desire to enable "Receive to [email protected]" Lightning Addresses, we are exploring the idea to implement Liquid Reverse Swaps to LNURL/LN addresses trustlessly - using covenants.
Goal
How it works
Boltz adds a script path that allows coins to be claimed to the wallet address of the user (and only to this address) by just providing the preimage. No signature required. This way we can have a 3rd party with access to swap preimages broadcast claim transactions without the possibility to steal because it can only go to the user's address. The user will see received funds next time coming online.
Useful OPCODEs:
OP_INSPECTINPUTVALUE
OP_INSPECTOUTPUTVALUE
OP_INSPECTOUTPUTSCRIPTPUBKEY
TBD
More
A mobile wallet might even use a primitive like Android's doze windows to claim instead of relying on a third party if there is a chance the 3rd party could collude with Boltz and leak preimages.
The text was updated successfully, but these errors were encountered: