Cool, so we are in agreement that Knots is nonsense.
Discussion
Any code changes are nonsense. Core has proven out the vulnerability. The Devs are the weak link. It’s killing Bitcoin.
So there should also never be bug fixes or work on quantum-resistance done, got it.
Correct. Quantum, let’s talk about it in 20 years if ever. It’s just buzzword. #Bitcoin is immutable, scarce money. If it loses immutability it’s done. And with Core v30 it may have just lost it.
Well that simply isn’t how open source software works.
It’s not an app it’s a rule set. No updates required. Man, you’re falling for all the attack vectors. “Quantum” is used for FUD to do just what you’re doing, legitimizing code changes (and to create the next buzzword to move the AI money around)…the people who want to destroy #bitcoin are pursuing all of these btw, and they’re winning:
1. Lobbying and regulation: One way to prevent Bitcoin adoption would be to use lobbying and regulatory influence to restrict its use and make it more difficult for people to acquire and trade Bitcoin. This could involve working with governments and regulatory bodies to create laws and regulations that limit Bitcoin adoption or make it more difficult to use.
2. Discrediting Bitcoin: Another potential strategy would be to try to discredit Bitcoin as a legitimate investment or financial tool. This could involve spreading misinformation or negative propaganda about Bitcoin in the media, or working with financial institutions and experts to discredit the technology and its potential benefits.
3. Sabotage and attacks: A more aggressive strategy would be to launch direct attacks on the Bitcoin network or its users. This could involve hacking attacks or distributed denial of service (DDoS) attacks that disrupt Bitcoin transactions and make it difficult or impossible for users to use the network.
4. Creating a competing technology: One way to undermine Bitcoin adoption would be to create a competing technology that offers similar benefits but with fewer risks or drawbacks. This could involve investing in other cryptocurrencies or blockchain-based technologies that offer similar functionality to Bitcoin but with different features or benefits.
5. Targeting Bitcoin users: Finally, another potential strategy would be to target Bitcoin users directly with fraud or other criminal activities. This could involve phishing attacks or other scams that target Bitcoin users and attempt to steal their funds or sensitive information. By creating a climate of fear and uncertainty around Bitcoin, it may be possible to discourage people from using the technology and limit its adoption
Thanks for the copy pasta. 🍝
Nothing in this list of fear-mongering bullet points is solved by choosing one version implementation over another or preventing any further updates.
Bug fixes, yes.
But rewriting Bitcoin for an unverified, disprovable threat is fraud disguised as foresight by a community who have a sunken cost interest to do so. We dont need to upgrade Bitcoin to QR when it falsifies the model the “threat” depends on.
We’ve lived through the era where Bitcoin shattered every unsound economic theory, now we’re entering the era where it does the same to physics. The ultimate goal has always been convergence: to unify money and physics, value and reality. Bitcoin is that unification. CQC is the final performance of fiat, always has been. Final boss FUD. Bitcoin is the threat to fiat, not the other way around.
I don’t take QC seriously at all yet, I just threw that in as a hypothetical. I think bitcoin should be extremely difficult to change and forks that could lead to chain splits should be avoided. I also think it’s dangerous to demonize developers, which I’ve seen quite a lot of lately.
Which bugs? None of the BIPs are worth the risk.
Crickets. That’s what I thought. The bug fix argument is a red Hering. We need to stop development. Bitcoin is fine as is. We need to close the attack vector. Developers are the single most fatal risk to Bitcoin. Everything else, Bitcoin will prevail.
Damn, I didn’t know I needed to respond on your time while I’m working. Good to know.
For one, Unix timestamps is still not resolved.
