Bitcoin Core developers are quietly debating a change that could strip encrypted routing support from the protocol entirely, leaving node operators exposed to one of Bitcoin's most dangerous attack vectors.
The proposal, currently under review by Core maintainers, outlines a two-stage removal sequence: a deprecation warning in version 32.x, followed by full elimination of encrypted routing support in version 33.x. The trigger is a problem most node runners don't even know they have.
The Real Problem: Your Node Is Probably Sick
Node health across the Bitcoin network is poor. That's not spin, that's the diagnosis driving this entire conversation. Sparse, unreliable fallback routes have created a landscape where encrypted routing protocols offer a false sense of security rather than genuine protection. Maintainers are now testing whether stripping the feature and leaning on fallback route resilience actually produces a stronger network, not a weaker one.
The risk they're trying to solve is eclipse attacks, where a bad actor surrounds a target node with malicious peers, cutting it off from the honest network entirely. Once isolated, that node can be fed fraudulent transaction data, manipulated into confirming fake payments, or used to surveil user activity. Encrypted routing was supposed to help prevent this. The argument now is that broken encrypted routing may be making it worse.
This Is Still a Proposal, But the Direction Is Clear
Nothing is finalized. The 32.x warning and 33.x removal remain under discussion as developers monitor whether sparse fallback infrastructure can actually carry the load. But the fact that Core maintainers are seriously debating removal signals real concern about the current state of node connectivity across the network.
This isn't a fringe conversation. Bitcoin Core doesn't float proposals like this without significant internal pressure. When the people maintaining the most critical software in crypto say the network's node health is bad enough to reconsider foundational privacy infrastructure, that warrants attention.
What Node Operators Should Do Right Now
If you're running a Bitcoin node, three things matter immediately.
First, audit your peer connections. Abnormally low peer counts or connections clustered around a small number of IP ranges are early eclipse warning signs. Second, stay close to the Core GitHub repository as the 32.x release approaches. The deprecation warning, if it ships, will give you time to adapt before forced removal in 33.x. Third, watch how the maintainer debate evolves on fallback route testing. If sparse routes prove resilient, removal accelerates. If they don't, the proposal could be shelved entirely.
The bottom line: Bitcoin's base layer security is under active debate right now. Node operators who ignore this are the exact users this change is designed to protect, whether they want the protection or not.