Sep 24, 2026 · 45 min · 12 segments
Almost every public Bitcoin node still runs Bitcoin Core. Brandon Black argues that client monoculture is a systemic risk — and that automation plus AI now make independent consensus implementations…
Stephan LiveraHost
Maybe you can set the scene a little bit because this is the first episode in this little miniseries, let's say.

But can you just give a sense of like, you know, rough numbers, who... how many people are using Core, what percent is on Core, what percent is on using some of the others? Like, I think it's about 80 last I checked on...

Of the 25,720 public nodes running on the Bitcoin network, 21,385 are Bitcoin Core.

It says 4,300 are Bitcoin not, but I presume that's pre, obviously pre-110, you know.
Yeah, I mean, I think as Toshi commented, there's, there's risk of consensus divergence when you run an alternative node implementation because there's no spec for, um, the Bitcoin protocol.
A- and so I think that's why all the public nodes essentially, it, it's a rounding error other than that, uh, run Bitcoin Core as their main consensus implementation.
So I've been talking with some folks since I started rBitcoin on the topic of how can we change that, how can we make it safe to run multiple implementations, and there's a lot of different opinions about that.
So, so Toby over at hornetnode, he's trying to create a written spec for consensus so that we can move away from that idea that you have to run Core to be in consensus.
If we have it written down, we can actually check every node against those consensus rules.
And then Epoch over at satd, he runs his own consensus rules in parallel with libbitcoin consensus against every, every transaction, so he's always checking with every transaction to see if he's in consensus.

Specifically, is that the libbitcoin kernel, or I think it's now been called Bitcoin Core kernel, the thing that sedated is doing, that thing or another thing?

Maybe you can set the scene a little bit because this is the first episode in this little miniseries, let's say.

But can you just give a sense of like, you know, rough numbers, who... how many people are using Core, what percent is on Core, what percent is on using some of the others? Like, I think it's about 80 last I checked on...

Of the 25,720 public nodes running on the Bitcoin network, 21,385 are Bitcoin Core.

It says 4,300 are Bitcoin not, but I presume that's pre, obviously pre-110, you know.
Yeah, I mean, I think as Toshi commented, there's, there's risk of consensus divergence when you run an alternative node implementation because there's no spec for, um, the Bitcoin protocol.
A- and so I think that's why all the public nodes essentially, it, it's a rounding error other than that, uh, run Bitcoin Core as their main consensus implementation.
So I've been talking with some folks since I started rBitcoin on the topic of how can we change that, how can we make it safe to run multiple implementations, and there's a lot of different opinions about that.
So, so Toby over at hornetnode, he's trying to create a written spec for consensus so that we can move away from that idea that you have to run Core to be in consensus.
If we have it written down, we can actually check every node against those consensus rules.
And then Epoch over at satd, he runs his own consensus rules in parallel with libbitcoin consensus against every, every transaction, so he's always checking with every transaction to see if he's in consensus.

Specifically, is that the libbitcoin kernel, or I think it's now been called Bitcoin Core kernel, the thing that sedated is doing, that thing or another thing?
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.