Merge bitcoin/bitcoin#35963: doc : update cjdns docs to discourage using onlynet option

beefda21be doc : update cjdns docs to discourage using onlynet option (naiyoma)

Pull request description:

  Currently, the number of CJDNS addresses is still very small and may not be sufficient to fill all outbound connection slots. When running with the `-cjdnsonly` and `-cjdnsreachable` options, `ThreadOpenConnections()` repeatedly calls `Select()`, which returns the same few addresses over and over. The connection attempts may fail, the addresses remain in `AddrMan`, and the loop continually restarts.

  The documentation does mention running CJDNS alongside other networks, but we should explicitly explain why using only CJDNS is discouraged, since running with these options alone is supported.

ACKs for top commit:
  achow101:
    ACK beefda21be
  jonatack:
    ACK beefda21be
  hodlinator:
    ACK beefda21be
  brunoerg:
    ACK beefda21be

Tree-SHA512: 46126291ceb1c36384f9b3deaccdcf20baf8cd4a68491d2ad9fc4a35ec71ad4194b38c4a22c9853bd3f329e2ecb9a0452813d1eea121eb3712876e73dfd4b3f0
This commit is contained in:
merge-script
2026-08-18 10:08:37 +01:00

View File

@@ -73,7 +73,11 @@ connections are not affected by this option. It can be specified multiple times
to allow multiple networks, e.g. onlynet=cjdns, onlynet=i2p, onlynet=onion.
CJDNS support was added to Bitcoin Core in version 23.0 and there may be fewer
CJDNS peers than Tor or IP ones. You can use `bitcoin-cli -addrinfo` to see the
CJDNS peers than Tor or IP ones. Therefore, using CJDNS alone without other
networks is discouraged: a node may be unable to fill its outbound connection slots
but will repeatedly try the few addresses it knows and is more susceptible to
[Sybil attacks](https://en.bitcoin.it/wiki/Weaknesses#Sybil_attack).
You can use `bitcoin-cli -addrinfo` to see the
number of CJDNS addresses known to your node.
In general, a node can be run with both an onion service and CJDNS (or any/all