-
Notifications
You must be signed in to change notification settings - Fork 33
⚗️Investigate compatibility of RFC003 and LND with HODL invoices #841
Comments
Ok so the thing Thomas and I found our was that in order to compile lnd and ln-cli with this feature you need to add:
To the Dockerfile. Eventsin an X-LN Swap (beta_ledger is LN) the things we need to watch for are Alice adds a HODL invoiceWe agreed that it's best that the COMIT node does this itself. Bob sends the payment (conditioned the secret_hash)This is done using sendpayment. It's actually tricky to tell if this has been done. Bob's node has to list his channels, waiting for for something like this:
When he sees Alice settles the payment (and reveals the secret)We haven't tested this but it can be done by using RFC003 spec unanswered so farWhat's the Ledger?We didn't figure out the answers to what should be the ledger etc and what's possible. IMO the ideal situation is:
But to do that we have to ensure that we can guarantee a payment is sent to a certain channel. If that's not possible, maybe we could make the How to negotiate timesLN uses absolute block height for the expiries. We have to decide whether we negotiate in terms of a specific time in the future in the SWAP messages and then try and convert it into block height or have block heights in the expiry messages. |
Note: the new feature A rewrite of this spike can be found in: comit-network/spikes#6 |
This Spike is about figuring out how we could do an RFC003 SWAP with
lnd
as one of theLedger
s. Note that this would be independent of lightning channels as a Ledger (unless you find that lnd exposes an api that would allow this).HODL invoices were introduced into
lnd
here: lightningnetwork/lnd#2022 which will make things easier.What to include:
The text was updated successfully, but these errors were encountered: