Mar 1, 2022 · 39m · another-podcast
Talking about crypto
0:00 / 0:00
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Technology analysts Benedict Evans and Toni Karen Brown critically evaluate the mechanics, history, and real-world utility of cryptocurrency and Web3. They explore the tensions between speculative hype, decentralized governance, security trade-offs, and the complex infrastructure abstraction required to achieve mainstream adoption.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. The hosts hold 87.4% of the talking time here. How this is scored →
The hosts as informed peer 7.8 Guest teaching 1.4 Guest disagreement 1.2 The hosts pushing back 2.4
speaking balance: gold is the hosts, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 19:01 Questioning whether crypto builders know what problems they solve
Toni directly challenges the prevailing industry narrative by asserting that most participants in the crypto space do not actually know what problems they are attempting to solve.
Hardest push from the hosts ▶ 10:50 Pushing back on the practical benefit of raw data portabilityBenedict challenges Toni's point about regulatory enthusiasm for data portability, arguing that moving graph data from Instagram to LinkedIn offers zero value without network effects.
Biggest teaching moment ▶ 4:58 Reframing Web evolution around online hangout locationsToni reframes the abstract technical distinctions between Web1, Web2, and Web3 into an intuitive mental model based on where users hung out and who owned the space.
The host holds their own ▶ 30:45 Refusing shallow dismissals of blockchain scaling potentialBenedict demonstrates deep historical and technical command, forcefully dismissing critics who treat early performance bottlenecks as proof that the underlying architecture cannot scale.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The hosts as informed peer | Guest teaching | Guest disagreement | The hosts pushing back | Why |
|---|---|---|---|---|---|---|
| Defining the Evolution: Bitcoin, DeFi, and Web3 | 7 | 3 | 1 | 1 | Benedict traces the evolution of crypto across three distinct historical waves from Bitcoin to DeFi to Web3 computing. Toni interjects with a concise framework mapping Web1 through Web3 to digital hangout spaces. | |
| Navigating Hype, Scams, and Quiet Builders | 7 | 1 | 1 | 1 | Benedict separates public hype and scams from serious foundational builders, quoting industry peers like Logan Bartlett and Chris Dixon. Toni concurs that public media narratives drown out quiet technical work. | |
| Core Web3 Mechanics: Composability, Transparency, and Portability | 8 | 2 | 2 | 6 | Benedict details core Web3 architectural principles including consensus, transparency, and composability. When Toni notes regulators favor data portability, Benedict pushes back by pointing out that exporting personal social graph data into an empty competing network yields little value. | |
| Governance Challenges and Historical Lessons from Open Source | 8 | 1 | 1 | 2 | In response to Toni asking about downsides, Benedict draws on political science and open-source history to highlight governance traps in DAOs and consumer UI failures in Linux. | |
| SaaS Meets Open Source and Building Novel Products | 8 | 1 | 1 | 1 | Benedict explains how open source evolved into cloud SaaS infrastructure rather than desktop consumer software, framing crypto as SaaS combined with open-source composability. | |
| The Infrastructure Plumbing Stage and Early Tech Parallels | 8 | 2 | 2 | 2 | Toni notes that builders today may not know exactly what problems they are trying to solve. Benedict contextualizes this by comparing the current plumbing stage to early PC hardware complexity and 1990s packet switching skepticism. | |
| Usability Abstractions, Security Risks, and Decentralization Trade-Offs | 8 | 1 | 1 | 2 | Benedict analyzes security risks in smart contracts and explains the core tension between building user-friendly abstraction layers and maintaining Web3 decentralization. | |
| User Adoption Barriers and Scaling Without Breaking Web3 | 8 | 1 | 1 | 6 | Benedict uses a 1995 Linux hard-drive wipe anecdote to emphasize usability hurdles, while forcefully pushing back against superficial critics who dismiss blockchain scaling without providing fundamental theoretical constraints. | |
| Regulatory Enigmas and the Tangible Questions Dilemma | 8 | 1 | 1 | 2 | Benedict recounts discussions with EU regulators on decentralized antitrust and shares his marijuana farming metaphor regarding how crypto advocates deflect operational questions. | |
| Historical Misconceptions and the Five-to-Ten Year Horizon | 8 | 1 | 1 | 1 | Benedict looks at early web misconceptions like Tim Berners-Lee's browser editor to argue that mainstream crypto utility remains on a five-to-ten year horizon. |
Statements from this episode (18)
Evans: Much of Crypto's Actual Use Case Is Simply Speculating on Crypto
“And in fact, a lot of the use case of crypto is in fact speculating on crypto.”
Evans: Web3 Enables Building Fundamentally Different Kinds of Products
“It would allow you to build, not just to build a product in a different way, but build a different kind of product, which are two different important points”
Evans: Crypto scams proliferate because immature software was added to money
“Layered onto that, you have a huge amount of sort of scamming because basically you've added software to money and connected to the internet, and it's relatively early, immature software.”
Evans: Most interesting discourse is no longer happening on Twitter
“The public discourse is very different from the private discourse, and most of the interesting discourse isn't on Twitter anymore.”
Evans: Blockchains Expose Running Code and Transactions Unlike Traditional Open Source
“With open source, you could download the code and look at it, but you couldn't see it running inside Google. Whereas with a blockchain computer, you can see the code running and all the rules and all the transactions as they happen.”
Evans: Social Data Portability Fails Because Relational Network Effects Cannot Be Exported
“I could export my data, but most of my data is who's liked my pictures and who else they liked and who else follows them and who follows them. And A, I don't own this, but more to the point, if I am Like, go to a new network. Like, there's nothing in that new …”
Evans: Open source and Linux failed completely as consumer products
“So Linux failed completely. As a consumer product, open source failed completely at creating consumer products.”
Evans: Open source works for infrastructure, not consumer software
“Open source was hugely important in creating technology infrastructure and plumbing of every kind. And it was a much better organizational model for writing that software. It was not a great organizational model for writing end user software for consumers.”
Evans: Crypto enables governance and portability impossible with standard databases
“And crypto is basically sort of SaaS meets open source. So it's all sort of running publicly in the cloud. And so you can make different applications with this. You can do these incentive structures and open governance structures and portability that you can't…”
Evans: Crypto builders must make products uniquely enabled by crypto
“Don't clone office, make Google drive. Like that's making something that where it matters that it's the internet, make something where it matters that it's crypto.”
Evans: Tech platform maturity reduces visible infrastructure complexity
“As you create all of this capability and all this infrastructure and plumbing, at a certain point that kind of gets abstracted away and standardized and so on into Windows and Mac and so on. And then the visible complexity goes down again.”
Evans: Crypto is in an early-80s PC era of infrastructure and bullshit
“We're at this stage now of, like, internet early, PCs early eighties, internet early nineties, Enormous amounts of bullshit, and people kind of building this plumbing, and infrastructure, and that's where all the kind of clever, interesting stuff is.”
Evans: Mainstream users will not read code, necessitating crypto abstraction
“And you read this and you think, okay, that's not a mass market consumer experience any more than the command line was, any more than open source coding was, and you can believe everyone will learn the command line and everyone will write the code, but they pr…”
Evans: Running a full MMO on Ethereum is unfeasible
“And of course the Nirvana is everything runs on the chain, but try, try running a MMO, a massively multiplayer online game on Ethereum at like one transaction a second, like good luck.”
Evans: Comparing crypto's first 10-year development pace directly to the internet is flawed
“There's a kind of a dumb criticism is to say the fact that we don't have email and the web and so on yet for blockchain tells us we never will, which is just dumb. And there's, oh, well it happened in the first 10 years for the internet and we've been 10 years…”
Evans: Tim Berners-Lee's first web browser was also an editor
“The first web browser, Tim Berners-Lee's first web browser was also an editor because people thought this was like a document sharing tool.”