Stephan Livera Podcast

Bitcoiners built L402 for a Lightning-native web. Crypto built x402 for agents — and early volume is mostly stables. Ben Carman helped get Lightning into the x402 standard, and argues the pragmatic move is to meet that stack in the middle rather than wait for L402 alone.
Ben Carman of Spiral rejoin me to unpack HTTP 402 Payment Required, facilitators versus Coinbase Commerce, why agentic payments are still near zero today, and why AI agents may adopt Bitcoin faster than humans — because models already know sats, invoices, and QR codes.
Timestamps:
00:00 — Intro
00:50 — L402, x402, and MPP
01:09 — What HTTP 402 Actually Is
02:41 — Meet x402 in the Middle
03:44 — Facilitators and Coinbase Default
06:06 — x402 Standard vs Coinbase Commerce
07:26 — Stables Dominate Early Volume
08:03 — Agentic Payments Still Near Zero
08:55 — Agents Already Know Bitcoin
12:05 — Personal Agents vs B2B Agents
13:03 — Pay-Per-Query Agent Wallets
16:14 — Businesses on Bitcoin Are Easier
16:39 — AI Climb and Builder Craft
22:29 — Won't Fund OpenAI — Still Uses Them
25:38 — Cost Deflation = Human Freedom
28:57 — Best AI tools as of Oct 2
31:16 — Terminal Bench and Real Evals
32:25 — Bench Maxing vs Real Feel
34:59 — Four Years From ChatGPT
36:56 — Quantization Without the LARPs
39:51 — Mesh Alliance and Mesh LLM
42:37 — Goose, LDK, Think Big
Links: 
https://x.com/benthecarman

https://x.com/spiral_xyz

Stephan Livera links:
Follow me on X: @stephanlivera

Subscribe to the podcast

Subscribe to Substack

Bitkey ditched seed phrases for a recovery-focused 2-of-3 design: an app key, hardware key, and Block server key that use phones, hardware, and cloud access to help people retain control of their funds.
Clay Garrett, Bitkey lead at Block, joins Stephan Livera to explain the design trade-offs: safety as security plus recoverability, cloud backup that needs your hardware to decrypt, and why Bitkey does not treat vendor lock-in as its ethos.
They dig into recovery paths, multi-vendor trade-offs, transfer-without-hardware limits, Recovery Contacts and inheritance, a working FROST prototype, what covenants could move on-chain, chain code delegation, and privacy-conscious Electrum options.
Timestamps:
00:00 — Intro
00:19 — Clay Garrett Joins — Bitkey at Block
00:56 — Bitkey V2 and the 2-of-3 Model
03:03 — Safety Means Access and Recoverability
04:11 — App+Hardware Spends Without Block
07:09 — Cloud Backup and Instant Phone Swap
09:27 — Lost Hardware and the 7-Day Delay
12:14 — Vendor Lock Is Temporary, Not Ethos
15:44 — Multi-Vendor After Coldcard
21:20 — Which Wallet Fits Your Threat Model?
26:49 — $5 Wrench and Transfer Without Hardware
30:04 — Recovery Contacts and Inheritance
36:06 — FROST Prototype Already in the Repo
38:04 — On-Chain Looks Like Single-Sig
39:34 — Covenants Could Move Policy On-Chain
42:09 — Chain Code Delegation — BIP 89
46:10 — Electrum, Mempool, and Custom Servers
52:08 — Industry After Coldcard Changed
55:21 — Wallet Plus Free-for-Life Co-Signing
Links: 
https://x.com/clay_garrett

https://bitkey.world/

Stephan Livera links:
Follow me on X: @stephanlivera

Subscribe to the podcast

Subscribe to Substack

Most crypto exchanges are built like casinos: they chase the next hot token, prediction market, or trading product. Relai is building a different category—a savings brand for people who want to accumulate Bitcoin, hold it in self-custody, and build wealth over the long run. Julian Liniger explains why serving patient savers requires a different product, message, and business model.
The conversation also explores why rising living costs are pushing Europeans to rethink ordinary savings, and why the temptation to get rich quickly can drive people toward momentum trading and leverage. Julian makes the case for a longer time horizon: Bitcoin savings is less about chasing the next move and more about consistently building a position through changing market conditions.
Supporting context includes Relai's MiCA compliance journey, where regulatory overhead is costly but can also raise the bar for smaller competitors. Julian also discusses the company's self-custody model and reports more than 100,000 users holding over 20,000 BTC in their own wallets—not under Relai management. The episode covers how a Bitcoin-only company can earn revenue through services around long-term ownership while keeping the savings proposition at the center.
Timestamps:
00:01 — Europe's Cost of Living Squeeze
03:11 — Why Europeans Still Don't Get Bitcoin
07:37 — High Time Preference & Get-Rich-Quick
10:31 — Bitcoin Needs Patience Again
10:54 — AI Hype vs Bitcoin as Savings
14:58 — Bitcoin Is Where You Keep Your Winnings
21:42 — Leverage, Treasury Cos & Risk
23:46 — Relai Private Loans in Europe
29:03 — MiCA: Overhead and Moat
33:11 — Bitcoin Savings vs Casino Exchanges
35:26 — 100k Users, 20k+ BTC Self-Custody
37:49 — Retail App vs Relai Private
40:00 — Self-Custody Phone Wallet
42:58 — Seven-Figure Raise in a Bear Market
45:12 — AI for Building and Securing Relai
50:00 — Living Costs Drive Bitcoin Search
Links: 
https://x.com/julian_liniger

https://x.com/relai_app

Stephan Livera links:
Follow me on X: @stephanlivera

Subscribe to the podcast

Subscribe to Substack

Bitcoin soft-fork debates around CTV, CSFS, OP_CAT, and OP_VAULT keep stalling — and Misha Komarov of Allocinit argues you can emulate much of that covenant behavior with cryptography instead of changing consensus.
Misha joins Stephan to unpack Bitcoin PIPEs v2: a Witness Encryption design that locks a signing key under an NP statement so a valid zero-knowledge proof decrypts the key and produces an ordinary Schnorr spend. Bitcoin L1 only checks a normal signature.
They compare PIPEs v1 (Functional Encryption / richer post-covenants) with v2 (Witness Encryption / binary pre-covenants), ciphertext sizes from ~300 TB toward single-digit terabytes, DKG and 1-of-n setup assumptions, non-custodial vault and shared-pool use cases, contrasts with cosigner models like Sigbash, and how Allocinit’s Shielded Bitcoin design differs from Shielded CSV’s client-side validation approach — plus open cryptanalysis challenges and a path toward implementable code.
Timestamps:
00:00 — Intro: Misha & Bitcoin PIPEs v2
00:27 — Background: BitMessage to =nil;
01:31 — Soft-Fork Fatigue & Nice-to-Haves
03:24 — Emulate Opcodes Without Soft Forks
04:54 — Witness Encryption Unlocks Keys
06:01 — Witness Encryption vs Bitcoin Witness
09:00 — PIPEs v1 vs v2: FE to WE
11:39 — Ciphertext Size & Cost Trade-offs
15:28 — Vaults as the Unhappy Path
16:23 — PIPEs vs Sigbash Cosigner
18:05 — DKG Setup & 1-of-n Trust
21:11 — Shared Vaults & Lending Use Cases
23:24 — Beyond Canonical OP_VAULT
26:35 — Shielded Bitcoin vs Shielded CSV
32:17 — Self-Custody Peg-In and Peg-Out
37:14 — On-Chain Footprint Walkthrough
39:42 — Security Challenges & Code Roadmap
Links: 
https://x.com/nemothenoone

https://x.com/allocinitxyz

Stephan Livera links:
Follow me on X: @stephanlivera

Subscribe to the podcast

Subscribe to Substack

Almost every public Bitcoin node still runs Bitcoin Core. Brandon Black argues that client monoculture is a systemic risk — and that automation plus AI now make independent consensus implementations more realistic than skeptics assume.
Brandon (aka reardencode) returns to Stephan Livera Podcast for the first episode in a mini-series on non-Core Bitcoin implementations. He is shipping rbitcoin, a Rust full node aimed at server-side wallet and Lightning backends, with Electrum served in-process.
They dig into why rbitcoin has no UTXO set and no Core-style dbcache, how build-time differential testing differs from satd’s in-process libbitcoinconsensus dual-eval, BIP324 v2-only P2P, archival storage tradeoffs, LibreRelay-inspired policy, and what “production-ready™” means when every first-party line was written by AI under his prompting.
Brandon is blunt about maturity: the project is still early, contributors are welcome at rbitcoin.org, and listeners should treat alt clients as high-scrutiny infrastructure — not a drop-in replacement for Core tomorrow.
Timestamps:
00:00 — Intro: Brandon Black & rbitcoin
00:34 — Why Build rbitcoin
03:46 — Alt Clients Mini-Series
04:39 — Consensus Divergence Risk
05:53 — satd vs rbitcoin Paths
06:51 — Automation Makes Diversity Possible
08:29 — Build-Time Differential Testing
09:20 — Why Consensus Bugs Matter
10:55 — Lessons from btcd Divergences
13:35 — Target User: Wallet Backends
15:29 — Miners Leave the Non-Goal List
16:47 — Kill the dbcache Model
20:50 — Electrum In-Process
22:23 — Silent Payments & Tor
23:01 — BIP324 v2-Only P2P
23:46 — AI-Coded: Zero Human Lines
25:04 — Grok Plus Multi-Model Review
27:01 — DoS Rules & LibreRelay
28:34 — Upgrade Hooks
29:34 — Archive-Only, No 'UTXO Set'
31:50 — AI as the New Compiler
33:52 — Context Limits & Dependencies
38:06 — rust-bitcoin Relationship
39:08 — Wallet Infra Opportunity
40:00 — Still 10% a Joke
41:35 — Future of Client Diversity
44:50 — Outro: rbitcoin.org
Links: 
https://x.com/reardencode

https://rbitcoin.org/

Stephan Livera links:
Follow me on X: @stephanlivera

Subscribe to the podcast

Subscribe to Substack