Woofun AI reports that Bitcoin Core contributors are actively debating the future of CJDNS support within the protocol, centering on Issue 36041 which questions whether this optional transport layer should be retained or deprecated. The core tension lies in balancing the utility of CJDNS as a fallback communication channel against the security liabilities introduced by its critically low node density, potentially exposing operators to targeted network isolation. This discussion moves beyond general complaints about low usage, focusing instead on concrete metrics that suggest the current infrastructure may no longer provide the resilience it was designed to offer.

The data underpinning this debate reveals a starkly shallow peer pool, with only seven of the 22 reached addresses successfully clearing the good-node filters. Zumsande, a key participant in the discussion, noted that his node identified just three or four peers, highlighting the fragility of the current network state. He proposed a benchmark of low triple digits as the rough threshold that might justify continued support for the transport, providing maintainers with a specific numerical target for argument rather than vague concerns. This metric serves as a critical reference point, transforming abstract worries about adoption into a measurable standard for viability, though the global CJDNS population may theoretically be larger than the single crawler's database suggests.

Security analysis indicates that the risk of eclipse attacks is not solely determined by the ten regular outbound slots available to nodes. The practical exposure to such attacks depends on a complex interplay of address availability, address selection algorithms, crawler reliability gates, and the occasional establishment of extra outbound connections. While the measured pool supports a concentration concern for CJDNS-only nodes, the full cost of executing a successful eclipse attack remains unquantified in public discussions. This lack of precise cost modeling leaves a gap in understanding the true severity of the threat, even as the structural vulnerabilities of a thin peer pool are clearly identified.

Woofun AI data shows that structurally, CJDNS is positioned as a complementary transport option alongside IPv4, IPv6, Tor, and I2P, offering route diversity rather than serving as a primary network. Bitcoin Core's documentation frames it as a backup path, allowing nodes to maintain connectivity if one network encounters issues.

However, the stakes differ significantly between CJDNS-only operators and mixed-network operators; the former face the direct risk of the thin pool, while the latter can retain other automatic paths even when CJDNS peers are scarce. This distinction is crucial, as the value of CJDNS is highest when it serves as a redundant layer in a multi-transport strategy, rather than as a standalone solution.

The technical configuration directly affects specific user groups, particularly those utilizing the -onlynet=cjdns flag, which tells Bitcoin Core to treat the relevant IPv6 range as CJDNS, or -bind=cjdns, which instructs Bitcoin Core to treat the relevant IPv6 range as CJDNS, which limits automatic outbound connections to that transport. According to the documentation, these options can currently be combined with other networks, while inbound and manually added connections remain available under the -bind=cjdns setting. This flexibility allows for nuanced network setups, but it also means that the impact of deprecating CJDNS would be unevenly distributed, primarily affecting those who rely on it as their sole or primary transport mechanism.

Issue 36041 remains open, with the warning and removal sequence recorded only as a proposal, reflecting the ongoing uncertainty surrounding the transport's future. The proposal highlights a small observed peer set, multiple expressions of support for deprecation, and one proposed release sequence, illustrating the community's divided stance. Seven good nodes makes the transport-diversity tradeoff measurable and leaves the removal choice open, marking a pivotal moment where empirical data challenges the assumed value of code-level redundancy. This debate underscores the broader challenge of maintaining legacy features in a dynamic network environment, where security and usability must be continuously re-evaluated.