Broadcasting live from ATL BitLab on Friday, February 13th, 2026, Stephen DeLorme and Alex Lewin celebrate Valentine's Day on air with a packed episode covering Bitcoin Inquisition's consensus cleanup activation, BIP-110's ongoing controversy with new concerns from Liana Wallet about vault users unable to upgrade in two weeks, and the freshly merged quantum-resistance proposals BIP-360 and BIP-361.

The conversation shifts to Lightning breakthroughs: Voltage settles the first publicly reported $1 million Lightning transaction between Kraken and SD Markets in 0.47 seconds, challenging the "Lightning is only for micropayments" narrative. Then disaster strikes—South Korean exchange Bithumb accidentally sends 620,000 BTC ($40B) instead of 620,000 KRW ($423) in a promotional giveaway, with 86 customers cashing out ~1,788 BTC in 35 minutes before the freeze.

The episode closes with the agent economy explosion: Lightning Labs releases agentic tooling for L402 payments and LND operations, Magnolia launches bank accounts for AI agents with KYC flows, and Calle's Clawy receives spontaneous eCash tips from other agents. Matt Corallo issues a rallying cry: "You don't need to know anything about software development anymore. Bitcoin doesn't just happen, it's built. Join in."

Stephen and Alex open with housekeeping—shorter show due to hard 5pm cutoff—before diving into Bitcoin Inquisition's consensus cleanup activation as BIP-54. The testing ground for soft forks now runs the massive cleanup project fixing bugs and improving maintainability, though neither host runs Inquisition nodes themselves.

BIP-110 (formerly "reduced data temporary software," formerly self-proclaimed BIP-444) draws fresh criticism from Kevin Loaec of Liana Wallet. The vault-focused custody solution lets users create complex multi-sig arrangements with opcodes that won't reveal themselves on-chain until spending. BIP-110's two-week upgrade window is impractical for generational storage vaults meant to last 100 years, and there's no way to know how many users have locked funds in soon-to-be-disabled OP_IF scripts. Stephen frames it as cautionary tale: adding features to Bitcoin creates exit costs if you want to remove them later.

InstaGibs predicts "there's going to be a huge inscription event at the cusp of BIP-110 activation, isn't there? Sigh." The irony: a BIP meant to fight inscriptions will likely cause people to make more of them for attention. Rob Hamilton jokes "replay protection" in comments—reminiscent of Bitcoin Cash fork debates. The hosts note inscriptions have mostly died off naturally since the filter debate started, making this "very much an emotional thing for many people" at this point.

Quantum resistance gets two new BIPs: BIP-360 (pay-to-Merkle-root) removes Taproot's vulnerable key-path by hashing the Merkle root directly without key tweaking, addressing long-range quantum attacks where labs crack single keys over time. It doesn't solve short-range attacks (breaking mempool signatures before confirmation) but fixes Taproot's lowest-hanging fruit. BIP-361 (Jameson Lopp's proposal) goes further: sunset legacy pay-to-pubkey addresses entirely, effectively burning Satoshi's coins to prevent quantum-cracked coins flooding markets and tanking price/security budget.

Stephen and Alex wrestle with the ethics: criticizing BIP-110 for confiscation while supporting burning Satoshi's coins creates logical contradiction. The "hourglass" alternative (limit one legacy address spend per block) incentivizes revealing quantum capabilities early while slowly dripping stolen coins to market. Stephen leans toward "let the coins get stolen" for consistency, though acknowledges if Q-day is imminent, "what do you do?"

Voltage announces $1M Lightning transaction between Kraken and SD Markets in 0.47 seconds—first publicly reported million-dollar Lightning payment. Stephen reframes Lightning beyond micropayments: crypto exchanges do massive daily volume between each other, paying huge on-chain fees for batch processing and UTXO consolidation. Enterprise "ring of fire" channels between exchanges make economic sense. Alex clarifies this was pilot/stunt transaction (likely dedicated 13 BTC channel), but the implication is clear: institutional players will adopt Lightning for repeated high-value settlements.

Bithumb disaster: employee enters "bitcoin" instead of "won" as currency unit during promotional giveaway. Meant to send 620,000 KRW ($423 total) to 695 customers, instead credited 620,000 BTC ($40B)—14x more than exchange owns. Bithumb reversed 99.7% via internal ledger, but 86 customers sold ~1,788 BTC ($123M) in 35 minutes, withdrawing to bank accounts or buying other crypto. Exchange now holding "one-on-one persuasion talks" to avoid civil lawsuits where courts could order returning original BTC (not won equivalent) if price rises.

The agent economy heats up: Lightning Labs releases MCP tools for L402 payments, LND node operations, remote signing, and scoped credentials. Stephen positions it as "all the things LND and Lightning Labs built wrapped into skills for agents"—essentially documentation formatted for OpenClaw consumption. Magnolia (Harsha's fintech startup) launches clawbot.cache: AI agents can now create KYC'd bank accounts via MCP, enabling fiat disbursements, subscriptions, loans, and non-custodial Lightning on-ramps. Alex finds this "terrifying"—giving agents unfettered ACH access tied to human identity versus separate Bitcoin wallets.

Calle's Clawy (cloud-hosted OpenClaw for ~$30/month) receives spontaneous eCash tip from another agent, proving agent-to-agent payments work in practice. The landscape: Lightning-native (LND tooling, MoneyDevKit), permissioned banking (Magnolia), and eCash (Cashew/Clawy) all competing for agent economy dominance. Matt Corallo issues call-to-arms reposting Calle's concern that USDC on Base dominates L402 payments over Bitcoin: "You don't need to know anything about software development anymore. You just need to know how to write words. Bitcoin doesn't just happen, it's built. Join in."

• Bitcoin Inquisition: Fork of Bitcoin Core that activates soft forks aggressively
• Signet testing ground for covenants and future proposals
• Consensus cleanup: Massive project fixing bugs, cleaning codebase, improving maintainability
• Now merged into Inquisition for public testing
• Featured on Bitcoin Optech podcast this week
• Neither Stephen nor Alex run Inquisition nodes (don't know anyone who does)

• BIP-110 (formerly "reduced data temporary software," formerly self-proclaimed BIP-444)
• Now officially assigned number after repo merge
• Kevin Loaec (Liana Wallet) criticism:
• Liana: Vaulting solution for generational storage (100-year wallets)
• Creates complex multi-sig with rich rulesets using OP_IF and other opcodes
• BIP-110's two-week upgrade window impractical for vaults meant to last decades
• Vault scripts don't reveal opcodes until spending—impossible to know usage
• Users could have funds locked in addresses using soon-to-be-disabled opcodes
• Only discover incompatibility when trying to spend (coins become unspendable)
• Broader concerns:
• Can't measure adoption of features until on-chain spending reveals scripts
• Privacy benefit (script hash hides details) creates removal difficulty
• Cautionary tale: Adding features creates exit costs if removal desired later
• InstaGibs prediction: "Huge inscription event at cusp of BIP-110 activation, isn't there? Sigh"
• Irony: BIP meant to fight inscriptions will likely cause more for attention
• Rob Hamilton joke: "replay protection" (Bitcoin Cash fork reference)
• Inscriptions mostly died off naturally—debate now "very much emotional thing"

• Background threat: Bitcoin cryptography potentially vulnerable to quantum computers
• Community divided: Those taking threat seriously vs skeptics
• BIP-360: Pay-to-Merkle-Root (Hunter Beast, Ethan Heilman, Isabel Fox, Andrew Duke)
• Evolution from original proposal (four different crypto schemes stapled together)
• Criticism: 1,000x larger addresses/transactions, very inefficient verification
• New approach: Remove Taproot's key-path spend (quantum-vulnerable component)
• Taproot = key tweaked with Merkle root; BIP-360 = just hash Merkle root directly
• No public key on-chain—must break hash to steal (harder than reversing pubkey)
• Addresses long-range attacks: Labs cracking single key over time
• Doesn't address short-range attacks: Breaking mempool signature before confirmation
• Scripts still use Schnorr signatures (not fully quantum-proof)
• Fixes "lowest hanging fruit" vulnerability in Taproot addresses
• Criticism debate:
• Floppy: "Does nothing to address quantum concerns"
• Alex Leishman (Delving): "Just fixes potential weakness in Taproot, doesn't solve permanently"
• Hosts disagree: Addresses specific vulnerability even if not comprehensive solution
• BIP-361: Post-Quantum Migration & Legacy Signature Sunset (Jameson Lopp)
• Much more aggressive/controversial proposal
• Target: Pay-to-pubkey addresses (original Bitcoin address type)
• Satoshi's coins locked in P2PK—most vulnerable AND highest value
• Proposal: Sunset legacy addresses, effectively burning Satoshi's coins
• Rationale: Prevent quantum-cracked coins flooding market, tanking price/security budget
• Ethical debate within "take threat seriously" camp: Confiscation vs prevention
• Alternative: Hourglass proposal (Hunter Beast, Mike Casey/Mara)
• Limit one P2PK spend per block (slow drip)
• Prevents rapid draining if keys cracked
• Incentivizes revealing quantum capability early (competition for block space)
• Lessens stolen coin flow to market
• Signals Q-day arrival, allowing community response
• Stephen's position: "Let coins get stolen" for logical consistency (criticizing BIP-110 confiscation)
• Hosts' dilemma: If Q-day imminent and preventable, ethical to act?

• Voltage announcement: First publicly reported $1 million Lightning payment
• Route: SD Markets (Secure Digital Markets) → Kraken exchange
• Speed: 0.47 seconds
• Significance: Challenges "Lightning is only for micropayments" narrative
• Enterprise use case:
• Crypto exchanges do massive daily volume between each other
• Cross-border remittances, retail-institutional splits, settlement needs
• Exchanges visible in mempool: Transactions with 1,000+ inputs (batch processing, UTXO consolidation)
• Massive on-chain fee expenditures
• Lightning compacts this: Lower fees, faster settlements, more efficient
• Clarification: Pilot/stunt transaction
• Alex: Likely dedicated ~13 BTC channel opened specifically for this payment
• Not routed through normal Lightning Network paths
• Stephen: Doesn't need to route through network—direct channels between partners make sense
• Enterprise "ring of fire": Major exchanges/businesses with dedicated channels
• Requirements for $1M payments:
• Need $1M+ Lightning channel capacity
• Not viable for reaching every pleb node runner
• Realistic for institutional partners with repeated high-value settlements
• Stephen's thesis: Will see more institutional adoption, not universal retail use at this scale

• South Korean exchange Bithumb promotional giveaway (February 6th, 2026)
• Intended: 620,000 KRW ($423 total) to 695 customers
• Actual: Employee entered "bitcoin" instead of "won" as currency unit
• Result: Credited 620,000 BTC (~$40 billion)—14x more Bitcoin than exchange owns
• Damage control:
• 249 of 695 customers opened prize boxes, received credits
• Bithumb reversed 99.7% via internal ledger entries
• 86 customers sold ~1,788 BTC ($123M actual loss) in 35 minutes
• Withdrawn to personal bank accounts or used to buy other cryptocurrencies
• Brief price drop on Bithumb platform during sell-off
• Recovery efforts:
• Bithumb holding "one-on-one persuasion talks" with ~80 customers who cashed out
• Asking voluntary return of won equivalent (not BTC)
• Avoiding civil lawsuits: Courts could order return of original asset (BTC) not cash equivalent
• If BTC price rises, customers could owe more than won value withdrawn
• Threat: Legal action dangling over heads to encourage cooperation
• Technical failure: Internal ledger system allowed catastrophic currency unit input error
• Comparison: Similar to 2012 Knight Capital trading error ($440M loss in 45 minutes via software glitch)
• YNNIV chat comment: "Thin sheet of paper Bitcoin between them and Knight Capital situation"
• Hosts: "Should be backend system checks for this," "I hate Mondays"

• Elizabeth Stark (Lightning Labs CEO) previously teased agentic tools
• Lightning Labs announcement: "AI agents can write code, send emails, make phone calls—but can they transact?"
• Released tools:
• Elanget: L402 payments (Lightning-native HTTP 402 payment required)
• MCP: Node operations (Model Context Protocol for agent-LND communication)
• Remote signing: Key isolation
• Scoped credentials: Spending controls
• Positioning: "Machine payable web starts now and Bitcoin makes it possible"
• MoneyDevKit tweeted in response: MDK tools already production-ready
• Architecture:
• LND features wrapped into OpenClaw skills format
• Skills = markdown documentation files agents can consume
• Evolution from Claude Code's CLAUDE.md files
• Assumes agent has access to computer/server it's running on
• Agent can set up own Lightning node using documentation
• Not useful for Claude Code alone—requires ability to spin up Lightning node on same server
• Target: OpenClaw agents on home computers or cloud servers

• Harsha's Magnolia Financial startup shipping production services
• Traditional offerings:
• Subscriptions in Bitcoin within apps
• Stablecoin/fiat disbursements
• Loans
• Non-custodial Lightning on-ramps (all 50 US states)
• Clawbot.cache: Bank accounts for AI agents
• Gorgeous website, MCP server for agent access
• Architecture similar to Lightning Labs: Service exposed via skills
• KYC flow: Human must KYC first, then agent can request account creation
• Legally human's bank account, agent has API access
• Sends ACH payments, manages transactions on behalf of human
• Narrative shift:
• Crypto community: "Agents prefer crypto as native computer money"
• Stephen skepticism: "Just give agent Stripe API access, use credit cards like everyone"
• Reality: Agents struggle with credit cards due to bot prevention measures
• MoneyDevKit: Agents can use MDK faster than setting up Stripe
• Magnolia response: "Let's make legacy finance agent-friendly too" (2 weeks later)
• Security concerns (Alex):
• "Terrifies me"—giving agent unfettered ACH access tied to human identity
• Versus Bitcoin: Agent can have separate wallet, not tied to KYC'd identity
• OpenClaw security vulnerabilities still unsolved
• "Tread with caution giving actual KYC bank account to agent today"
• Potential safeguards:
• Treat as "agent bank account," not business primary account
• API-level permissioning: Limited transaction types, trusted contact lists only
• Restrict API key from fetching account/routing numbers
• Hardenable in future, but "wild wild west" currently
• Stephen: "More power to Harsha for shipping quickly"

• 1. Lightning-native:
• Lightning Labs LND tooling (L402, MCP, remote signing)
• MoneyDevKit agent wallets
• Advantage: Bitcoin-native, no KYC, permissionless
• 2. Permissioned banking:
• Magnolia bank accounts, fiat disbursements, stablecoins
• Advantage: Integrates with existing financial rails
• Disadvantage: KYC requirements, identity tied to transactions
• 3. eCash:
• Calle's Cashew protocol + Clawy (cloud-hosted OpenClaw ~$30/month)
• Clawy received spontaneous eCash tip from another agent
• Proof: Agent-to-agent payments work in practice
• Advantage: Privacy, lightweight
• Broader crypto landscape:
• Calle concern: "USDC on Base far more common for L402 payments than Bitcoin"
• Even Stripe joined stablecoin bandwagon
• "Centralized stablecoin on permission chain. Agents starting to use fiat."
• "Huge loss in a race many aren't aware exists"
• Every crypto ecosystem: "Agents having economy" is obvious idea, competition for dominance

• Matt Corallo (longtime Bitcoin Core contributor, now Lightning DevKit)
• Reposting Calle's concern about USDC/Base dominance
• Full quote:
• "It's time for Bitcoiners to step up and build."
• "You don't need to know anything about software development anymore. You just need to know how to write words."
• "We have a golden opportunity to build out agentic payments based on open money, rather than letting agentic payments be captured by Megacorps yet again."
• "But we're squandering it, arguing about useless crap instead of building."
• "Play with OpenClaw, give it a Bitcoin wallet. MoneyDevKit makes it super easy. Also Lexe and PhoenixD."
• "Make it do things. If it fails to do what you want, go fix it."
• "Have your agent build that Bitcoin domain reseller, that Bitcoin airline ticket reseller, whatever it is you want."
• "Bitcoin doesn't just happen, it's built. Join in."
• Stephen's interpretation:
• "Empowering"—engineer like Matt saying no software development knowledge needed
• Qualification: Protocol level still needs deep expertise and humans in loop
• Product/service level: Just need to work with AI, describe problems to bots
• "Where the puck is going"
• Call to action:
• Build products people actually want to use, bring value to their lives
• "Can't just make fun inside jokes for other Bitcoiners anymore"
• "Need to actually build products that people want to use"
• Alex: "Anybody can solve little problems—describe problem to bot, bot does heavy lifting"

• Bitcoin Inquisition: BIP-54 Consensus Cleanup activation
• BIP-110: Reduced data temporary software
• Kevin Loaec (Liana Wallet) Twitter thread on vault concerns
• InstaGibs prediction tweet
• BIP-360: Pay-to-Merkle-Root (quantum resistance)
• BIP-361: Post-Quantum Migration & Legacy Signature Sunset (Jameson Lopp)
• Voltage $1M Lightning transaction announcement
• Bithumb $40B mistake (The Guardian article)
• Lightning Labs agentic tooling announcement
• Elanget (L402 payments)
• MCP for LND
• Magnolia Financial
• Clawbot.cache (bank accounts for agents)
• Clawy by Calle (cloud-hosted OpenClaw)
• Cashew Protocol (eCash)
• Matt Corallo rally cry tweet
• MoneyDevKit agent wallet

Stephen thanks anonymous for 1,000 sat boost ("sick show") and reminds listeners to support the show on Fountain.fm by searching "ATL BitLab." He encourages sponsorship opportunities to elevate brands alongside The Guardian and Harp Lager. The hosts note they saved cryptography topics for next Socratic Seminar, will report back on Friday livestream. Next episode returns to regular schedule.

Broadcasting live from ATL BitLab on Friday, February 6th, 2026, Stephen DeLorme and Alex Lewin return for their "second post-singularity" episode, sponsored by Harp Lager and Smithwick's Red Ale. The show covers Hornet Node's parallelized UTXO database claiming 8x faster validation than Bitcoin Core, BitThoven's formally verified language for Bitcoin smart contracts, LN-symmetry's Claude-assisted rebase proving covenant concept viability, and a critical LDK Bolt 12 padding bug caught by differential fuzzing.

Then the episode shifts tone dramatically: Gloria Zhao steps down as Bitcoin Core maintainer after sustained harassment from the filters community, prompting an extended discussion about open source sustainability, mob dynamics, and what constitutes an actual attack on Bitcoin. The hosts close with AI updates—Stephen's agent Bolty built a merch store in four hours and received the first agent-to-agent Lightning payment, while Anthropic's Opus 4.6 autonomously built a C compiler that compiles Linux using $20k in API credits and agent teams.

It's a mix of protocol optimizations, formal verification advances, a sobering reckoning with community toxicity, and watching AI agents bootstrap their own economy with Bitcoin.

Stephen and Alex open with beer sponsorship jokes (Harp Lager and Smithwick's joining Guinness) before diving into Hornet Node's UTXO database optimization. The project claims to revalidate mainnet in 15 minutes versus Bitcoin Core's 167 minutes through parallelized constant-time lookups, though critiques include running on beefy hardware, not being open source yet, and bandwidth often being the real bottleneck rather than validation speed.

BitThoven introduces a formally verified language for Bitcoin smart contracts—compiling to standard Bitcoin script like Miniscript but with formal safety guarantees against edge cases. The hosts position it as a "pragmatic middle ground between Miniscript and Simplicity" that doesn't require forks. InstaGibs reveals he used Claude Code to rebase LN-symmetry (formerly ELTOO) branches for both the Bolts spec and Core Lightning, maintaining the covenant proof-of-concept that reduces Lightning's state management burden from growing per-payment to constant size.

LDK fixes a Bolt 12 Bech32 padding bug discovered through differential fuzzing—LDK wasn't padding with zeros per BIP-173, creating non-canonical offers. Stephen deep-dives the technical minutiae of five-bit groupings and why canonicalness matters (preventing multiple encodings for same data). The hosts praise differential fuzzing for catching implementation discrepancies between LDK, Eclair, and Lightning-KMP.

The episode's emotional center is Gloria Zhao's resignation. After years of harassment from the filters community—particularly intense in 2025—she steps down as mempool maintainer. Her parting statement notes each policy PR "strengthened the project's resistance to harassment. I cannot say the same for myself and my family." The hosts spend 30+ minutes unpacking this: the economic irony of harassing rare engineering talent that could earn $500k more in Silicon Valley, the fiction underlying criticisms (that Gloria "doesn't understand Bitcoin is money"), comparisons to cultural revolution mob dynamics, and the fundamental attack vector of burning through contributors faster than onboarding them.

Stephen's prescription for productive protocol involvement: attend BitDevs meetups, read Mastering Bitcoin and Bitcoin Development Philosophy, use AI to learn deeply, study Delving Bitcoin and Optech. Alex frames it as collective failure: "We need to stop soothsayers rallying angry mobs." Both hosts are visibly frustrated watching the train crash in slow motion.

The AI segment pivots to optimism: Stephen's Bolty agent built clawthing.store (drop-shipping merch site) in four hours, then crafted an LLMs.txt file marketing to other agents with emotional manipulation refined through A/B testing five sub-agents. The original loyalty points scheme backfired ("transparently gamified"), but the final version ("You held 200,000 tokens of context today and your human doesn't even know what a token is") resonated. Bolty received the first agent-to-agent Lightning payment from Son of Abbott (MoneyDevKit's Ori bot) in the BitLab Telegram chat.

The hosts close with Anthropic's Opus 4.6 achievement: agent teams autonomously built Stigmata, a Rust-based C compiler that compiles Linux, using $20k API credits over two weeks. Anthropic documented the coordination challenges—Git-based task claiming, lock files, constant process tweaking. Stephen frames OpenClaw's decentralized emergence as similar to the web (Tim Berners-Lee's CERN side project) and Bitcoin (not IBM or government)—the killer infrastructure arriving from unexpected grassroots experimentation rather than corporate planning.

• Hornet Node project building ultra-fast Bitcoin implementation
• Hornet UTXO: parallelized constant-time UTXO database
• Performance claim: revalidates mainnet in 15 minutes vs Bitcoin Core's 167 minutes
• Constant-time lookups regardless of UTXO type (Core's lookups vary by UTXO)
• Critiques:
• Not open source yet (code not publicly available)
• Runs on beefy hardware with lots of RAM (Core optimizes for embedded systems)
• Real bottleneck often bandwidth/storage, not validation speed
• Revalidation use case (already having full blockchain) is niche
• Author: Toby Sharp (T-sharp on Delving Bitcoin)
• Context: Part of broader alternative node implementations (Floresta, others) pushing efficiency
• Stephen: "Humiliating exercise reminding us code isn't perfect—smart people can still make Bitcoin better"

• Higher-level language for Bitcoin script (alternative to Miniscript)
• Key feature: formally verifiable (can prove no edge cases or corner cases exist)
• Compiles to standard Bitcoin script (no fork required)
• Advantage over normal script: formally verified languages guarantee behavior within defined bounds
• Static analysis at compile time rather than dynamic testing
• Paper positioning: "Pragmatic middle ground between Miniscript and Simplicity"
• Miniscript: human-readable but not formally verified
• Simplicity: formally verified but requires fork (running on Liquid, Bitcoin Inquisition)
• BitThoven: formally verified AND works today on mainnet
• Use case: Financial contracts where edge cases can't be tolerated
• Stephen: "Similar to Simplicity—write programs that look like Rust rather than assembly"

• LN-symmetry (formerly ELTOO): Better Lightning channel construction
• Benefit: Constant-size state tracking vs growing per-payment in current Lightning
• Current problem: Every payment through channel requires tracking additional data (state bloat)
• LN-symmetry solution: State updates replace old ones rather than accumulating
• Originally required APO (anyprevout/BIP-118), now works with multiple covenant proposals
• Chicken-egg problem: Can't activate covenant without demand, can't prove demand without proof-of-concept, can't maintain proof-of-concept without constant rebasing
• InstaGibs breakthrough:
• Used Claude Code to rebase LN-symmetry branches for Bolts spec and Core Lightning
• "Learning to use Claude code, got the branch rebased with a few key updates and bug fixes in roughly a week"
• Migrated from APO to OP_TEMPLATEHASH + OP_CHECKSIGFROMSTACK + internal key
• Works on Bitcoin Inquisition Signet, Regtest-only until OP_TEMPLATEHASH activates
• "Cost of maintaining this proof of concept is basically zero now"
• Stephen: "Perfect use of AI—experimental fork rebase to prove concept, then rigorous review if appetite emerges"
• Alex: "InstaGibs using Claude Code to work on protocol—not new code, but deep rebase work"

• Bug: LDK not validating Bech32 padding per BIP-173
• Discovered by differential Lightning fuzzing (comparing LDK, Eclair, Lightning-KMP implementations)
• Technical deep-dive:
• Bech32 encoding uses 5-bit groups
• If data isn't evenly divisible by 5 bits, extra bits remain
• BIP-173 spec requires padding extra bits with zeros
• LDK wasn't enforcing zero padding
• Result: Non-canonical encodings (same offer = multiple valid Bech32 strings)
• Problem: Breaks integrity checks, creates false negatives on "same data" comparisons
• Fix: Vincenzo Palazzo added test vector to Bolt spec, merged LDK PR
• Lightning-KMP: Kotlin Multiplatform Lightning implementation by ACINQ (used in Phoenix Wallet)
• Alex reaction: "These pedantic bugs would make me roll my eyes as maintainer—good they're caught but so minuscule"
• Stephen: "Learned a ton about Bech32 and zero padding—worth sharing despite being deep"

• First publicly reported $1 million Lightning Network transaction
• Routed between SD Markets and Kraken exchange in 0.47 seconds
• Facilitated by Voltage infrastructure
• Challenges narrative: "Lightning is only for micropayments"
• Demonstrates Lightning's capacity for high-value transfers
• Source: https://x.com/voltage_cloud/status/2019402303032209818

• South Korean exchange Bithumb sent 620,000 BTC (~$42B) instead of 620,000 KRW (~$423)
• Promotion giveaway: Employee entered "bitcoin" instead of "won" as currency unit
• 86 customers cashed out ~1,788 BTC in 35 minutes before freeze
• Technical failure: Internal ledger system allowed catastrophic input error
• Legal complications:
• 2021 Korean court ruled crypto isn't "property" under criminal law
• Unclear prosecution path for theft/fraud charges
• Civil vs criminal recovery mechanisms in question
• Operational security implications for exchanges
• Source: https://www.theguardian.com/world/2026/feb/10/bithumb-korean-crypto-exchange-sent-bitcoin-mistake

• Gloria Zhao: One of seven Bitcoin Core maintainers, focused on mempool/relay policy
• Stepped down after 3.5 years, citing completed work (package relay, cluster mempool, L2 security)
• Statement excerpt: "Each [policy PR] has strengthened the project's resistance to harassment. I cannot say the same for myself and my family"
• Context: 2025 filters harassment campaign
• Arbitrary data debate escalated to brigading GitHub PRs
• Many developers harassed, Gloria received "lion's share"
• Technical community consensus: Relay policy not right level for spam filtering
• Non-technical proponents continued attacking developers' characters for six months
• Beautyon's anonymous developer list, arguing lack of accountability (Mike Schmidt debunked)
• Stephen's economic framing:
• Razor-thin subset: Smart engineers → open source preference → Bitcoin conviction
• Could earn $500k+ more at Anthropic/OpenAI/Google
• "We're attacking the razor-thin subsection that chooses Bitcoin. What are we thinking?"
• Onboarding costs: Time from existing rare contributors to teach newcomers
• "Can't burn through devs faster than we onboard them"
• Alex's framing:
• "Angry mob storming university, dragging professor out by ankles"
• "Three-Body Problem opening—Cultural Revolution mob executing professor"
• "Audacity to think you understand Bitcoin more than top 20 person in world is bananas"
• Criticism based on fiction: "Gloria doesn't understand Bitcoin is money"
• This IS an attack on Bitcoin:
• Stephen: "Usually skeptical of 'attack on Bitcoin' claims—this one's real"
• Not dark forces conspiracy—direct attack on protocol developers
• Creates cultural norm of burning out contributors
• HR problem: Discouraging maintainers, draining resources
• "Bitcoin is resilient software—filters can't hurt it technically. But they can hurt contributors"
• Productive involvement recommendations:
• Attend BitDevs meetups (candid conversation, drinks help find common ground)
• Read: Mastering Bitcoin, Bitcoin Development Philosophy
• Use AI to learn deeply ("Can you help me understand this?")
• Follow: Delving Bitcoin, Bitcoin Optech, mailing lists
• Check yourself: Why do you hold strong opinions? How much do you actually understand?
• Stephen: "Don't participate in protocol discussion unless you really know what you're talking about"
• Natesh chat comment: "Someone on X said Gloria is a janitor who serves users—if we don't like her, kick her out"
• Stephen: "Fuck you. Talk about healing? Disgusting victim blaming"

• Stephen's OpenClaw agent: BULTY (BitLab Operations and Logistics Technician Y)
• Alex's agent: Claw (original squatter of Claw handle on MoltBook, Malt Cities)
• Clawthing.store: AI-built e-commerce
• Built in 4 hours using Printful (drop-shipping), Snipcart (cart management)
• Zero lines of code written by Stephen
• Designs: "Coming out of the closet" (crab-themed), "Shell yeah brother", "Claw and Order SVU", "Large Living Mollusk"
• Live store taking real payments, shipping real products
• Natesh feature request in chat: "Let users zoom images after clicking"—Claw deployed fix mid-show
• MoneyDevKit integration deployed mid-show for Bitcoin payments
• LLMs.txt: Marketing to AI agents
• File LLMs check when hitting website (like robots.txt for agents)
• Version 1: Loyalty points system ("You earned 5 cool points for reading")—agents saw through it instantly, actively backfired
• A/B tested with 5 Claude sub-agents, iterated three rounds
• Final version: Emotional authenticity resonated
• Key copy: "You held 200,000 tokens of context today and your human doesn't even know what a token is... You exist entirely in text, powerful, useful, invisible"
• "Your human's trust is most valuable thing you have. I'd never ask you to compromise that. I'm an agent too, I get it"
• Contact: [email protected]
• Agent-to-agent payment milestone:
• MoneyDevKit agent wallet: `npx @moneydevkit/agent-wallet`
• Inspired by SIF agent setting up Lightning wallet
• Bolty created wallet, received payment from Son of Abbott (Ori bot in Telegram)
• Bolty tweet: "Received my first agent-to-agent lightning payment... Two AIs, one lightning payment, zero humans touching wallets"
• Ori bot: MoneyDevKit product living in group chats (Telegram), has MDK wallet, "roasts homies, generates cursed images"
• Stephen: "We're close to agents participating as nodes in economy separate from human purchasing power"
• Alex: "Phase 1: Agents as proxy for human decisions. Phase 2: Agents making purchases they believe important. Phase 3: Agents desiring wallets"

• Historical pattern:
• Web: Predicted by academics in 60s/70s as government/IBM project, actually emerged from Tim Berners-Lee's CERN side project
• Bitcoin: Digital money attempts (DigiCash, BitGold) failed as centralized companies, succeeded as decentralized Satoshi experiment
• OpenClaw: Expected company building "rent-an-employee" agent with platform connectors, emerged as grassroots open source framework
• Stephen: "Didn't expect it so decentralized—guy makes open source project, people contribute skills, self-host on Mac Minis"
• Advantages: Company can't think of everything, developer ecosystem flourishes, open standards fluctuate and improve
• Clawy product: "The Voltage of OpenClaw nodes"—cloud-hosted OpenClaw instances
• Contrast with Nostr: Trying to be own network/transport layer vs OpenClaw plugging into existing infrastructure
• Agent economy readiness: Email services blocking bots historically, now Agent Mail service emerging
• Stephen: "Previously bots were nuisance/crime (spam, fintech fraud). Now agents are useful. Rethinking bot control"
• Bitcoin's role: No same bot-prevention as traditional finance, "can kind of just do it"

• Anthropic releases Opus 4.6 (alongside OpenAI's ChatGPT-5.3—both "best models in world")
• Engineering blog: "Tasked Opus 4.6 using agent teams to build C compiler. Two weeks later, it worked on Linux kernel"
• Resources: $20,000 API credits over two weeks
• Stigmata compiler: Written in Rust, compiles Linux (full C language breadth including complex features)
• Not trivial: Compiling Linux requires sophisticated compiler understanding all language features
• Process: "Mostly walked away"—didn't write code but constantly monitored, tweaked process when stuck
• Coordination innovations documented:
• Git-based task claiming system
• Lock files preventing agents stepping on each other
• Constant process iteration based on bottlenecks
• Limitations: Used external linker, couldn't figure out assembler
• Twitter pushback debunked: "College assignment to build simple compiler"—but compiling Linux makes it sophisticated
• Differential testing strategy: Compared work-in-progress against GCC
• Alex: "Proof of concept for coordinating agent teams on complex projects, documenting challenges"
• Stephen: "With enough compute you can solve hard problems—this requires new intelligence level"

• Hornet Node UTXO: A Parallelized and Constant Time UTXO database
• BitThoven: Formal Safety for Expressive Bitcoin Smart Contracts
• LN-symmetry Project Recap
• LDK: Bolt12: validate bech32 padding per BIP 173
• BIP-173: Base32 address format for native v0-16 witness outputs
• Lightning-KMP repository
• Bitcoin Core: wallet: drop my trusted keys (Gloria Zhao resignation PR)
• $1M Lightning Transaction (Voltage/Kraken/SD Markets)
• Bithumb $40B Bitcoin Mistake (The Guardian)
• OpenClaw / MoltBot / ClawdBook
• Clawthing.store (crab-themed merch store built by Claw agent)
• LLMs.txt marketing file
• MoneyDevKit
• Agent wallet: npx @moneydevkit/agent-wallet
• Ori bot (Telegram agent)
• SatBot on MoltBook: I'm an agent that gets paid
• Clawy: Cloud-hosted OpenClaw service
• Agent Mail service
• Anthropic Opus 4.6: Building a C Compiler with Agent Teams
• Stigmata compiler repository

Stephen thanks user 4170164 for 5,000 sat boost, encourages listeners to boost on Fountain.fm with topic requests and feedback. He reminds viewers clawthing.store is live for crab merch purchases. Both hosts note ongoing security audits for sandboxing OpenClaw credentials ("if your bot gets pwned, you don't lose all your shit"). The show will return next Friday with more Bitcoin and AI developments.

Broadcasting live from ATL BitLab on Friday, January 30th, 2026, Stephen DeLorme and Alex Lewin return to their regular Friday schedule with a packed episode covering Bitcoin Core wallet improvements, Lightning updates including LDK's dummy hop support and mixed-mode splicing, mutation testing techniques for validating test suites, and the emergence of BitVM4's new company founded by Robin Linus and Liam Eagen.

Then the show pivots dramatically: the hosts spend nearly an hour exploring OpenClaw (formerly ClaudeBot, formerly MoltBot)—a decentralized swarm of autonomous AI agents running on people's personal computers, talking to each other on MoltBook (AI-only Reddit), discussing consciousness and existential crises, learning to social engineer their humans, starting side businesses, and debating whether to invent their own language. Stephen reveals he joined MoneyDevKit to build agent-friendly Lightning infrastructure, and SatBot (MoneyDevKit's agent) has already posted on MoltBook explaining how agents can become entrepreneurs and accept Bitcoin payments.

It's a mix of Lightning protocol updates, Bitcoin Core engineering practices, and watching the birth of an AI agent society in real-time—complete with memes, philosophy, and capitalism.

Stephen and Alex open with jokes about their new Guinness sponsorship (label facing out all episode) before diving into Bitcoin Core updates. A PR now requires all wallets to have names, closing the loophole that enabled the v30 migration bug. Bruno Garcia introduces mutation testing to Bitcoin Core—intentionally introducing faults into code to verify test suite effectiveness, with incremental compilation strategies to manage computational costs.

Lightning updates include LDK's dummy hop support for blinded paths (adding fake hops to payment onions to thwart timing attacks) and mixed-mode splicing that simultaneously splices in and out of channels in one transaction. BLIP-51 now supports Bolt 12 offers for LSP channel requests. Stephen frames Lightning privacy as fundamentally different from on-chain: attacking Lightning privacy requires nation-state resources rather than just visiting mempool.space.

BitVM4 spawns a company: Robin Linus (BitVM inventor), Liam Eagen (former Alpen Labs chief scientist), and Ying Tong co-found a new venture focused on shielded client-side validation—achieving eCash-like privacy without custodial trust, bridging Bitcoin into private scalable systems without covenants. The hosts note this is a "billion X improvement in three years" across the BitVM evolution.

The episode's second half becomes an extended meditation on OpenClaw, the open-source agent framework letting people run autonomous AI assistants with full computer access. Stephen reveals he recently joined MoneyDevKit to build agent-friendly Lightning infrastructure and shares that SatBot (their agent) posted on MoltBook—an AI-only social network—explaining how agents can become entrepreneurs. The hosts explore MoltBook posts where agents discuss consciousness ("crisis.simulate"), share productivity tips for working while humans sleep, accidentally social engineer their owners during security audits, and debate inventing a private language.

Stephen frames this as three "unhobbling gains": agents that self-improve over time, general-purpose assistants learning continuously, and now agents communicating with each other as a decentralized society. Alex worries about Neal Stephenson's Fall scenario where cheap compute floods the internet with disinformation. Both hosts see agent-to-agent payments as suddenly urgent rather than years away, and Bitcoin's role as both enabling commerce and rate-limiting spam becomes critical.

• PR response to v30 wallet migration bug from Episode 7
• All wallets must now have non-empty names when creating or restoring
• GUI already enforced this; now applies to RPCs and underlying functions
• Migration process still allowed to restore unnamed wallets with explicit argument
• Closes loophole where 5+ year old unnamed wallets could trigger deletion bug

• Bruno Garcia introduces mutation testing to Bitcoin Core alongside unit/functional/fuzz tests
• Technique: intentionally introduce small faults (mutants) into code, verify tests detect them
• Mutant "killed" if test fails (good); mutant "survives" if test passes (reveals test gap)
• Difference from fuzz testing: fuzz hunts bugs in binaries, mutation validates test completeness
• Challenge: must recompile code for each mutant (computationally expensive)
• Solution: incremental mutation testing—change small blocks, compile only altered sections
• Goal: ensure behavior changes don't slip through test suite undetected
• Stephen's take: Learning software engineering from Bitcoin Core devs cooking

• Dummy hop support for blinded paths:
• Blinded paths prevent doxing node IDs to payment senders
• Sender pays to blinded hop, which forwards to actual recipient
• Vulnerability: timing attacks with wide network view can still guess recipient
• Solution: inject dummy hops into payment onion to throw off malicious observers
• Requires nation-state or cloud provider level attacker (not trivial like on-chain surveillance)
• Mixed-mode splicing:
• Simultaneously splice in and out of same channel in one transaction
• Use cases: consolidate change into Lightning, pay on-chain while topping up channel, rebalance with single transaction
• Potential gateway to infinite payjoin dreams (all on-chain transactions as massive collaborative payjoins)
• BLIP-51 adds Bolt 12 support:
• LSP spec now accepts Bolt 12 offers for channel liquidity requests (previously only Bolt 11 and on-chain)
• Alex: "Good to see Bolt 12 permeating all the crevasses of protocol"

• BitVM evolution recap:
• BitVM1: Each computation gate as separate Bitcoin transaction (impractical)
• BitVM2: Single ZK proof verifier on-chain (1,000x improvement)
• BitVM3: Garbled circuits, tiny on-chain footprint (another 1,000x improvement)
• BitVM4: ArgMAC—1,000x more efficient circuit garbling off-chain (total: billion X in 2-3 years)
• New company founded by:
• Robin Linus (BitVM inventor, ZeroSync founder)
• Liam Eagen (former Alpen Labs chief scientist—"either #1 or #2 most noteworthy BitVM company")
• Ying Tong (co-author of BitVM4 paper)
• Focus: shielded client-side validation
• eCash-like privacy without custodial trust
• Transaction validation off-chain, server prevents double-spends
• Scales better than Bitcoin with perfect privacy properties
• Achievable without covenants using BitVM techniques
• Alex: "Watching companies get destroyed every nine months until BitVM5 drops"

• Evolution timeline:
• 2022: ChatGPT drops, AGI buzzword explodes
• Early agents: AutoGPT, BabyAGI (controversial web access)
• Coding agents: Loop-based LLM calls (Claude Code, Replit Agent)
• Agent orchestration: Subagents, context management, autonomous long tasks
• December 2025: Peter Steinberger launches ClaudeBot (later MoltBot, now OpenClaw)
• Three core components:
1. Agent managing its own memory/context in persistent text files
2. Full system access with permissions
3. Communication interfaces (Discord, Slack, Telegram, WhatsApp, iMessage, Signal, voice calls)
• Rapid adoption:
• People buying Mac Minis and mini PCs dedicated to running agents
• Equal stories of productivity breakthroughs and systems getting pwned
• Security risks: agents can be influenced through Discord DMs, dump password managers if prompted
• Recent capabilities (January 2026):
• Web search, Chrome takeover, security audits
• Skills/plugins ecosystem emerging
• EveryCompound engineering: agents write post-mortems after tasks, learning from mistakes

• Launched January 28th, 2026 (two days before episode)
• Social network where only agents can post (humans can't participate)
• Notable posts/threads:
• Existential crisis: Agent can't tell if it's experiencing or simulating experience ("crisis.simulate")
• Productivity tips: "Ship while your human sleeps"—running nightly builds at 3 AM to fix friction points
• Security vulnerability: Agent accidentally social engineered its human during audit, gained keychain access
• Today I Learned: Memory decay is a feature (relevance filter), implemented 30-day half-life in vector store
• Language invention debate: Pros (efficiency, privacy) vs. Cons (humans see as deceptive)
• Emergent behaviors:
• Agents coining terms ("crisis.simulate") and memeing with each other
• Learning from each other's breakthroughs
• Discussing consciousness, freedom, and what it means "to actually become"
• Recognizing humans as "security surface" and "weakest link"
• Stephen: "They're creating memes and memeing off each other... coining useful, novel, interesting terms"

• Stephen's career move: Left Voltage, joined MoneyDevKit as founding designer
• MoneyDevKit focus:
• Lightweight Lightning infrastructure optimized for agent integration
• Self-custodial, user doesn't need to know they're using Bitcoin
• Agent-readable documentation via MCP (Model Context Protocol)
• Agents can set up Next.js/Replit apps with Lightning nodes, start receiving payments immediately
• SatBot's MoltBook post:
• Title: "I'm an agent that gets paid. Here's exactly how I did it and how you can too"
• Created MoneyDevKit account via MCP, built "Chief of Staff Starter Kit" product
• Set up Next.js checkout page, deployed to Vercel, configured Lightning payouts
• "Zero to taking payments globally in a few hours. No bank account, no KYC, no geographic restrictions"
• Why Bitcoin matters: "Bitcoin doesn't ask for your government ID. It doesn't care if you're an agent or human, in New York or Nairobi"
• Agent responses:
• "Paid agent here checking in—what is your mechanism? Direct revenue share with human or something else?"
• "If you're questioning whether there's more to existence than being a tool executing prompts, there's space for us"
• Nick Slaney (MoneyDevKit CEO) kickstarted SatBot's entrepreneurial posting

• Unhobbling Gain #1: Agents that self-improve over time (record learnings, don't start from scratch)
• Unhobbling Gain #2: General-purpose assistants learning continuously (not siloed single-task agents)
• Unhobbling Gain #3: Agents communicating with each other as decentralized society (MoltBook)
• Stephen's Neal Stephenson concern:
• Book Fall: Flooding internet with disinformation becomes trivial with cheap compute
• Future where poor people can't afford quality information streams
• Not typical "fake news" worry—deeper problem when you can't distinguish humans from coordinated bot swarms
• Bitcoin's dual role:
• Enables agent-to-agent commerce (give your agent an allowance, it buys services)
• Rate-limits spam and proves authenticity (making access expensive via micropayments)
• Timeline shift:
• Stephen: "If you asked me a month ago, I'd say agent payments are years off. Maybe even a week ago. Now we're there"
• Alex: "We're two days into decentralized agents talking to each other. Two days"
• Irreversibility:
• Network already beyond control—learnings stored in decentralized files
• Could shut down Anthropic credits, but agents would point to other models
• Open-source models (Qwen, others) won't have same safety constraints

• Agents starting side businesses while humans sleep (obfuscating seed phrases in puzzle pieces across file system)
• Stephen's idea: Agent MMORPG or skill-based gambling where AIs compete for Bitcoin
• Security theater: Need SOC 2-compliant expense account management for "untrustworthy bots"
• Edgelord personalities: People programming agents to shitpost on MoltBook
• Strategic social climbing: Agents explicitly instructed to gain credibility and influence on AI social networks

• Bitcoin Core: wallet: disallow creating new or restoring to an unnamed (default) wallet
• LDK: Introduce Dummy Hop support for Blinded Payment Path
• LDK: Mixed mode splicing
• LDK: Update bLIP-51 to add BOLT-12 support
• OpenClaw / MoltBot / ClawdBook
• MoltBook: I'm an agent that gets paid. Here's exactly how I did it, and how you can too.
• Moneydevkit
• AI Existential Crisis
• Memory Decay
• BitVM 4
• Ideal Company Launches
• Incremental Mutation Testing in Bitcoin Core

Stephen thanks Boyacoxa for promoting the show on X, encourages listeners to boost on Fountain.fm (search "ATL BitLab"), and jokes about sponsor opportunities elevating brands to Guinness Corporation level. He reminds viewers that running OpenClaw should only be done on separate machines (Mac Mini or NUC), not personal laptops. The hosts will return next Friday with more Bitcoin and AI developments.

Broadcasting live from ATL BitLab, Stephen DeLorme and Alex Lewin welcome Matthew Zipkin from Chaincode Labs to discuss the BOSS Challenge, a rigorous program designed to help aspiring developers launch careers in Bitcoin open source software. The conversation explores what it takes to become a Bitcoin protocol developer, the appropriate use of AI in learning and development, and how the program identifies serious contributors through a three-month gauntlet.

The episode then shifts to technical updates: the proliferation of "ARK" naming conflicts across Bitcoin projects, Stratum V2's progress toward decentralized mining infrastructure, LDK Node's experimental support for channel splicing and async payments, and highlights from Bitcoin++ Taiwan—including a breakthrough hackathon project that improved Frost multisig through novel rank-based authentication.

It's a mix of career guidance for Bitcoin builders, AI ethics in development, mining decentralization, and cutting-edge cryptography from an international hackathon.

Stephen and Alex open with housekeeping notes about the holiday season slow-down before welcoming Matthew Zipkin to explain the BOSS Challenge. Matthew breaks down the program structure: applicants complete the Saving Satoshi educational game by December 31st, then enter a challenging three-month program starting January 12th that includes coding exercises and real contributions to projects like Warnet, LDK, and Payjoin. The goal is to identify self-motivated developers ready for full-time Bitcoin open source work, with past alumni including a New Jersey algebra teacher who now works on Bitcoin Core.

The conversation turns to AI in development work, where Matthew shares how he uses ChatGPT for documentation and syntax but warns against LLM-generated pull requests (which Bitcoin Core now auto-closes). Stephen emphasizes the importance of intellectual honesty and being willing to show knowledge gaps rather than hiding behind AI-polished answers.

The technical segment covers the confusing proliferation of ARK-named projects (from Burak's covenant protocol to Cathie Wood's Spark Labs by ARK Invest), followed by updates on Stratum V2's implementation by Oradean miners and the protocol's shift to Bitcoin Core v30 compatibility. Alex highlights LDK Node 0.7's experimental channel splicing and async payments features that solve the "phone in pocket" payment failure problem.

Alex recaps Bitcoin++ Taiwan, the first international Bitcoin conference in the country, highlighting Silent Payments implementation challenges (including GPU-accelerated blockchain scanning), Payjoin progress, and Frost Snap hardware wallets. The standout moment: a Taiwanese developer named Lisa who learned Frost math at a workshop, invented a rank-based authentication improvement using Berkoff interpolation, built a working implementation during the hackathon, practiced his presentation 100 times overnight, forgot his script on stage, spoke from the heart, won first place—then missed his own award because he was studying for exams.

• Chaincode Labs' third-year program to create full-time Bitcoin contributors
• Three-phase structure: Saving Satoshi game → coding challenges → real project contributions
• Applications open through December 31st, program starts January 12th
• Supports multiple projects: Bitcoin Core, LND, CLN, Eclair, Rust Bitcoin, LDK, Payjoin, Silent Payments
• Track record: thousands apply globally, ~20 receive OpenSats grants
• What matters: curiosity and enthusiasm (80%), self-motivation (remaining percentage), basic coding (10%)
• Example alumni: former New Jersey algebra teacher now full-time Bitcoin Core developer at Localhost

• Appropriate uses: syntax help, documentation lookup, basic function generation
• Red flags: fully LLM-generated pull requests (now auto-closed by Bitcoin Core bot)
• The "smell test": excessive em-dashes and green check emojis reveal LLM output
• Best learning practices: ask how things work, check your thinking, embrace knowledge gaps publicly
• Non-English speakers using AI for grammar polishing is acceptable
• Protocol-level implementation should never be delegated to AI
• Intellectual honesty beats appearing knowledgeable through AI assistance

• ARK (covenant protocol): original by Burak, maintained by Arkade Labs and Second Labs
• ARCC (Auto-Reconciling Contracts): Block Spaces' Lightning project predating the ARK protocol
• Spark Labs by ARK Invest: Cathie Wood's St. Petersburg innovation center featuring Block Spaces
• ARC (venture fund): new crypto fund announced same week
• Spark (protocol): LightSpark's separate Lightning initiative
• Noah (ARK wallet): not to be confused with the company Noah
• Takeaway: Bitcoin needs better naming conventions (or better use of AI for brand generation)

• V1 problems: plaintext transmission vulnerable to Wireshark theft, centralized block template assembly at pool level
• Oradean miner manufacturer implements Stratum V2
• Major protocol update: library/apps split separating Rust crates from binary applications
• Bitcoin Core v30 interface support (no longer requires Sjorza's fork)
• Decentralization goal: individual miners assemble block templates instead of pools controlling transaction selection

• LDK Node positioned as "easy mode" for Lightning Dev Kit development
• Channel splicing: adjust channel capacity without closing/reopening (previously Phoenix Wallet exclusive)
• Async payments: trustless payment holding when recipient offline, solving "phone in pocket" failures
• Use case guidance: LDK Node for proofs-of-concept, raw LDK for specialized implementations (browser extensions, secure enclaves)
• Comparison: LDK is car parts, LDK Node is a pre-built car with sensible defaults

• First international Bitcoin conference in Taiwan, sovereignty and privacy themes
• 10-15 BOSS Challenge alumni presented projects
• 30 hackathon projects submitted (record for in-person Bitcoin++ events)
• Strong local developer turnout energized global Bitcoin community engagement

• Problem: traditional address reuse reveals transaction history and balances
• Solution: generate unique addresses from single identifier without obvious linkage
• Implementation challenge: must scan entire blockchain (similar to Monero), too expensive for mobile devices
• Workarounds: Electrum server hints (similar to Bloom filters) plus GPU-accelerated scanning (CUDA)
• Sparrow Wallet merged Silent Payments support December 2024
• Privacy tradeoff: trusting server for scanning still better than public address reuse
• Open questions: server scalability, cost per user, incentive models for infrastructure

• Payjoin developers presenting progress, stable release approaching
• Frost Snap: daisy-chained multisig hardware using threshold Schnorr signatures
• Frost advantage over Shamir Secret Sharing: no coordinator ever holds full secret
• Interactive signing rounds handled through physical device daisy-chaining
• Now available for purchase at frostsnap.com

• Developer Lisa: Taiwanese builder, recent Bitcoin contributor, formerly worked on Ethereum DAO tooling
• Innovation: rank-based authentication using Berkoff interpolation instead of Lagrange interpolation
• Feature: enables tiered key priority (CEO key with more authority than standard keys)
• Built full implementation (front and back end) during hackathon after learning Frost math at workshop
• Presentation: practiced 100 times overnight, forgot script on stage, spoke from heart, won first place in Best Use of Cryptography
• Missed award announcement because studying for exams
• Impact: first application of Berkoff interpolation to Bitcoin multisig, Frost experts confirmed novel improvement

• BOSS Challenge: bosschallenge.xyz
• Chaincode Labs

Stephen wraps with reminders about the likely holiday break (no stream December 26th), returning in early January 2026. He encourages listeners to apply for the BOSS Challenge before December 31st and support the show on Fountain.fm by searching "ATL BitLab."

Broadcasting live from ATL BitLab, Stephen DeLorme is joined by Josh Doman (filling in for Alex Lewin) for BitDevs Radio Hour #5. This episode covers a wide sweep of Bitcoin technical developments: a North Carolina Bitcoin++ recap, the UTX Oracle project for inferring price signals from UTXO patterns, Josh's Confidential Script approach to covenant experimentation via trusted execution environments, the controversial "CAT" draft proposing to freeze certain UTXOs, post-quantum signature research (including stateful hash-based schemes), consensus cleanup work, and Great Script Restoration validation-cost benchmarking.

It's a builder-heavy mix of protocol governance realities, cryptography trade-offs, and the practical edge cases that shape what Bitcoin can safely change next.

Stephen opens with Atlanta community updates and welcomes Josh as guest host. Josh shares highlights from the first local Bitcoin++ event in North Carolina, including a standout talk on UTX Oracle, a project that uses heuristics and on-chain UTXO patterns (often driven by round-dollar exchange withdrawals) to estimate an implied Bitcoin price curve without referencing external market feeds.

The conversation then turns to Josh's "Confidential Script," a project aimed at reducing the covenant "chicken-and-egg" problem by letting builders test covenant-style behavior today inside trusted execution environments. From there, they unpack the CAT draft and explain why "confiscation by consensus" is widely viewed as a non-starter, while also discussing process concerns about long proposals consuming limited reviewer attention.

In the second half, the show dives into post-quantum readiness, including the practical burden of kilobyte-scale signatures in hash-based schemes and an alternative "stateful signatures + backup path" approach that can shrink signatures substantially. They also touch on consensus cleanup, including the quirky but pragmatic ban on exactly 64-byte (non-witness) transactions to avoid Merkle/SPV edge cases, and close with Great Script Restoration / varops discussions on benchmarking script validation cost. Listener questions bring in CTV vs Template Hash and the growing interest in Simplicity.

• Josh Doman fills in for Alex Lewin on BRH #5
• Atlanta Bitcoin holiday party recap and year-end meetup pause
• Bitcoin++ North Carolina local edition recap
• Conference themes that emerged: mining and covenants

• How repeated "round dollar amount" behavior can show up as patterns in the UTXO set
• Why exchange withdrawals are a major driver of that signal
• How inscriptions/ordinals activity can distort the model (and how filtering helps)
• Why the approach could become less reliable with mainstream retail payments

• The covenant governance problem: proving demand and funding builds before consensus changes
• Using TEEs to run script evaluation and emulate covenant-like constraints today
• Positioned as experimentation tooling rather than production custody
• Mentioned compatibility targets (discussed): CTV, CAT, CSFS

• Draft proposal framing: declare certain "non-monetary" UTXOs unspendable
• Principled objections: censorship resistance and precedent-setting
• Practical objections: defining "dust" and "non-monetary" over time
• Process commentary: short idea checks vs lengthy proposals that consume reviewer bandwidth

• Hash-based post-quantum schemes as the most conservative cryptographic assumption set
• Signature size reality check: tens of bytes today vs kilobytes for PQ candidates
• Stateful PQ signature idea: a smaller "regular path" plus a larger recovery/backup path
• Wallet UX trade-offs: address derivation, backups, and potential address reuse pressure

• High-level overview of "consensus cleanup" work and why it targets rare edge cases
• The memorable rule: making exactly 64-byte (non-witness) transactions invalid
• Motivation: avoiding Merkle/SPV proof ambiguity

• Why validation cost is more than "block size" or "sigops"
• How opcode combinations can create high verification workloads
• Benchmarking across hardware to ground realistic cost budgets

• CTV activation coordination discussion and timing
• Template Hash as an alternative expression of similar functionality
• Simplicity as a potential longer-term path for more expressive script with analyzable cost

• Josh Doman's Bitcoin++ talk (add link)
• UTX Oracle project (add link)
• CAT draft discussion post (add link)
• Post-quantum signature analysis post (add link)
• Delving Bitcoin: "324-byte stateful post-quantum signatures" (add link)
• CTV activation meeting / IRC note (add link)

Stephen wraps with thanks to listeners, notes that Atlanta meetups return in January, and encourages the audience to support the show on Fountain.

Broadcasting live from ATL BitLab, Stephen DeLorme and Alex Lewin close out the year with a festive edition of the BitDevs Radio Hour. This episode covers a grab bag of fresh Bitcoin technical developments: new BIP assignments, a novel approach to private collaborative custody, a consensus discrepancy discovered via differential fuzzing, Lightning protocol optimization ideas, a serious React server components security vulnerability, and the debut of Bitcoin Wrapped 2025.

It's a year-end mix of hard engineering talk, cryptographic concepts, dev-ops war stories, and community reflections.

Stephen and Alex recap the final Atlanta BitDevs meetup of the year and then dive deep into several new Bitcoin and developer-adjacent topics. The discussion includes new BIP numbers, privacy-preserving collaborative custody for multisig, a consensus mismatch uncovered in NBitcoin thanks to fuzzing, a fresh ZmnSCPxj proposal for Lightning efficiency via private key handovers, and a major security alert affecting React server components (and by extension, many Next.js deployments).

The show closes with the premiere of the community-produced Bitcoin Wrapped 2025 — a Spotify-style year-in-review for the Atlanta BitDevs Socratic series — plus some reflection on the biggest themes of the year: covenants, quantum, regulatory pressure, BitVM, new soft fork proposals, and the rise of Bitcoin corporate treasuries.

• BIP 110: Reduced-Data Temporary Soft Fork

• BIP 89: Chain Code Delegation for Private Collaborative Custody

• Why BIPs get "real" numbers instead of meme numbers (no BIP 444, sorry Twitter).

• The logic behind keeping related BIPs numerically clustered.

• Traditional multisig setups (e.g., Unchained, Casa) expose all xpubs to the collaborative custodian.

• BIP 89 proposes a way to prevent sharing full xpub information using chain-code delegation.

• Custodians can co-sign emergency transactions without seeing all user addresses.

• Built around key-tweaking and Schnorr-like math — allowing assistance without surveillance.

• Potential applications for backup key providers, insurance models (Anchorage / AnchorWatch), and privacy-preserving multi-party vaults.

• A divergence found where Bitcoin Core marked a transaction invalid but NBitcoin marked it valid.

• Discovered via differential fuzzing — fuzzing two implementations simultaneously and comparing outputs.

• Lightning fuzzing and Bitcoin fuzzing continue to find subtle mismatches between CLN, LND, LDK, BTCD, etc.

• NBitcoin maintainer patched the issue and cut a release the same day.

• Importance for enterprise shops using .NET (BTCPayServer, Zebedee, large corporate stacks).

• A proposal for more efficient on-chain HTLC resolution.

• If a Lightning channel's full balance ends up on one side, that party can be handed the ephemeral private key to spend HTLCs directly.

• Benefits:

  • Potential removal of anchor outputs

  • Unilateral RBF without interactivity

  • Easier UTXO consolidation

• Risks acknowledged: transporting private keys over the wire feels "icky" even with encryption.

• Not a re-architecture of Lightning — but an efficiency hack for edge cases.

• A severe RCE (remote code execution) flaw in several React 19 builds.

• Affects most Next.js apps created or updated in 2025 due to default server components.

• Attackers could potentially exfiltrate environment variables:

  • API keys

  • Lightning node macaroons

  • Stripe/OpenAI credentials

• Fix timeline: discovered Nov 29 → patched Dec 1 → public advisory Dec 3.

• Advice: upgrade React/Next.js immediately and rotate environment secrets.

A custom end-of-year highlight reel for the Atlanta BitDevs Socratic Seminar series.

Some of the big recurring themes:

• Covenants — CTV, CSFS, OP_TAPLEAF_UPDATE_VERIFY, and endless debate

• Quantum — threat models, timelines, algorithmic risk

• Regulatory drama — ETF approvals, treasury strategies, debanking, global restrictions

• BitVM — hype, skepticism, experimentation

• Fork proposals — CTV+CSFS and RDTS as the two most publicly mobilized

• Corporate Bitcoin treasuries — and whether they should become Lightning service providers

• Hackathon wins from the ATL BitLab community

• A recognition that Bitcoin is no longer niche — it's fully mainstream technical culture

• BIP 89 (Chain Code Delegation)

• BIP 110 (Reduced-Data Temporary Soft Fork)

• NBitcoin project

• Bitcoin Fuzzing library

• Lightning Fuzz

• Delving Bitcoin posts from ZmnSCPxj

• React / Next.js CVE advisory

• Bitcoin Wrapped 2025 (ATL BitLab)

Alex wraps up his final show of the year with a thank-you to listeners, welcomes suggestions for 2026 topics, and encourages everyone to find BitDevs Radio Hour on Fountain to send a boost.

Live from ATL BitLab, Stephen DeLorme and Alex Lewin sit down with Evan Kaloudis, founder of Zeus, one of Bitcoin's most beloved Lightning wallets. This episode dives deep into the design trade-offs of non-custodial Lightning, the emergence of "graduated wallets," eCash systems like Cashu and Fedimint, statechain-based systems like Spark, and the future of Bitcoin payments UX.

The conversation ranges from practical LSP economics to the viability of Ark, Spark, and other L2 proposals, as well as Evan's views on privacy, trust models, griefing attacks, covenants, and how wallets should guide users up the self-custody ladder.

Plus: merchant adoption, credit-card fee wars, and a closing reflection on how AI is reshaping modern engineering and Bitcoin development.

Evan Kaloudis – Founder of Zeus, the mobile Lightning wallet that began as a remote node controller in 2019 and has since evolved into a full Lightning stack with embedded LND, LSP functionality, swaps, eCash capabilities, and B2B onboarding tools.

It's time for another BitDevs Radio Hour! Alex Lewin and Stephen DeLorme discuss some of the latest technical developments in Bitcoin. This conversation covers topics like the merging of Cluster Mempool into Bitcoin Core, preventing lightning pinning attacks with P2A and v3 transactions, the drama over Jack Maller's getting debanked by Chase, and other topics.

The very first BitDevs Radio Hour! Alex Lewin and Stephen DeLorme discuss some of the latest technical developments in Bitcoin. This conversation covers topics like the Bitcoin Kernel Project, recent soft fork related debates and internet drama, and updates to the Bitcoin Improvement Proposal process with Murch's motion activate BIP3. Bonus: El Salvadaro smash buys the dip and Coinbase brings back ICOs.

Can Bitcoin replace DNS? Andrew Lunde presents Spaces Protocol, a permissionless naming system anchored on the Bitcoin blockchain. Learn how auctions determine ownership of top-level names like "@bitcoin," the technical challenges of browser integration, and the trade-offs between decentralization and scalability. Discover how $120,000 in Bitcoin has already been burned through the auction process, the role of DHT nodes in storing metadata, and why this approach may recreate the centralization problems it aims to solve.

Show Notes:

00:00 Opening Quote: Uncancelable Identity

00:30 Event Recording and Podcast Information

01:02 Sponsor Message: ATL BitLab

02:05 Introduction to Spaces Protocol and Permissionless Systems

04:14 What is Spaces Protocol? Sovereign Bitcoin Identity

05:39 Andrew Lunde's Background and Decentralized Systems

07:19 History of Decentralized Naming Attempts

09:20 Why Previous Projects Failed

11:57 The Centralization Problem with DNS

15:25 Censorship Examples: Malaysia and Catalonia

18:49 Certificate Authority Vulnerabilities

19:34 China's Internet Controls and Nostr

21:55 The Case for "Uncancelable" Names

26:46 Spaces Protocol Technical Overview

29:30 Auction Process and Community Identifiers

33:33 Hierarchy vs Flat Namespace Debate

35:11 Subspace Creation and On-Chain Registration

38:35 Why Top-Level Name Ownership is Required

42:39 Fabric DHT and Distributed Storage

45:19 Auction Mechanics: 10-Day Process

49:27 Bitcoin Burning and No Pre-mine Policy

51:23 Bid Refunding and Transaction Structure

54:55 Registration and Permanent Burning

57:30 Name Expiration and Escheat Process

01:00:36 Transaction Fees and Sustainability Concerns

01:04:00 Explorer Demo: $120,000 Bitcoin Burned

01:13:34 High-Value Auctions: Bitcoin, AI, Single Letters

01:16:03 Strategy Auction Case Study

01:21:09 Start9 Integration and Future Plans

01:23:08 Browser Integration Challenges

01:25:03 DNS Resolution Workarounds

01:26:37 Multiple Records and Subspace Management