transaction identity leakage during initial block download #2122

issue rebroad opened this issue on December 21, 2012
  1. rebroad commented at 1:04 PM on December 21, 2012: contributor

    During initial block download ResendWalletTransactions() runs, trying to send transactions which may have already been introduced into blocks. This therefore reveals two things about the node, one that it is not up to date with the blockchain, but also that those transactions originated from this node. This information could be used by people analysing the network to determine where the transactions came from.

    Can/should the code be changed to provide the option not to send wallet transactions until the block chain is more up to date?

  2. rebroad commented at 5:05 AM on May 12, 2013: contributor

    superceded by #2445

  3. rebroad closed this on May 12, 2013

  4. HashUnlimited referenced this in commit d38ad87468 on Jul 2, 2018
  5. HashUnlimited referenced this in commit 7e33650d61 on Jul 2, 2018
  6. HashUnlimited referenced this in commit c48cce0ca1 on Jul 2, 2018
  7. HashUnlimited referenced this in commit 2fc92336e7 on Jul 3, 2018
  8. sidhujag referenced this in commit 9a1ef491d0 on Jul 6, 2018
  9. owlhooter referenced this in commit b7c326115e on Oct 11, 2018
  10. MarcoFalke locked this on Sep 8, 2021
Contributors

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-22 18:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me