{"version":1,"type":"rich","provider_name":"Libsyn","provider_url":"https:\/\/www.libsyn.com","height":90,"width":600,"title":"BRH-010: BitDevs Radio Hour #10 \u2013 AI Agents Get KYC Bank Accounts, BIP-110 Vault Problems, $1M Lightning Payment Goes Live","description":"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\u2014South 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." Episode Summary Stephen and Alex open with housekeeping\u2014shorter show due to hard 5pm cutoff\u2014before 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\u2014reminiscent 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\u2014first 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)\u201414x 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"\u2014essentially 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"\u2014giving 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." Topics Covered \ud83e\uddf9 Bitcoin Inquisition: Consensus Cleanup Activated as BIP-54 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) \u26a0\ufe0f BIP-110 Controversy: Liana Wallet's Vault Problem 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\u2014impossible 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\u2014debate now "very much emotional thing" \ud83d\udd10 Quantum Resistance: BIP-360 and BIP-361 Merged 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\u2014must 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\u2014most 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? \u26a1 $1M Lightning Transaction: Enterprise Adoption Signal Voltage announcement: First publicly reported $1 million Lightning payment Route: SD Markets (Secure Digital Markets) \u2192 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\u2014direct 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 \ud83d\udcb8 Bithumb $40B Mistake: 620,000 BTC Instead of 620,000 KRW 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)\u201414x 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" \ud83e\udd16 Lightning Labs: Agentic Tooling for L402 and LND Elizabeth Stark (Lightning Labs CEO) previously teased agentic tools Lightning Labs announcement: "AI agents can write code, send emails, make phone calls\u2014but 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\u2014requires ability to spin up Lightning node on same server Target: OpenClaw agents on home computers or cloud servers \ud83c\udfe6 Magnolia: Bank Accounts for AI Agents 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"\u2014giving 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" \ud83d\udcb0 Agent Economy Landscape: Three Approaches Competing 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 \ud83d\udce2 Matt Corallo's Rally Cry: "Bitcoin Doesn't Just Happen, It's Built" 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"\u2014engineer 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\u2014describe problem to bot, bot does heavy lifting" Links 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 Closing Notes 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. ","author_name":"ATL BitLab Podcast","author_url":"https:\/\/atlbitlab.com\/podcast","html":"