Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
S16 · E27 · 2:28:56

S16 E27: David Seroy on Alpen Labs & ZK Rollups on Bitcoin

22 May 2025 · by Vlad Costea · 10 min read
Published at block 897,867
MP3 (205 MB)

The audio keeps playing while you browse the site.

Read the transcript25,780 words, every line links to the minute it was said

Ask this episode

Embed this episode

Paste this on your site or blog. It is a small player that streams from here: no trackers, no cookies, no ads.

Preview the player

David Seroy runs the non-technical side of Alpen Labs, a company founded by four MIT alumni who all come from Nepal, and the name is a hint: "if you rearrange the letters, it spells Nepal." We recorded with Bitcoin at $109,000, the stream ran 2 hours and 29 minutes, and David moved a business development meeting back by an hour so that I could keep asking questions. Ribbit led the round, with Wences Casares, Uma Roy of Succinct and Jeremy Rubin among the other backers.

I wanted him on because Alpen is one of the few teams trying to put ZK rollups on Bitcoin without a federation holding the coins, and because David is willing to argue the unpopular side of most things that come up on this show. The conversation started with origin stories and the name, wandered through Knots, Lightning, stablecoins and a fight on a Las Vegas stage that never happened, and ended on a disagreement I did not manage to close. The pickleball tournament Alpen won also came up, though I had no strategy for that one.

Four Nepalis, a Grant and an Anagram

Alpen's founders started out on research, not on a product. John Light had a grant from StarkWare and the Human Rights Foundation to study sovereign rollups, and the Alpen founders took that work and widened it. Then Robin Linus developed BitVM, and inscriptions made it possible to put ZK verifiers on Bitcoin in practice. David described the position of anyone using a rollup bridge before that as stark: "you would essentially have to give up your Bitcoin to someone else."

The name came out of a long naming process, and David has no illusions about how that goes: "naming is not easy. It's easier to build the tech than, you know, to name something." I pointed out that Citrea is a similar story, since it is the Turkish founders' word for orange. I had Orkun Kilic on in S15 E18 about the first ZK rollups on Bitcoin. David calls the two projects "conceptually quite similar" and expects the teams to drift apart as they move into different execution domains, SVM on one side and shielded CSV on the other. He added that he counts Orkun among "one of my favorite people," and passed along Talip's line that Bitcoin blocks have room for three or four ZK rollups.

Spam, Scaling and the Knots Argument

Rollups post data to Bitcoin, and the people who dislike that data have names. I asked about Knots and OCEAN, and David was dismissive of the technical case: "I mostly see this as like a guerrilla marketing tactic rather than a competent technical argument." On the supposed damage to the base layer he went further, calling it "pretty much an absolute nothing burger," and on the data in question: "this is not spam. This is scaling Bitcoin as money."

I added the old proof-of-work argument: it was designed to stop spam by making you pay for it, so anything with a fee attached is hard to call spam. David also took a swipe at the personalities, saying "you have people like Luke Dashjr, who is like extremely technically competent, but frankly, like at times, maybe a little bit like deranged." He said his own motive is plain: "I'm in this for money and not for, you know, NFTs or, you know, Dick Butts or, you know, like random tokens." On the security budget, rollups compress data "up to like a 30 to 50x compression effect," and he thinks valuable transactions stay on layer one, which he calls "a pretty significant criticism of drivechains." Near the end of the show he returned to the same fight: "the leverage in the debate has kind of switched," and "I don't need their permission. I don't care."

The Bridge and Its 1-of-N Promise

Alpen's bridge is built on BitVM and uses a 1-of-N trust assumption, which David summed up as working "as long as like one person or one party is honest." That was the point where I brought up drivechains. David prefers bridges that are "more closer to what we call cryptographically secured," as opposed to ones secured economically by miners. He talked about drivechains with respect, and I covered the same ground with David Burkett on MWEB and why drivechains need a use case.

On soft forks, the current plan needs none. In his words: "we don't need any sort of soft fork whatsoever, but it could make what we're building more efficient or cleaner." His wish list has four items: CTV, which he called elemental, CheckSigFromStack for efficiency, OP_CAT to remove the BitVM machinery and its trust assumptions, and multiplication for verifying ZK proofs. The multiplication gripe was vivid: "right now in Bitcoin script, like to try to do multiplication. "It's like, you have to like hack together, like addition, OP_ADD, OP_ADD, OP_ADD, you know, a bunch of crazy stuff." I had James O'Beirne in S16 E23 on CTV, CSFS and big blocks.

David also rejected the MEV worry for Bitcoin layer one outright: "I don't think that there's any credibility to the MEV argument." Alpen's research, he said, could yield a 100x to 1000x improvement to BitVM. A private devnet is running, a public testnet is expected in weeks or months, and mainnet is targeted for Q4.

A Grant, a Sacrificial Lamb and No Permission Slips

We spent some time on who gets to try these things. David pointed to the $1 million grant that was "put out" for this kind of work, and described the early adopters as "almost like a sacrificial lamb," since somebody has to go first and take the hit. On permission he was flat: "we don't need to ask for permission."

The backers matter to him too. Wences Casares, whom David described as "may be the single largest Bitcoin holder aside from Satoshi on the planet, who was like patient zero in Silicon Valley," made his first Bitcoin investment in over eight years by backing Alpen. David put it as "the guy that came up with the green Bitcoin logo" when the topic came up. His father texted him about some news before David had heard it himself: "I honestly didn't even know until my dad texted me."

There was a long detour around Nic Carter's Karate Combat fight and his recovery from an autoimmune condition, plus David Hoffman's broken ribs, and a story about the Alpen team taking "first place in the pickleball tournament." I also drifted into Phil Zimmermann and the 1990s PGP legal fight, when people printed the code on T-shirts as protected speech. Hoffman's ribs, I think, came out of an encounter with some gym equipment.

Dark Dollars and the Trojan Horse

David wants a lot to happen on top of a Bitcoin rollup. He described Bitcoin-backed lending protocols like Morpho as the alternative to what exists now: "you can just go to Morpho and borrow at 4.5% without any of the other hassle instantly." The current options are worse, because the collateral is "wrapped, so it's trusted, it's centralized, you're using WBTC." A rollup with real bridges would mean "no more excuses." He knows there are limits: "there is no amount of ZK cryptography, BitVM, that can ever fully eliminate the trust assumptions" between two consensus systems. I asked whether Alpen users would face a hidden catch, and he said "With Alpen? No."

On stablecoins we disagreed immediately. David said "I see stablecoins as actually kind of like a bridge to hyperbitcoinization," and I replied that the T in Tether "stands for Trojan horse." He countered that "every dollar that goes into Tether 100% supports the fiat game," and then, on my objection that stablecoins undermine Bitcoin, called it "that's a total red herring." His proposal is what he calls dark dollars: privacy-focused, Bitcoin-collateralized stablecoins.

Privacy rollups drew my skepticism. David's answer was that "this intersection of like stablecoins and privacy, it's non-existent," so there is room to build it. He noted that privacy is a "less talked about" use case and that "it's a very precarious thing to say that you support" it. Shielded CSV from Liam Eagen and Robin Linus offers scalability and privacy together, and Liam Eagen, Robin Linus and Jonas Nick covered it in S15 E58. David also corrected our vocabulary: "the technical term we should be using is like a validity proof rather than a zero knowledge proof." Alpen's proofs give validity, not privacy.

Lightning, Merchants and a Butter Robot

I asked about merchant adoption, since the show has run on the claim that Bitcoin should be spendable. David said the focus has moved, and that "I think we just oversold what Lightning can actually do." He sees Lightning as fixated on high-frequency payments, with a custodial user experience to match: "Lightning is more custodial, so is Fedimint." I answered with the butter robot meme ("what is my purpose?") and a more serious worry, that "you get Bitcoiners accustomed to using custodians."

David is comfortable with unpopular positions: "I like being the underdog." He added that "the puck is moving in a different direction," and that conference organizers keep seating him against Paul: "they always put me on panels with Paul." The stack he wants to build is "radically unopinionated," and the crowd that cares about BitVM and ZK rollups is small, since a lot of other people "don't care about BitVM and they don't care about ZK rollups."

One more idea from him: account abstraction on a rollup would let a phone's secure enclave act as a hardware wallet, because modern smartphones already have the hardware and only lack the programmability. I also joked that David was trying to get me "jumped in Vegas," after a bit about a panel that went sideways in my telling.

No Token, and a Fight I Did Not Win

Alpen has no token, and David said so before I finished asking: "No, we don't have a token." Gas is paid in Bitcoin, and the team is "bending over backwards to avoid one." His anger at the industry comes out here: "that's my biggest issue with the tokens is they've just like, they've radically set back our industry from like a development and engineering perspective." He also holds that "we can't, you know, we can't let Bitcoin development be dictated by people who are not developers and who literally have like no idea about how these protocols work."

Whether any of this reaches mainstream users is something he leaves open: "the jury is still out." He expects "insane amounts of BTC" to flow into the system once it works.

Where we still disagree is the stablecoin question. David believes Bitcoin-collateralized stablecoins on a rollup lead people toward hyperbitcoinization, and that the dark dollar idea can offer privacy as well. I still think a dollar on Bitcoin teaches people to hold dollars, and that Tether-style trust sits uneasily next to a project built on removing trust. We did not settle it, and both of us said so.

Listen to David Seroy on Spotify, Apple Podcasts, YouTube, and More

Time stamps:

  1. 00:00:56– Introduction to the Episode
  2. 00:02:08– Background on Alpine Labs
  3. 00:05:00– The Concept of ZK Rollups
  4. 00:08:04– Comparing Alpen Labs with Drivechains
  5. 00:10:18– Concerns About Data Usage
  6. 00:12:41– Nuances of Data Posting
  7. 00:13:47– Opposition to Rollup Data
  8. 00:14:43– Filtering Transaction Data
  9. 00:17:31– Consensus on Bitcoin Usage
  10. 00:19:39– The Complexity of Changing Bitcoin
  11. 00:22:29– Historical Context of Data Insertion
  12. 00:22:43– Creating Layers on Bitcoin
  13. 00:23:28– Scaling Bitcoin Beyond Marketing Drama
  14. 00:23:45– Trust Assumptions in Multi-Sig Deployment
  15. 00:24:16– Soft Forks for Efficient Financial Services
  16. 00:25:00– Benefits of CTV and Check Sig From Stack
  17. 00:25:56– Improving Efficiency with New Soft Forks
  18. 00:27:01– Challenges of Multiplication in Bitcoin Script
  19. 00:27:43– Irony of CTV's Reception
  20. 00:28:53– Opposition to Change in Bitcoin
  21. 00:30:14– Concerns Over OP_CAT and MEV
  22. 00:31:14– Safety of MEV in Bitcoin's Ecosystem
  23. 00:32:22– Using OP_CAT in Bitcoin
  24. 00:33:28– Starkware’s Grant for Rollup Research
  25. 00:34:52– Building on Bitcoin Cash vs. Bitcoin
  26. 00:36:38– Bitcoin Price All Time High
  27. 00:39:07– Alpen Labs' Development Plans
  28. 00:40:10– Bitcoin.com’s Shift to BTC
  29. 00:41:04– Differences Between CTV and Alpen Labs
  30. 00:43:21– Backers of Alpen Labs
  31. 00:44:28– Ethereum People Investing in Alpen
  32. 00:45:02– Nic Carter's Fight Experience
  33. 00:47:00– Reflections on Fighting Culture & Karate Combat
  34. 00:48:52– Personal Athletic Endeavors
  35. 00:50:15– Debate on Ethereum's Influence
  36. 00:52:51– Nuances of Ethereum and Bitcoin
  37. 00:54:21– Rollups and Trust Assumptions
  38. 00:55:19– David Seroy’s Stratacast
  39. 00:56:23– Need for Niche Bitcoin Podcasts
  40. 00:58:17– Bitcoin's Existential Crisis
  41. 01:00:01– Stock Portfolio Sacrifices
  42. 01:00:56– Bitcoin as a Store of Value vs. Payment
  43. 01:01:06– Concerns Over Stablecoins
  44. 01:03:14– Legitimacy of Stablecoin Claims
  45. 01:04:36– Building Bitcoin-Backed Stablecoins
  46. 01:05:31– Bitcoin-backed Stablecoins Demand
  47. 01:06:34– Intersection of Stablecoins and Privacy
  48. 01:07:29– Potential for Privacy-focused Stablecoins
  49. 01:08:35– Changing Adoption Narratives
  50. 01:09:48– Synergy Between Stablecoins and Bitcoin Adoption
  51. 01:10:51– Ideological Shifts in Bitcoin Use
  52. 01:12:56– Alpen Labs and zk Technology
  53. 01:15:51– Client-Side Validation Origins
  54. 01:18:31– Zero-Knowledge Proofs in Transactions
  55. 01:20:30– Bridging Bitcoin to Privacy Protocols
  56. 01:21:00– Privacy vs. Market Attention
  57. 01:22:37– Legal Implications for Privacy Protocols
  58. 01:27:51– Privacy in Bitcoin
  59. 01:28:07– The Future of Privacy Solutions
  60. 01:29:54– Understanding zk Technology
  61. 01:31:20– Current Rollup Implementations
  62. 01:32:28– Interoperability of Rollups
  63. 01:34:19– Critique of Lightning Network
  64. 01:36:13– Challenges of Lightning Network
  65. 01:39:47– Cultural Commentary on Bitcoin's Evolution
  66. 01:43:14– Drivechains and Rollups for Miners’ Revenue
  67. 01:48:10– Mainstream Bitcoin Events
  68. 01:49:38– Alpen Labs and Tokens
  69. 01:50:22– The Ethereum Token Dilemma
  70. 01:51:05– Token Justification and Practices
  71. 01:52:00– Incentive Issues with Tokens
  72. 01:53:22– Lightning Network and zk Rollups
  73. 01:55:09– Alpen Labs Main Chain Launch
  74. 01:56:19– Cultural Resistance to Innovation
  75. 01:58:42– Building Without Community Approval
  76. 02:01:35– User Experience with zk Rollups
  77. 02:04:52– Current Wallet Compatibility
  78. 02:06:42– Yield Generation in DeFi
  79. 02:09:37– Bringing Ethereum Innovations to Bitcoin
  80. 02:11:11– Scaling Bitcoin: Block Size Debate
  81. 02:12:33– Historical Perspectives on Block Size
  82. 02:14:13– The Shift in Bitcoin Developer Opinions
  83. 02:15:06– The Rise of Pragmatism in Bitcoin Development
  84. 02:17:01– Challenges with Bitcoin Narratives
  85. 02:19:11– The Role of Non-Technical Voices in Bitcoin
  86. 02:20:25– Optimism Amidst Bitcoin's Challenges
  87. 02:25:12– The Power Dynamics in Bitcoin Development
  88. 02:27:48– Closing Thoughts and Future Directions

Verify this episode

This is the SHA-256 fingerprint of the MP3 as published here, timestamped in the Bitcoin blockchain with OpenTimestamps. If one byte of the file changes, the fingerprint changes.

SHA-256
9459e2a869d2b94762c66e3ebf3ab2dedace8b1c6cbca09750356a62ff3ac128
Proof
2025-05-27_s16_e27__david_seroy_on_alpen_labs_zk_rollups.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
How to check it yourself
  1. Download the MP3 and the proof into the same folder.
  2. Run sha256sum 2025-05-27_s16_e27__david_seroy_on_alpen_labs_zk_rollups.mp3 (on a Mac: shasum -a 256 2025-05-27_s16_e27__david_seroy_on_alpen_labs_zk_rollups.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2025-05-27_s16_e27__david_seroy_on_alpen_labs_zk_rollups.mp3.ots. It hashes the MP3 again and checks the proof against your own Bitcoin node, then prints the block and the date the file existed by. Without a node, ots info 2025-05-27_s16_e27__david_seroy_on_alpen_labs_zk_rollups.mp3.ots shows the block height to look up in any block explorer.

Share: X · Email · Link

Related

Comments

Comments run on my own server. No trackers, no tracking cookies.

0:000:00