So with the lightning network is a network of channels, payment channels. A payment channel is a agreement among two people who have a shared UTXO on the blockchain, a two of two multi-signature coin, basically. And these two parties now pre-sign Bitcoin transactions, spending out of that shared coin to whatever destination they have. The trick is they pre-sign a transaction, but they don't yet publish it. So that means if the two parties agree, they can pre-sign the follow-up transaction without publishing that. And they can pre-sign the next transaction without publishing that, etc. So ultimately, they have an infinite amount of transactions that can be pre-signed moving economic value or monetary value without ever broadcasting those update transactions to the Bitcoin network or to the blockchain. Basically, increasing the scalability of the system well, infinitely ultimately. And that's cool and all. But because of numerous quirks in the Bitcoin protocol and the fact that Satoshi, well, actually Satoshi had the first idea of payment channels, I'm not sure it might be even in the white paper with the N sequence number. But his naive idea of a payment channel was very quickly found out to be not working because it could be cheated. And now with the Lightning Network, we have a method or a protocol of how two people can coordinate this payment channel in a way that they cannot be cheated from, which is excellent. It's just that this punishment mechanism is done in a way that the two parties have to remember every update to the payment channel. You can prune some parts, but basically every time you update the state of who owns how much money in this two of two multi-signature, that has to be remembered by both people. And if you forget, even one small part of this piece of data, then you are at risk of being stolen from and irrevocably. And that's a massive design flaw. And it leads to a lot of headaches. So basically, you need to keep an ever growing amount of data that you can't even hierarchically deterministically derive like you do with Bitcoin private keys. In Bitcoin private keys, we have one set of 12 words and that gives you infinite amount of private keys. You just need to remember those 12 words and you have to back up of all of the keys that you would use. Great. We don't have that in Lightning. You need to keep every time you make a transaction, you need to remember a new random arbitrary set of data. And you have to back it up. So after every time you make an update to your payment channel, you need to have a secure backup of making sure that this piece of data is there. And if you lose any of your old backups, you're at risk of losing all of your money. And that's not good. There are solutions to this. There are solutions to this since 2017 or something long before we even released a Lightning network. But the solutions require a change to the Bitcoin consensus protocol and L2 or Lightning symmetry, as it's now known. It has been hashed to that for five, eight years or something like this. And we know it's super important. We know that Lightning is basically broken without it and has no chance of scaling to reach enough capacity to satisfy the need of all the humans and computers and robots who will want to use Bitcoin as a money system.