From jlrubin at mit.edu Mon Jul 12 22:20:41 2021 From: jlrubin at mit.edu (Jeremy) Date: Mon, 12 Jul 2021 15:20:41 -0700 Subject: [Lightning-dev] Impact of eltoo loss of state In-Reply-To: References: <20210712081749.GB6250@erisian.com.au> Message-ID: Another option would be to somehow encrypt this data in, say, an OP_RETURN for any update transaction for each participant (perhaps worth breaking update symmetry for efficiency on this...) that way if an update ever happens on a state you don't have you can use your static key to decrypt the relevant data for what PK_si signed off on. -- @JeremyRubin On Mon, Jul 12, 2021 at 3:16 PM Jeremy wrote: > Without an exact implementation, one thing you could do to fix the lost > state issue would be to make the scripts something like: > > [` CLTV DROP PKu CHECKSIGVERIFY GETLOCKTIME > BIP32DERIVE CHECKTRANSACTIONSIGNEDFROMSTACK`, `2016 CSV DROP PK_si > CHECKSIG`] > > In order to upgrade to state M>= N+1 you'd have to publish a transaction > signed with the BIP32 derived key for that update in the future. > > The downside is that you end up double publishing the txdata on the chain, > but it at least ensure data availability. > -------------- next part -------------- An HTML attachment was scrubbed... URL: