Skip to content
This repository has been archived by the owner on Mar 9, 2023. It is now read-only.

Why is message D required? #14

Open
jprupp opened this issue May 13, 2016 · 1 comment
Open

Why is message D required? #14

jprupp opened this issue May 13, 2016 · 1 comment

Comments

@jprupp
Copy link
Contributor

jprupp commented May 13, 2016

Message D means that the anchor transaction was confirmed in the bitcoin blockchain. Watching the blockchain directly is enough to know when this happens. It is not necessary to exchange further messages.

@matsjj
Copy link
Contributor

matsjj commented May 16, 2016

I would stick to it for now, as it eliminates some risks of incoherence between the parties. While both parties know how many confirmations the other party wants the anchor to have to consider it safe, we don't know which view the other party has of the blockchain. Maybe it is on some part of fragmented network and only sees the block 1 minute later?

Either way, LNEstablishDMessage is just a signal to say that one is ready to accept / relay payments now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants