diff --git a/en/ln-02.md b/en/ln-02.md index 26c46b8..c63d3a4 100644 --- a/en/ln-02.md +++ b/en/ln-02.md @@ -1,6 +1,6 @@ ---- - Title: LN Chapter 2: Updating state - Summary: Today's chapter will describe the basics of how the update layer works under LN-Penalty, covering commitment transactions in more detail and serving as a set up for more detailed picture for how HTLCs fit into the picture in future chapters. + --- In the previous chapter, we learned how Alice and Bob opened a channel, using commitment transactions that can be published on the blockchain at any time to reclaim their funds. But of course, the initial commitment transactions become invalid as soon as the channel state changes, in other words, when a payment is made and the channel balance becomes distributed differently between the channel participants. In this chapter, we will start learning about how Alice and Bob can agree on a new division of funds, i.e. how to split the channel balance differently and invalidate the older commitment transactions that they have. @@ -23,7 +23,7 @@ In the last chapter, we showed how Alice and Bob exchanged their pubkeys to crea In a similar manner, Bob can construct Alice's commitment transaction too and provide her his signature for it. Alice can sign this valid transaction herself at any time and broadcast it to the network, giving her the assurance she needs to reclaim her funds in case Bob disappears. -![state1]() +![state1](https://cdn.satellite.earth/65f65f962198275cc0a472100fe513f657150ec8cfe59134f8f8a2dfbd0c8549.png) At this point, either party can broadcast their commitment transactions to close the channel. Let's say Alice broadcasts hers. Bob will get his 5 BTC immediately. Alice will have to wait the `to_self_delay` number of blocks before being able to use her 5 BTC. She doesn't need to worry about Bob spending her output though because she knows she never shared her private key with him. @@ -35,7 +35,7 @@ The problem though, is that Alice still has her commitment transaction from the Bob also sends Alice his old key (`dB1`) to invalidate his old state. He has no reason not to do this since his new state is more profitable to him. -![state2]() +![state2](https://cdn.satellite.earth/c08cf95f78ddaa6307b5b83da327aaa18c31384df959e667919b59893e334695.png) That's it! We have now learned how Alice and Bob can securely transact by setting up new states and invalidating old states. @@ -47,4 +47,4 @@ That's it! We have now learned how Alice and Bob can securely transact by settin ### References - [BOLT3](https://github.com/lightning/bolts/blob/master/03-transactions.md) -- [LN Things Part 2: Updating state](https://ellemouton.com/posts/updating-state/) por nostr:nprofile1qqswrt9pnxatlplu49h6meld8svmwqt87wwvk256rqk07n6eu4qeh5gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dszpfjtz +- [LN Things Part 2: Updating state](https://ellemouton.com/posts/updating-state/) by nostr:nprofile1qqswrt9pnxatlplu49h6meld8svmwqt87wwvk256rqk07n6eu4qeh5gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dszpfjtz