ghost43
ghost43
Thank you for writing this up! In general I like this proposal very much, and we would definitely want to implement this (or whatever it evolves into) into Electrum. -----...
> We would need a new message to ask our peers to store an updated version of our `node_backup_data`. We would send that message for example whenever we've opened a...
> Don't add TLVs everywhere, simply use a separate message? The idea is that having TLVs as part of `commitment_signed`, `revoke_and_ack`, etc, allows atomically updating the channel backups with the...
For electrum, it's [email protected] with GPG key: [`6694 D8DE 7BE8 EE56 31BE D950 2BD5 824B 7F94 70E6`](https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/ThomasV.asc) See https://github.com/spesmilo/electrum/blob/master/SECURITY.md
> I think this is were it's incorrect. Alice should not send a `commitment_signed` with both those changes because she can see that Bob wouldn't be able to pay for...
> No, she can just send her commit_sig for the new HTLC without taking into account the proposed update_fee. She already sent `revoke_and_ack` in the example (scenario 1), so it's...
> to avoid running into this too frequently is to avoid sending `update_fee` for a fee increase when your balance is very low Yes, of course you are right, from...
> In a simple test, I was able to get consistent builds by exporting `CFLAGS=-g0` before building the wheel. This prevents adding any of the debug information to the generated...
Yes, we removed the kivy GUI. So this issue is no longer relevant. Thanks for pointing it out. If you think there is a similar bug in the qml GUI,...