Key Takeaways

Bitcoin Core v30 (Oct 9, 2025) is an evolutionary hardening release: it removes legacy checkpoints in favor of a header pre-sync that reduces implicit trust, upgrades P2P robustness (stronger orphan/package relay so one honest peer keeps you synced and thwarts eclipse-style isolation), and deprecates the old BDB wallet for SQLite as part of years-long modularization. The contentious OP_RETURN/ordinals debate resurfaces, but the dev stance is to preserve neutrality, don’t damage Bitcoin’s “money-ness” with policy filters against valid transactions. Expect continued investment in fuzzing/security testing, careful tooling-first approaches to any scripting/covenant upgrades, and a pragmatic reminder: if your node secures money, stay updated, the real near-term risk is legal/regulatory pressure on privacy tech and open-source devs, not the code itself.

Best Quotes

“The checkpoint removal is philosophical, it says the Core devs are not in charge of what your chain is.”

“We hurt the money-ness of Bitcoin trying to save it.”

“An eclipse attack is trying to trick you into not keeping on to a good person.”

“If you don’t run your node with money, it doesn’t matter what you do. But if you do, stay up to date.”

“I’m firmly on team ‘nothing ever happens.’ Bitcoin won’t die tomorrow.”

“Running a node is for you, your sovereignty, your privacy, not for the network.”

“The biggest risk isn’t technical, it’s legal. Developers still don’t have real protections.”

“America could still be the base for freedom through code. If we lead, the world follows.”

“Freedom of speech has strengthened, except when it involves money, and that’s the loophole they exploit.”

“It’s okay if people run their own node software. That’s the point of self-sovereignty.”

Conclusion

V30 won’t “change Bitcoin,” it quietly secures it, reaffirming decentralization by removing trustful crutches, hardening the network’s relay paths, and modernizing internals. The path forward is sober: build assurance (testing/tooling) before new script capabilities, keep nodes current, and defend the ecosystem where it’s most vulnerable, in law and policy, so developers and users can exercise financial speech without fear. In a year, this release is likely remembered less for drama and more as the maintenance milestone that kept a multi-trillion-dollar protocol boring, resilient, and ready for the next decade.

Timestamps

0:00 - Intro
0:45 - Bitcoin Core v30 and the Release Process
8:34 - Checkpoint Removal and Code Modularization
13:59 - Bitkey & Obscura
15:44 - P2P Robustness and Performance Upgrades
26:23 - Security Fuzzing and Eclipse Attack Protection
36:35 - SLNT & Unchained
38:01 - The OP_RETURN Debate and Why Updates Matter
54:18 - Future Covenants and Scripting Proposals
1:06:48 - Privacy Threats and Payment Infrastructure
1:20:59 - Fighting for Developer Freedom

Transcript

(00:00) A lot of people are putting hundreds of millions, billions of dollars even into this asset or completely unaware of the sort of optimizations that you guys are working on. Greg, we meet here on the eve of Bitcoin’s death. They could have gone to chain with an old version long ago and you just never heard about it. You’re sitting there waiting. You’re saying that’s weird.
(00:16) I’m not getting blocks, but things must be okay. And then on the other side, they actually have taken your money and run. An eclipse attack is a way of using arbitrary network means trying to trick you into not keeping on to a good person. I think most things are happening within the colored lines. It just improves velocity.
(00:34) Aside from making sure that this multi-t trillion dollar asset doesn’t fall over in the next few years, what would you contend as the biggest risk to Bitcoin right now? I mean, I think it’s got to be spicy, Greg. We meet here on the on the eve of Bitcoin’s death, October 9th, 2025. Bitcoin Core version 30. Yep. Drops tomorrow. very somber. Very somber.
(01:05) Uh, in all seriousness though, I think, uh, a lot of discussion, as we were just talking, um, before we hit record has revolved around obviously this OP op return um, debate whether or not the limit should be lifted or not and the potential consequences of doing that. Uh maybe we’ll touch on that, but I think um there hasn’t been enough discussion on everything else that’s included in Bitcoin Core version 30.
(01:33) So wanted to sit down with you and talk about what Bitcoin Core has been working on with this particular version. And I think before we do that for the layman out there, maybe we just do like a highle um a highle refresher of what Bitcoin Core is, what in what is entailed in um basically releasing um new versions, particularly significant versions like version 30. And then we can jump into the nitty-gritty of of what’s included.
(02:08) Sure. You want me to take the lead on this? Yes, sir. All right. So, basically, there’s a Bitcoin core software is the reference client, so to speak, where has majority kind of mind share and running share of the Bitcoin protocol itself. Um, it includes a bunch of different parts. Um, peer-to-peer layer stuff, consensus stuff, um, a wallet, which people still use, uh, a bunch of other like bunch of other tools and pieces in there.
(02:41) Um, a major release is done every six months. So, on a six-month cadence, there’s a what’s called a feature freeze, which is, hey, stop adding new things. Um, we’re going to continue just doing bug fixes until this time. there’s a branch off which means okay now we have a new fork in the history that will turn into releases that will release binaries based off of this and then eventually a release right with series of release candidates which is happening right now and then eventually a final release. Um in addition to this you also have kind
(03:13) of using this forked history that if there’s future bugs found if and if and when there are future bugs found and issues um the fixes could be applied directly on these forked off histories and do minor releases. So someday I will very highly likely have a 30.1 for various reasons. Um and this is how that done.
(03:36) That’s that’s done on a per need basis. So right now, if I understand correctly, there’s uh 20 and 29 minor releases being cut right now for various reasons, bug fixes and improvements. Um so this can happen throughout this life cycle. Um and then eventually at some point these major releases or these major branches get marked as end of life. So saying basically we won’t support this anymore.
(04:02) we won’t do any effort to like update maintenance to this make buil and make binaries or anything like that and then it kind of gets stale and so that’s kind of the the life cycle. Yeah. Yeah. And take an even further step back just on the concept of implementations, right? You have Bitcoin sort of consensus and then implementations like core not le bitcoin uh ptcd.
(04:30) They sort of have their own implementations that build software that is within consensus but does things a little differently. Correct. Yeah. So some are complete implementations. So BTCD is a good example that’s been around a long time. Um it has it’s it’s programmed in go the Golang and it has a complete implementation of the consensus software.
(04:53) So when you get a string of bytes in the form of a blockchain, it needs to come out to the same exact answer as Bitcoin D or any other implementation that raises the reimplementation raises the chance that there is mismatches, but those can hopefully be ironed out and debugged and fixed over time.
(05:16) Um, but there’s there’s definitely like always it’s a very demanding problem making sure they’re in lock step of consensus and even between Bitcoin versions there’s been historical problems with that uh where implementation details like how the database is stored causes forks in the future right with unforeseen events.
(05:39) Um it’s been a long time since it’s happened, but um it’s always possible with updates or or not updating too. Yeah. And where would you say we are um in terms of the path of Bitcoin Core? Cuz like going back I remember my first Bit Devs in New York in 2015. Um Russ Yianowski basically presented on SegWit and obviously we had SegWit getting implemented but I think um one thing over the year over the last 12 years has been made clear to me is that Satoshi when he launched Bitcoin it was a bit of a spaghetti codebase and there’s been a lot of work to sort of separate things within that code base
(06:20) particularly or not particularly but one thing being like the wallet and the guey um and it feels like the last decade aid of Bitcoin core development specifically has been trying to get the implementation to a point where um things are separated appropriately, more modular and you can begin to do um things that that make it uh more complex, make it easier to build more complex applications on top of the Bitcoin protocol layer.
(06:57) Yeah, there’s definitely that’s one of the major things happening is historically splitting out these functionalities, getting them into their own containers that can be tested separately. Um, so focusing on like the charlatan he’s been working on, he’s been continuing carrying this torch on the lipcoin kernel. So being able to separate the consensus parts out of the codebase completely exposes an API so people can use reuse this either in in an alternative implementation or just for tooling.
(07:28) Um it’s not exactly you know a lot of this work is not glamorous in that there’s cost benefits to be weighed. Uh the cost is here is that when you’re refactoring these very critical parts of the codebase mostly consensus not wallet uh