The Bitlemmas Podcast

The Bitlemmas Group

Bitlemmas | The Book Club for the Open-Source World Open-source built the internet. Linux, Git, Apache, PostgreSQL — the backbone of modern computing was written by communities, not corporations. But today, those same communities are slowly being captured: by corporate foundations, centralized governance, and infrastructure they no longer control. Who's keeping it free? Bitlemmas is a podcast dedicated to that question. Every episode, we dig into books on Bitcoin, monetary history, decentralized protocols, and open-source governance - reviewing them critically, debating their ideas, and connecting them back to the builders who need them most. No fan interviews. No hype cycles. Just serious reading, honest critique, and conversations that actually go somewhere. We sit at a very specific crossroads: The old open-source ethos - maintainers, foundations, infra folks Bitcoin-grade decentralization - no premine, no roadmap, no issuer, no censorship Monetary literacy and protocol design If you're a developer, maintainer, protocol designer, or open-source contributor who wants to understand how decentralized systems are governed — and how they should be — this is your show. What we cover: - Bitcoin and the Bitcoin ecosystem - Monetary history and policy - Decentralized protocol design - Open-source governance and community infrastructure - Participatory democracy in software communities

  1. Sep 21

    The NOSTR Protocol | Book Review

    Nostr is often pitched as "Twitter without a company," but that mental model breaks down fast. In this episode, Watson and B Sovereign do a full protocol review of The Nostr Protocol in a Single Page, the compact reference ebook by Jeff Gardner, and unpack what Nostr actually is: a signed event language carried by independently operated relays. We separate the myths from the mechanics: identity as a key pair instead of a platform account, why relays can censor but can never counterfeit a signature, how portability quietly shifts routing work onto the client, and why even a tiny protocol core still needs human coordination through NIPs, or Nostr Implementation Possibilities. Along the way, we compare Nostr's approach to federated alternatives like ActivityPub, including Mastodon and Lemmy, walk through the full publish and read paths, dig into key management, private messaging (NIP-17, NIP-44, NIP-59), deletion semantics, Negentropy sync (NIP-77), and close with a builder's checklist, a choke point to exit point analysis for anyone designing a Nostr client or relay. In this episode: Why Nostr separates portable authorship from replaceable transport The four counterintuitive truths of the Nostr protocol How NIP-01 events are created, signed, and verified Why relays are sovereign but cannot forge your signature How NIP-65 and the outbox model handle routing and discovery The real tradeoffs in private messaging, key custody, and deletion Five protocol choke points and the exit pattern for each one Resources mentioned: The Nostr Protocol in a Single Page (ebook) by Jeff Gardner, NIP-01, the base Nostr protocol, and the full NIP index at github.com/nostr-protocol/nips. Bitlemmas is the book club for open source builders who take decentralization seriously. Every episode, we review a book or protocol on Bitcoin, monetary history, decentralized programming, or community governance, then connect the ideas back to real code and real projects. Subscribe for new episodes, and visit bitlemmas.com to leave feedback or suggest the next book.

  2. Sep 16

    Self-Sovereign Identity | Book Review

    Your driver's license already does selective disclosure badly. Self-Sovereign Identity shows what it looks like done right. In episode 25 of the Bitlemmas book review series, Watson, b sovereign, and Jose dig into Self-Sovereign Identity by Alex Preukschat and Drummond Reed, a guide to decentralized digital identity and verifiable credentials, often shortened to SSI. The book's starting point: most of what gets called digital identity online is really just an identifier controlled inside someone else's database, whether that's a siloed account and password or a federated login through a large identity provider like Google. In both cases, the practical control point sits outside the person. The hosts trace the book's path from face to face trust, to institution issued identifiers, to account based logins, to federated single sign on, and finally to peer controlled digital relationships built on decentralized identifiers, or DIDs, and verifiable credentials held in a personal wallet. Along the way they work through the book's four counterintuitive truths: identity is not your account, the less you disclose the more useful identity becomes, decentralization is a relationship model, and cryptography is necessary but governance is what actually lets trust scale. The episode spends real time on selective disclosure (proving you're over 21 without handing over your home address), the difference between an identifier and an identity, pairwise DIDs and how they stop platforms from correlating your activity across relationships, and why a governance framework, not just a cryptographic signature, is what lets a verifier trust an issuer they've never met. The back half runs a choke point to exit analysis for builders: the account landlord, the shared password, issuer by issuer trust, the custodial recovery trap, and the governance framework itself as a potential gatekeeper, each with the exit pattern SSI proposes. The hosts close with a set of practical questions for anyone building identity products: does the user know which relationship they're acting in, can they prove only what's needed, and can they leave a provider without losing their identity. Visit bitlemmas.com for more and to leave feedback in the comments.

  3. Aug 26

    Community and Privacy | Book Review

    In this episode, Watson, B. Sovereign, and Jose explore the groundbreaking architectural theory from Sergei Chermayeff and Christopher Alexander's Community and Privacy—a book that reframes one of modern society's greatest misconceptions: that privacy and community are opposing forces. Discover why privacy isn't isolation, but rather the architecture that makes meaningful community possible. We break down Chermayeff and Alexander's six-realm privacy gradient (from urban public to individual private), examine the critical role of locks and buffers in design, and challenge the myth that openness alone creates thriving neighborhoods and vibrant cities. This episode goes beyond physical architecture, exploring how these principles apply directly to software design and product decisions. We discuss the tension between visibility and consent, the concept of "worse is better" in open-source development, ubiquitous language, and why exposure thresholds must be designed before users encounter them. Perfect for architects, software engineers, product designers, and anyone interested in how human-scale design shapes both community and digital experiences, this episode asks the essential question: Where does your product collapse private, shared, and public realms? Key Topics: Privacy architecture, community design, thresholds, locks and buffers, exposure control, software design patterns, open-source philosophy, pattern language, Christopher Alexander, ubiquitous language, bottom-up design. Listen now and explore how thoughtful boundaries create thriving communities.

    Community and Privacy | Book Review
  4. Aug 10

    Guild Socialism Restated | Book Review

    Can a workplace really be democratic while a boss still signs everyone's paychecks? This episode digs into G.D.H. Cole's Guild Socialism Restated — a 1920s blueprint for industrial democracy that's aged into a surprisingly modern playbook for governance design. Cole's core move: authority should be scoped, not seized. Producers govern their own work, consumers get real safeguards over price and quality, and coordination between them stays a service, not a command. We walk through his four counterintuitive truths — democracy can't stop at parliament, producer rule is incomplete without consumer checks, decentralization still needs institutions, and coordination turns dangerous the moment it becomes command — and translate each one into a real-world test: a cooperative grocery store, then a software platform, where the same person shows up as both producer and consumer with different claims in each role. Along the way: why political scientists secretly like voter apathy, the difference between a guild and a cartel, why "worse is better" beats a hidden benevolent dictatorship, and a builder's checklist for making authority visible before conflict forces the question. Topics covered: 00:00 — Intro and the book's central thesis: industrial democracy with scoped authority 02:37 — Framing the episode: the authority layer, and what keeps coordination from becoming domination 05:45 — The four counterintuitive truths, previewed 06:20 — Truth 1: Democracy cannot stop at parliament 31:02 — Truth 3: Decentralization needs institutions 44:56 — Truth 4: Coordination becomes dangerous when it turns into command 1:08:16 — Builder patterns: sane defaults, MVP thinking, and "worse is better" 1:11:01 — Questions to contemplate 1:11:28 — Conclusion, plus the one model, one story, and one action for this episode Source referenced: G.D.H. Cole, Guild Socialism Restated (1920). Leave your thoughts in the comments or find past episodes at bitlemmas.com.

    Guild Socialism Restated | Book Review
  5. Aug 5

    Patterns of Distributed Systems | Book Review

    BitLemmas Episode 22 - Patterns of Distributed Systems Breaking down how real systems like leader election, quorums, replication, and consensus actually work under the hood. Hosts Watson and B. Sovereign walk through why adding servers doesn't remove limits, it just moves the hard part into coordination, and connect it directly to Bitcoin's own block size war debate over throughput versus decentralization. This episode covers: The four counterintuitive truths of distributed systems: more servers create more coordination work, replication isn't commitment until it's defined, quorums buy safety at the cost of throughput and latency, and time is a protocol decision, not a wall clock Write-ahead logs, high watermarks, and how leader-follower replication actually commits a write Crash faults vs Byzantine faults, and how quorum sizing changes between them A plain-English walkthrough of the Paxos consensus algorithm using a group-chat dinner analogy Lamport clocks, hybrid clocks, and Google Spanner's approach to clock-bound time Two-phase commit, gossip protocols, and the split-brain problem that shaped modern consensus algorithms The FLP impossibility result and why safety and liveness can't both be guaranteed A critique of the book's pattern language, drawing on Christopher Alexander's The Timeless Way of Building and Eric Evans's Domain-Driven Design Builder takeaways: why visible guarantees beat hidden distributed magic, and how to onboard users into a framework's trade-offs If you're building or reasoning about distributed systems, databases, or decentralized protocols, this episode is a practical field guide to the patterns that keep state correct when machines, messages, and clocks can't be trusted. Leave feedback in the comments at bitlemmas.com. Visit bitlemmas.com for more episodes and show notes.

    Patterns of Distributed Systems | Book Review

About

Bitlemmas | The Book Club for the Open-Source World Open-source built the internet. Linux, Git, Apache, PostgreSQL — the backbone of modern computing was written by communities, not corporations. But today, those same communities are slowly being captured: by corporate foundations, centralized governance, and infrastructure they no longer control. Who's keeping it free? Bitlemmas is a podcast dedicated to that question. Every episode, we dig into books on Bitcoin, monetary history, decentralized protocols, and open-source governance - reviewing them critically, debating their ideas, and connecting them back to the builders who need them most. No fan interviews. No hype cycles. Just serious reading, honest critique, and conversations that actually go somewhere. We sit at a very specific crossroads: The old open-source ethos - maintainers, foundations, infra folks Bitcoin-grade decentralization - no premine, no roadmap, no issuer, no censorship Monetary literacy and protocol design If you're a developer, maintainer, protocol designer, or open-source contributor who wants to understand how decentralized systems are governed — and how they should be — this is your show. What we cover: - Bitcoin and the Bitcoin ecosystem - Monetary history and policy - Decentralized protocol design - Open-source governance and community infrastructure - Participatory democracy in software communities