1 month ago
18
While no code has been removed and no final decision has been made, the low adoption metrics have forced contributors to re-examine the practical security and engineering trade-offs of maintaining legacy overlay networks inside the main Bitcoin client.
Key Takeaways
- A recent seeder database check found only seven “good” CJDNS nodes, highlighting minimal active adoption on the network.
- Thin peer pools undermine security by making it dramatically easier for malicious actors to isolate and manipulate CJDNS-only nodes.
- Developers are weighing code complexity and bug risks against keeping an alternative routing network available during emergencies.
- The proposal concerns node networking and transport protocols only; it does not affect block validation, transaction rules, or core consensus.
Seven “good” nodes trigger a broader infrastructure audit
The technical discussion began in an open GitHub issue when developers questioned whether Bitcoin Core should continue su...
English (US)