Re: [Lightning-dev] Impact of eltoo loss of state

2021-07-27 Thread Jeremy
Just my 2 cents: I think worrying about the size of a resolution during a contested close scenario (too much) is not worth it. Encoding the state needed (e.g., in op_return or whatever) is the safest option because then you guarantee the availability of the closing transaction data in the

Re: [Lightning-dev] Impact of eltoo loss of state

2021-07-27 Thread ZmnSCPxj via Lightning-dev
Good morning aj, and list, > > I don't think you can reliably hide that you forgot some state? Thinking a little more --- *why* do we need to hide that we forgot some state? The reason is that if your peer learns you forgot state, the peer can pass off obsolete state onchain, thereby stealing

Re: [Lightning-dev] Impact of eltoo loss of state

2021-07-27 Thread ZmnSCPxj via Lightning-dev
Good morning cdecker, aj, and list, > . In addition we can store the same data with multiple peers, ensuring that > as long as one node is behaving we're good. Depending on size limits of the stored data, it may be possible to use some kind of erasure coding so that at least k of n peers need