highperfocused/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2026-01-19 23:03:45 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge bitcoin/bitcoin#33750: doc: document fingerprinting risk when operating node on multiple networks

Browse Source 
e346ecae83 Add eclipse, partitioning, and fingerprinting note to i2p.md (da1sychain)
19a6a3e75e Add eclipse, partitioning, and fingerprinting note in tor.md (da1sychain)

Pull request description:

  Operating a Bitcoin node across multiple networks poses some fingerprinting risk. [0] Currently, this is not clear from the documentation and may be causing direct harm to users who are unaware of this.

  The included documentation change indicates this risk factor but also notes that operating a node across multiple networks does provide an important benefit (increases the cost of eclipse and partitioning attacks) and is thus not discouraged outright.

  The i2p documentation did not include a privacy recommendations section, so that is added as well.

  [0] https://delvingbitcoin.org/t/fingerprinting-nodes-via-addr-requests/1786

ACKs for top commit:
  danielabrozzoni:
    ACK e346ecae83
  rkrux:
    crACK e346ecae83
  mzumsande:
    ACK e346ecae83
  glozow:
    lgtm ACK e346ecae83

Tree-SHA512: d35a00f604ed70bb9d2339066612414f590d8cfe4d02eb0f586364b32016c7259aaaf059bc5162779f36b06fb06508ff7162022bdf65aa22a840bc34f69b7b50
This commit is contained in:
merge-script
2025-11-12 09:38:27 -05:00
parent 47618446a0 e346ecae83
commit d4e2a45833
2 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/i2p.md
View File

@@ -166,3 +166,13 @@ In most cases, the default router settings should work fine.
Please see the "General Guidance for Developers" section in https://geti2p.net/en/docs/api/samv3
if you are developing a downstream application that may be bundling I2P with Bitcoin.
## Privacy recommendations
- Operating a node that listens on multiple networks (e.g. IPv4 and I2P) can help
strengthen the Bitcoin network, as nodes in this configuration (i.e. bridge nodes) increase
the cost and complexity of launching eclipse and partition attacks. However, under certain
conditions, an adversary that can connect to your node on multiple networks may be
able to correlate those identities by observing shared runtime characteristics. It
is not recommended to expose your node over multiple networks if you require
unlinkability across those identities.

7
doc/tor.md
View File

@@ -238,3 +238,10 @@ for normal IPv4/IPv6 communication, use:
Otherwise it is trivial to link them, which may reduce privacy. Onion
services created automatically (as in section 2) always have only one port
open.
- Operating a node that listens on multiple networks (e.g. IPv4 and Tor) can help
strengthen the Bitcoin network, as nodes in this configuration (i.e. bridge nodes) increase
the cost and complexity of launching eclipse and partition attacks. However, under certain
conditions, an adversary that can connect to your node on multiple networks may be
able to correlate those identities by observing shared runtime characteristics. It
is not recommended to expose your node over multiple networks if you require
unlinkability across those identities.