Preferences such as your theme stay on your device. Google Analytics runs under Consent Mode and only measures fully when you choose Accept all. We run no advertising trackers. See the Privacy Policy.
Reviewed by our automated publish checklist (fact-grounding, duplicate detection, and SEO completeness checks) before going live — not a human editor. See editorial policy.
CoinBatmi feature visual — market neutral — Bitcoin Core considers dropping encrypted routing support as poor node health exposes users to eclip
Bitcoin Core maintainers are considering the removal of encrypted routing support after determining that poor node health across the network exposes users to eclipse attacks. The 32.x release series will carry a deprecation warning, with potential removal in the 33.x series, according to a CryptoSlate report.
The feature, designed to obscure transaction origins by routing through encrypted channels, has seen adoption stall as many nodes fail to maintain the uptime and connectivity required for reliable operation. When nodes drop offline or behave unpredictably, the encrypted paths they advertise become vectors for attackers to isolate victims from honest peers, an eclipse attack.
Maintainers are now testing whether sparse fallback routes, which use a smaller set of trusted connections when encrypted routes fail, provide sufficient resilience. The proposal remains in the evaluation phase; no final decision on the 33.x removal has been made.
BTC traded at $77,275 at the time of writing, up 0.10% in 24 hours and 22.60% over the past seven days, per CoinGecko. The 7-day close series shows a steady climb from $63,336 to $76,579. Volume reached $28.4 billion, while market capitalization hit $1.55 trillion.
BTC 7-day price
Total crypto market cap stood at $2.61 trillion with 24-hour volume of $85.5 billion, a 3.36% daily decline. Bitcoin dominance held at 59.2%; Ethereum dominance sat at 11.2%.
The fallback route test
The encrypted routing debate highlights a tension between privacy ambitions and operational reality. If the feature is dropped, developers may redirect effort toward improving baseline peer selection and connection management, areas where measurable gains against eclipse attacks already exist.
Maintainers are benchmarking sparse fallback routes against the current implementation. Early data suggests the simplified approach reduces the attack surface while preserving connectivity for the majority of honest nodes. A decision on whether to proceed with the 33.x removal is expected after the test window closes.
Watchpoints: the 32.x release candidate timeline, maintainer mailing list consensus on fallback route benchmarks, and any alternative privacy-preserving routing proposals that emerge from the review.
Frequently Asked Questions
+Why would Bitcoin Core remove a privacy feature like encrypted routing?
Maintainers found that poor node health makes encrypted routes unreliable, turning them into attack vectors for eclipse attacks rather than privacy protections.
+What is an eclipse attack in this context?
An eclipse attack isolates a node from honest peers by controlling all its connections, allowing the attacker to feed it a false view of the blockchain.
+When would the removal happen if approved?
The 32.x series would carry a deprecation warning; actual removal would target the 33.x series, but no release dates have been set.
Reader desk
Discuss the signal
Verified readers · 2 comments per post / 24h
Checking your session…
No comments yet. Be the first verified reader to add context.
Reader desk
Discuss the signal
Verified readers · 2 comments per post / 24h
No comments yet. Be the first verified reader to add context.