Nov 9, 2026 · 38 min · 9 segments
Josh chats with Lance and Anton from Caution about verifiable computing. We start out discussing all the challenges in bootstrapping software that almost nobody thinks about anymore. We then make our…
Josh BressersHost
And I'm very curious about because like historically speaking, for anyone who's never done this before, and you guys correct me if I get any of this wrong, because it's been it's been a minute.


And you'd have to first build the bootstrap compiler and the bootstraps compilers to build like another compiler.

And then that compiler builds the real compiler, right? And you're talking about, I guess, functionally that process, except you're starting from like nothing and then bootstrapping your way into a compiler.

How do you even start from nothing? You're welcome to get as technical as you want here because this is intriguing to me and I'll just ask dumb questions if I don't know what you're talking about.
Yeah, so step one, this is what this project called Stage Zero kind of came up with, which is you start with this tiny, tiny bit of machine code, but is intentionally written in a very commented and structured way to be human-auditable, human-readable.
So you're literally just writing hex characters, machine code, and this is meant to be a human-auditable tiny binary that if run Okay, hold on.

You're literally writing a binary with like hexadecimal characters inside of it.
Yes.
So it's called hex zero.
And we only want to do that in one place because it's a pain.
It is it is not something you want to maintain.
And so you start from this auditable seed.
And the idea there with that seed is that it should be simple enough of a spec that you could even implement it yourself probably more easily in a different language than you might be able to write it in hex zero.
And there's multiple alternative implementations.
You can even approximate it with like set an awk one-liner.
But the cool part is the output of this is you get a binary that you can then feed its own commented annotated code and then back out will come the same exact executable with the same hash, so it's self-hosting.
And then that can run a little bit more complicated version of itself until you get up to an actual basic assembler.
So then we get like...
All of these early, very painful steps to get to TinyCC, and from TinyCC is actually a very big unlock, because although it's a very, very minimal C compiler, it's sufficient enough to actually bootstrap Golang directly, which is pretty cool because Golang has a really rich standard library and you can do lots of things with it.

And I'm very curious about because like historically speaking, for anyone who's never done this before, and you guys correct me if I get any of this wrong, because it's been it's been a minute.


And you'd have to first build the bootstrap compiler and the bootstraps compilers to build like another compiler.

And then that compiler builds the real compiler, right? And you're talking about, I guess, functionally that process, except you're starting from like nothing and then bootstrapping your way into a compiler.

How do you even start from nothing? You're welcome to get as technical as you want here because this is intriguing to me and I'll just ask dumb questions if I don't know what you're talking about.
Yeah, so step one, this is what this project called Stage Zero kind of came up with, which is you start with this tiny, tiny bit of machine code, but is intentionally written in a very commented and structured way to be human-auditable, human-readable.
So you're literally just writing hex characters, machine code, and this is meant to be a human-auditable tiny binary that if run Okay, hold on.

You're literally writing a binary with like hexadecimal characters inside of it.
Yes.
So it's called hex zero.
And we only want to do that in one place because it's a pain.
It is it is not something you want to maintain.
And so you start from this auditable seed.
And the idea there with that seed is that it should be simple enough of a spec that you could even implement it yourself probably more easily in a different language than you might be able to write it in hex zero.
And there's multiple alternative implementations.
You can even approximate it with like set an awk one-liner.
But the cool part is the output of this is you get a binary that you can then feed its own commented annotated code and then back out will come the same exact executable with the same hash, so it's self-hosting.
And then that can run a little bit more complicated version of itself until you get up to an actual basic assembler.
So then we get like...
All of these early, very painful steps to get to TinyCC, and from TinyCC is actually a very big unlock, because although it's a very, very minimal C compiler, it's sufficient enough to actually bootstrap Golang directly, which is pretty cool because Golang has a really rich standard library and you can do lots of things with it.
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.