Jun 22, 2026 · 36 min · 14 segments
Every blockchain today leans on replication ideas worked out in the 1980s, by a Turing Award winner who wasn’t thinking about how it might apply to money at all. In this episode of First Principles…
Tim RoughgardenHost
Ittai AbrahamHostWell, it-- I, I may have thought of it as a pivot, but my first project there was a programming language, and that programming language was really an extension of the language I'd already developed.
We had this language called CLU, which supported abstract data types and objects.
And in Argus, which was the new language, we had abstract data types, and then we had one additional feature, this new kind of object, which we called a guardian.
And so the idea was a distributed program consisted of all these guardians, each running on its node, communicating with each other.
It was, in fact, picking up something I'd had to leave behind for CLU, which was parallel computing.
I had decided in CLU that that was gonna be a sequential language because I felt we had enough stuff going on that I didn't wanna complicate it by adding concurrency as well.
And so now I was able to pick up concurrency, but in this more interesting world where concurrency wasn't just that you had a for loop where you ran a bunch of threads in parallel, but instead you had multiple users, and they might be making requests in parallel and stuff like that.
And one of the interesting things about Argus was that we had to worry not just about concurrency, but also failures.
And we had computations there that would visit several nodes of the network, and then at the end, we had to make sure that such a computation either happened completely or had no impact whatsoever.
And so of course, we picked up transactions from database systems, and we ran those computations as atomic transactions, and we had a two-phase commit protocol going on.
It seemed like a continuation in a more, uh, evolved or complicated environment, so which allowed me to look at additional problems.
Well, it-- I, I may have thought of it as a pivot, but my first project there was a programming language, and that programming language was really an extension of the language I'd already developed.
We had this language called CLU, which supported abstract data types and objects.
And in Argus, which was the new language, we had abstract data types, and then we had one additional feature, this new kind of object, which we called a guardian.
And so the idea was a distributed program consisted of all these guardians, each running on its node, communicating with each other.
It was, in fact, picking up something I'd had to leave behind for CLU, which was parallel computing.
I had decided in CLU that that was gonna be a sequential language because I felt we had enough stuff going on that I didn't wanna complicate it by adding concurrency as well.
And so now I was able to pick up concurrency, but in this more interesting world where concurrency wasn't just that you had a for loop where you ran a bunch of threads in parallel, but instead you had multiple users, and they might be making requests in parallel and stuff like that.
And one of the interesting things about Argus was that we had to worry not just about concurrency, but also failures.
And we had computations there that would visit several nodes of the network, and then at the end, we had to make sure that such a computation either happened completely or had no impact whatsoever.
And so of course, we picked up transactions from database systems, and we ran those computations as atomic transactions, and we had a two-phase commit protocol going on.
It seemed like a continuation in a more, uh, evolved or complicated environment, so which allowed me to look at additional problems.
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.