The whole Bitcoin Core v29 vs Bitcoin Core v30 vs Bitcoin Knots debate is a massive False Trichotomy.
A False Trichotomy is a logical fallacy that presents three options as the only possible choices when, in fact, there may be other alternatives available.
This oversimplifies the situation and misleads the audience into thinking they must choose among the limited options presented.
You give people a worse option (Bitcoin Core v30) and a bad option (Bitcoin Core v29, Bitcoin Knots) to choose from and there is no right answer.
Blind trust in Bitcoin Core developers is very dangerous, in the same way blind trust in Bitcoin Knots developers is.
Humans can be fallible, corrupt or both.
Recent changes to the protocol have done more harm than good.
I lean toward the ossification camp - as Samson Mow said - a new client that is more battle-tested, more secure, leaning toward ossification and building more consensus for changes that are implemented.
If you tell me:
- "Bitcoin is not a finished product. We may be on a detour to address spam, and part of the crisis did originate with (mishandling of) the Segwit and Taproot upgrades - but to improve the world, we still need more functionality. Stopping all improvements forever ("ossifying") is fatal".
Then you're going to have to provide more context.
Is ossifying fatal because:
- of failed changes developers have made to the protocol,
- or is ossifying fatal because it doesn't allow for a use case you want to implement,
- or is ossifying not fatal at present?
Bitcoin development and "Bitcoin improvements" have turned into a complete shit show.
You have people with full time jobs, with a good chunk of their savings (time and energy) invested into Bitcoin getting bombarded with technicalities by developers.
Most of these developers don't understand psychology, finance, geopolitics, history, and human incentives, and have 0 capability to understand and game theory adversarial thinking.
If you can't explain how you're going to "improve" the protocol to non-technical plebs with full time jobs and can't prove how your "improvements" won't have bad downstream consequences, then you most likely shouldn't be "improving" the protocol.
If we are currently in a complete shit show protocol-wise and you start talking about other "improvements" you want to make to the protocol, it shows that you have very close to 0 ability to read the room.
The most dangerous to Bitcoin attack vector is developers making changes to the protocol that harm decentralization and impede Medium of Exchange use.
Screenshot of the quote above for context.

More context on how the most dangerous to Bitcoin attack vector is developers making changes to the protocol that harm decentralization and impede Medium of Exchange use:
