Hi everyone, Recently there was a commit to change pings from including random data to now including state data: the most recent bitcoin block header.
https://github.com/lightningnetwork/lnd/pull/5621 I was wondering if there was a discussion around the possible risks for continuously broadcasting your most recent state to the network. Are there no counterparty risks associated with this or is the attack surface just too small/unrealistic outside edge cases? If I were to just spitball a couple of ideas (and would welcome other examples), with this data I would wonder if: a) you could use block header update delays to de-anonymize/identify/locate nodes by using update times/uncle blocks/fingerprinting attacks b) any counterparty risks exist from an attacker node pretending to be on the same block as an out of date node If the security story around this update has been discussed in detail I'd love to know where to read more. Thanks, Skyler S.
_______________________________________________ Lightning-dev mailing list Lightning-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
