Bitcoin Core just changed its security policy because AI can find bugs with a simple prompt. Jameson Lopp explains the bigger trend behind it: two and a half months of exponential growth in vulnerability discovery, attackers adopting uncensored AI models first, and security researchers who “have not been able to get a lot of rest.” He breaks down the PHP remote code execution flaw, why the fallout was smaller than expected, and why security now has to be real time and built into the development pipeline instead of a once-a-year audit.
Chapters:
0:00 Bitcoin Core Changes Its Security Policy: AI Finds Bugs With a Simple Prompt
1:04 Google’s 500,000-Qubit Estimate: Physical vs. Logical Qubits
2:00 The Quantum Timeline: “If We Have Less Than a Decade, We’re Behind”
2:57 Why We Don’t Have a Quantum Computer With More Than a Few Hundred Usable Qubits
4:26 30% of Addresses Have Exposed Keys: Who Attackers Would Target First
6:27 Why a Quantum Upgrade Will Take Years: Taproot, Consensus and Untested Cryptography
7:54 The PHP Remote Code Execution Flaw Explained
9:41 The Real Trend: Exponential AI Vulnerability Discovery and Exhausted Defenders
10:54 Security Must Be Real Time: From Annual Audits to the Development Pipeline
13:19 Hardware That Can’t Be Patched, and Why Wrench Attacks Have Topped 700
DISCLAIMER: The views and opinions expressed in this show are those of the participants and do not necessarily reflect the official policy or position of BTC Inc., Bitcoin Magazine, or any affiliated entities. This content is provided for informational and educational purposes only and should not be construed as investment, legal, tax, or accounting advice. Nothing contained in this show constitutes a solicitation, recommendation, endorsement, or offer to buy or sell any securities or financial instruments. Viewers should consult their own advisors before making financial or business decisions.
