Home›Crypto›Market Structure›Bitcoin Core weighs removing encrypted CJDNS routing s…

Bitcoin Core weighs removing encrypted CJDNS routing support

A CJDNS address seeder database showed 22 reachable nodes and only seven deemed technically “good,” raising concerns that the thin peer pool could make eclipse attacks easier.

Reported · Written up by our desk · Market Structure

Bitcoin Core contributors are debating whether to drop encrypted CJDNS routing support after internal testing suggested the network transport may no longer add meaningful resilience, and could instead become a liability. The discussion centers on whether sparse CJDNS peer availability undermines the protection it was meant to provide.

According to CryptoSlate, one seeder database snapshot found 25 CJDNS addresses, with reachability falling to 22 and only seven classified as “good” under stricter technical filters. An issue author reported seeing just three to four peers in testing, despite Bitcoin Core including 11 fixed CJDNS seeds, prompting calls for deprecation.

The debate also considers a proposed release sequence where Bitcoin Core could warn users in a 32.x version before planning removal in 33.x, though the plan remains unresolved. The issue is still open in the 32.0 milestone, with no implementation branch or pull request in the Development section as of Aug. 23, CryptoSlate reported.

Bitcoin Core currently implements CJDNS as an optional peer-to-peer transport and address handling outside Bitcoin consensus. Contributors noted that the cost of filling standard outbound connections and the additional cost of eclipsing a CJDNS-only node would need to be weighed, since an eclipse attack isolates a node by monopolizing peers.

Latest closeBitcoin $77,322.07 ▲0.3%

More like this

Sources