Add eclipse, partitioning, and fingerprinting note to i2p.md
What the developer wrote
Authored by da1sychain
Add eclipse, partitioning, and fingerprinting note to i2p.md
Also introduced a Privacy Recommendations section to docs.
What changed, and why it matters
This commit only changes documentation. It adds a new 'Privacy recommendations' section to the I2P guide and slightly rewords an existing note in the Tor guide. The text warns users that running a node on multiple networks at once can help protect the Bitcoin network against certain attacks, but may also allow an adversary to link those identities. There is no code change and no vulnerability being fixed.
No action required. This is a documentation-only clarification about existing privacy trade-offs.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies two Markdown files (doc/i2p.md and doc/tor.md). It adds a privacy note about bridge nodes, eclipse/partition attack resistance, and identity correlation risks when exposing a node over multiple networks. No source code, configuration defaults, network behavior, or cryptographic logic is altered.
Changed components
doc/i2p.mddoc/tor.mdInspect captured patch +14 / −3
diff --git a/doc/i2p.md b/doc/i2p.md
index b769a74d..624b651f 100644
--- a/doc/i2p.md
+++ b/doc/i2p.md
@@ -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.
diff --git a/doc/tor.md b/doc/tor.md
index 1b28c8a6..e9db555f 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -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.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.