Bitlemmas

Bitlemmas exists to help the open‑source world build and govern truly decentralized, participatory community infrastructure. We do that by bridging: ● Old open‑source communities (Linux‑style foundations, maintainers, infra folks), and ● Bitcoin‑grade decentralization (no presale, no roadmap, no issuer, no censorship) ● Plus modern thinking on monetary policy and decentralized programming …so that more of those open‑source builders start designing and contributing to decentralized software and protocols that reflect these values. Our purpose is impact and alignment: upgrading the infrastructure of free communities so it stays free, resilient, and democratically governed.

The Democracy Project | Book Review 04/01/2026

Broken Money | Book Review 03/25/2026

Broken Money | Book Review Broken Money: Ledgers, Power, and the Future of Money The Ledger Framework of Money. In Episode 6 of the BitLemmas Podcast, Watson and B. Sovereign provide a comprehensive review of Lyn Alden’s book, Broken Money . The discussion moves beyond traditional economic theories to present a more effective mental model: money as a ledger governance system . By defining money as a combination of a ledger, governance rules, and network effects, the hosts explain how technological shifts reshape the ways we record and transfer value . This framework allows listeners to analyze any currency by identifying who can change its rules and what the consequences of those changes are for the users . Understanding Broken Ledgers. The transcript identifies the primary characteristics of a failing monetary system, which includes deposit freezes, capital controls, and runaway inflation . These failures occur when the governance of a ledger is captured to serve a small group at the expense of the majority, often through the expansion of the money supply . This flexibility in state governed ledgers allows for the opaque redistribution of wealth, often benefiting those closest to the money printer while diluting the purchasing power of savers . The conversation also highlights why the modern banking system is fragile by design due to maturity transformation, which creates inherent instability when short term debts outweigh long term asset returns . The Three Types of Monetary Ledgers. The hosts break down the evolution of money into three distinct categories based on their governance . Nature governed ledgers, such as gold, rely on physics and scarcity, making them difficult to manipulate . State governed ledgers, or fiat currencies, operate by decree with rules that are flexible and easily changed by political power . Finally, user governed ledgers, such as Bitcoin, function through open source consensus where rules are transparent and enforced by the users themselves . Each system carries different trade offs regarding portability, verifiability, and counterparty rist. Strategies for the Modern Money Stack. The episode concludes with a practical framework for building a personal money stack to route around systemic constraints . B. Sovereign suggests that individuals should intentionally categorize their wealth into spending, emergency, savings, and escape layers . While traditional bank deposits offer convenience, they carry the risk of being unbanked or facing capital controls . The hosts encourage listeners to audit their exposure to state governed ledgers and consider tools like self custody and user governed assets to ensure they own a piece of a ledger that cannot be arbitrarily devalued or frozen. 🌐 More at /episode/index/show/3afb197d-d16d-4de2-ac99-46fa31361707/id/40618305

The Lightning Network | Book Review 03/20/2026

The Lightning Network | Book Review The Lightning Network: Instant Bitcoin Payments (and the Real Tradeoffs) If you've ever wondered whether Bitcoin can actually compete with Visa, or why it currently can't, this episode is for you. In the fifth episode of The Bitlemmas Podcast, Watson, B. Sovereign, and Drew dig into Mastering the Lightning Network by Andreas Antonopoulos. The one thing Watson wants you to walk away with: Bitcoin is the court. Lightning is the cash register. Lightning is not a new coin. It's not a new chain. It's a contract system built on top of real Bitcoin, with Bitcoin itself acting as the enforcement layer when something goes wrong. The book's core argument is that Bitcoin's Layer 1 was never designed to handle every coffee purchase on the planet, and trying to force it to do that would undermine the decentralization that makes it worth using in the first place. Lightning is how you get fast, cheap, private payments without giving up self-custody. Watson walks the team through four things the book gets right that most people misunderstand: Bitcoin is the court, Lightning is the cash register. Most Lightning payments never touch the blockchain at all. But every Lightning contract is always enforceable on-chain if needed. Bitcoin doesn't get faster; payments do. The settlement layer stays slow, final, and sovereign. The spending layer becomes instant and nearly free. And unlike credit cards, Lightning payments have no chargebacks. When it's done, it's done. Treat it like the cash in your pocket. A channel is a shared vault, not an account. Two parties lock up Bitcoin in a two-of-two multisig on-chain. Neither one can move those funds without the other's cooperation. Off-chain, they pass signed balance updates back and forth, called commitment transactions, which are cryptographically certain and far stronger than anything on paper. B. Sovereign puts it well: it's like a safe deposit box you both own, passing notes that say "I now have 90%, you have 10%." The on-chain layer only comes into play if someone tries to cheat, or when both sides decide to close things out. Multi-hop payments can be trustless. You can pay anyone on the Lightning network without a direct channel to them. The money routes through intermediaries, and none of them can steal it. The mechanism is HTLCs (hash time-locked contracts): the recipient creates a secret, hashes it, and the payment locks at every hop to that hash with a deadline. When the recipient reveals the secret to collect, that reveal unwinds backwards through every node in the chain. Either the full payment goes through, or everyone gets their money back. There's no partial outcome. As Drew points out, you're not just sending money; you're enforcing conditions across multiple parties at the same time. Lightning is a liquidity and operations game. Channel capacity is public. Channel balances are private. Inbound and outbound liquidity are not the same thing, and managing that difference is what Lightning operations actually comes down to. Pathfinding is probabilistic, not a straight line. Payments can fail mid-route because a node's liquidity is sitting on the wrong side. B. Sovereign pulls from his finance background here: without balance between supply and demand, nothing moves. Running Lightning properly takes uptime, backups, security hygiene, and regular rebalancing. It is not a set-and-forget wallet. The conversation also covers the risks that tend to get skipped in the hype. Lightning is a hot wallet by design, which means your keys live on an internet-connected device. People the team knows personally have lost money running Lightning nodes without proper care. Watchtowers exist to protect you when you go offline, but only if you set them up and use them. Liquidity jamming is also a real attack where someone deliberately locks up your channels and stops you from processing payments. Watson wraps up with straightforward advice: Bitcoin is your savings, Lightning is your spending. Don't confuse the two. Get a noncustodial wallet like Phoenix or Muun, put $20 worth of Bitcoin in it, and make one payment this month. Get comfortable before you try to optimize anything. And if you're building on Lightning, run a node for a month, open a few channels, and experience the friction yourself, because that friction is where the next round of useful tools needs to come from. 🌐 More at /episode/index/show/3afb197d-d16d-4de2-ac99-46fa31361707/id/40560445

The Block Size War | Book Review 03/18/2026

Slicing Pie | Book Review 03/09/2026

Slicing Pie | Book Review Slicing Pie: Fair Ownership Without Fantasy Valuations What is the most dangerous question you can ask inside an early-stage venture? According to Slicing Pie by Mike Moyer, it is this: "What do we each get?" In the third episode of The Bitlemmas Podcast, host Watson — joined by B. Sovereign and Drew — breaks down one of the most practical books ever written on startup equity, and makes the case that fixed splits are not just inefficient. They are a trap. The book's central argument is deceptively simple: early equity is nearly impossible to value, and yet people always demand fairness. Traditional arrangements — the 50/50, the 33/33/33 — seem clean upfront but collapse the moment reality diverges from the plan. And it always diverges. Moyer's solution is what he calls a contribution ledger: a dynamic system that tracks relative inputs over time, and converts them into formal equity only when a real valuation event occurs — a funding round, an acquisition, or the moment payroll becomes sustainable. Watson walks through four counterintuitive but ultimately true claims from the book: Fixed splits always create fairness problems. Whether you slice the pie early or late, you are guessing. Do it upfront and you are betting on how much each role will matter — which you cannot know. Do it after the fact and you are trusting everyone's self-reported memory of what they contributed. Both approaches accumulate what Watson calls fairness debt: a growing, invisible gap between what people believe they are owed and what the arrangement actually delivers. Equity can be worthless now and still burn you. Ideas have no market value. Early equity is theoretical. But the promise of future fairness is real — and perceived betrayal of that promise damages relationships, erodes trust, and kills the collaboration before there is anything to split. The book's warning is not to wait until it matters. Fairness requires a ledger — rules and tracking. Not because you do not trust your partners, but because memory is unreliable and people's beliefs about what they are owed drift upward over time. As Drew puts it, drawing on his background in underwriting: in math we trust. The ledger replaces personal trust with an objective record. B. Sovereign adds that it eliminates memory-based arguments — contributions become visible, politics shrink. You do not need valuation. You need conversion rules. Moyer does not ask you to assign a price to the company. He asks you to agree on how inputs — hours, cash, assets — will be converted into ownership when a real valuation moment finally arrives. Hours are the foundation, with multipliers for unpaid time (2x) and cash investment (4x) that reflect the actual risk being taken. The conversation goes well beyond the book's mechanics. Watson details a cautionary scenario — the absentee 33% stakeholder who refuses to dilute when a new investor arrives, years after the original work was done — and explains why this is one of the most common deal-killers in early-stage fundraising. Drew connects the framework to the music industry and the structural exploitation built into fixed contracts. B. Sovereign ties overvaluation obsession to real startup wreckage he witnessed firsthand. Watson also introduces Moyer's concept of the Grunt Fund — the dynamic ownership pool where every logged contribution earns a proportional claim — and closes with a teaser toward Radical Company, a complementary framework for valuing what the ledger cannot count: community, evangelism, and intangible effort. The episode ends with a provocation that cuts past startups entirely: consent does not make a contract fair. Entering an agreement of your own free will does not absolve you from reasoning about whether its terms are just. That is the philosophical spine underneath all the spreadsheets. If you are building anything with other people — a startup, a side project, a creative collaboration — this episode will make you want to agree on the rules before a single hour is logged. 🌐 More at /episode/index/show/3afb197d-d16d-4de2-ac99-46fa31361707/id/40361375

The Starfish and the Spider | Book Review 03/02/2026

The Starfish and the Spider | Book Review The Starfish and the Spider: Decentralization, Resilience, and the Limits of Control What if the most resilient organizations in history succeeded precisely because they had no leader to overthrow? In the second episode of The Bitlemmas Podcast, host Watson breaks down The Starfish and the Spider by Ori Brafman and Rod Beckstrom — a book that flips conventional wisdom about leadership, power, and organizational design on its head. Watson walks through the book's central argument: that centralized ("spider") organizations are fast and efficient, but dangerously brittle — they have a head, and heads can be cut off. Decentralized ("starfish") organizations, by contrast, are slower to coordinate but nearly impossible to destroy. Cut off an arm, and it grows back. Take out a node, and the network adapts and multiplies. The episode covers four counterintuitive but compelling claims from the book: Efficiency creates a kill switch. When Cortez conquered the Aztec empire, he didn't need to defeat every village — he just needed to reach Montezuma. Spider systems collapse when their choke points are targeted. That single decision center is both a feature and a fatal flaw. Pressure creates more decentralization. When Napster was shut down, it didn't kill file sharing — it gave birth to headless, distributed networks that were far harder to stop. Starfish systems don't just survive attacks; they evolve because of them. The best leaders give away power. Not pseudo-participation, not "come share your feelings before I make the decision" — but real, binding decision-making power pushed to the edges. Watson draws a sharp distinction here and doesn't let the concept off easy. You can't manage a starfish with spider metrics. Decentralized organizations don't produce the kind of tidy accountability structures that traditional management demands. Trying to measure them the same way reveals more about the measurer than the org. Watson and co-host Brandon also dig into the book's concept of the catalyst — a rarely celebrated type of leader who sparks circles and then fades into the background, deliberately avoiding the choke points that hero-leaders inevitably become. And a third voice raises the hard question: how realistic is all of this? Do people actually rally around shared ideology without a charismatic figure holding it together? From Alcoholics Anonymous to the Apache, from Napster to modern software architecture, this episode connects the book's ideas to real-world systems — and challenges you to ask: if your CEO disappeared tomorrow, what stops? Whether you're building a product, a community, or an organization, this episode will change how you think about control, resilience, and the hidden cost of being a spider. 🌐 More at /episode/index/show/3afb197d-d16d-4de2-ac99-46fa31361707/id/40283975

The Price of Tomorrow | Book Review 02/27/2026

Bitlemmas

TOPICS