cryptogera/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2026-01-31 02:31:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add eclipse, partitioning, and fingerprinting note to i2p.md

Browse Source 
Also introduced a Privacy Recommendations section to docs.
This commit is contained in:
da1sychain 2025-10-30 14:45:21 -07:00
parent 19a6a3e75e
commit e346ecae83
2 changed files with 14 additions and 3 deletions
Show Stats 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,9 +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 increase
the cost and complexity of eclipse and partition attacks. However, under certain
- 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.
unlinkability across those identities.