bitcointxoko/guides
1
1
Fork 0
Code Issues Pull Requests 9 Actions Packages Projects Releases Wiki Activity

Update ln-07.md

Browse Source
This commit is contained in:
Bitcoin Txoko
2024-12-04 15:34:30 +01:00
committed by GitHub
parent 27dae8936e
commit dcc8358684
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
en/ln-07.md
+6
View File
@@ -288,3 +288,9 @@ The `your_last_per_commitment_secret` is the last per-commitment secret received
There are lots of checks that a node should do when receiving a `channel_reestablish` in order to make sure that all necessary updates are re-sent so that the channel can continue working as normal. There are also some checks that ensure that nodes are not tricked into revoking a state that should not yet be revoked or tricked into broadcasting a state that _has_ been revoked. If you are interested in the details around these checks, read [BOLT2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md). There are lots of checks that a node should do when receiving a `channel_reestablish` in order to make sure that all necessary updates are re-sent so that the channel can continue working as normal. There are also some checks that ensure that nodes are not tricked into revoking a state that should not yet be revoked or tricked into broadcasting a state that _has_ been revoked. If you are interested in the details around these checks, read [BOLT2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md).
Note that when a connection re-establish happens, both sides must remove any uncommitted updates from their staging area. If we revisit the git analogy, they should use git stash when a reconnection occurs. This means that both sides will need to retransmit any `update_*` messages that were not yet committed on the other side's commitment transaction. Note that when a connection re-establish happens, both sides must remove any uncommitted updates from their staging area. If we revisit the git analogy, they should use git stash when a reconnection occurs. This means that both sides will need to retransmit any `update_*` messages that were not yet committed on the other side's commitment transaction.
### References
- [BOLT2 Peer Protocol](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md)
- [Normal Operation of a pre-taproot LN channel](https://ellemouton.com/posts/normal-operation-pre-taproot/) by nostr:nprofile1qqswrt9pnxatlplu49h6meld8svmwqt87wwvk256rqk07n6eu4qeh5gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dszpfjtz
- [A Technical Walkthrough of Hash Time Locked Contracts and Lightning Channel Operations](https://lightning.engineering/posts/2023-06-28-channel-normal-op/)
- [BOLT8 Transport](https://github.com/lightning/bolts/blob/master/08-transport.md)