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 · E65 · 10:09:55

S16 E65: Moonsettler on OP_CTV & Failing to Improve Bitcoin

23 Dec 2025 · by Vlad Costea · 14 min read
Published at block 929,151
Cover art for S16 E65, Moonsettler on OP_CTV & Failing to Improve Bitcoin
MP3 (334 MB)

The audio keeps playing while you browse the site.

Read the transcript89,383 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

Moonsettler and I were live for 10 hours and 9 minutes without a break, which is longer than any other conversation I have recorded on Bitcoin Takeover. He wrote OP_PAIRCOMMIT (BIP 442), contributes to the LNHANCE covenant package, did research for Cashu on DLEQ proofs and fraud proofs, and maintains the covenants support table on the Bitcoin Wiki, so I had a lot to ask him, about opcodes and about everything around them.

I also had a few things I wanted to say to him. I was convinced Bitcoin does not need to scale or prioritize privacy if mints and Lightning carry the weight, and Moonsettler thinks that is exactly how Bitcoin ends up reinventing the old financial system. We started there, and the argument kept coming back for the next ten hours. It covered the BitMEX story, KYC, the Bitcoin Cash hackathon he attended in 2025, a bribe joke about two coconuts and the question of how Bitcoin should migrate away from keys a quantum computer could break.

Inventing Banking Once Again

My opening position was that eCash mints and Lightning could be the scaling answer, and that the base layer can stay small and boring. Moonsettler's reply was that "Basically, they're inventing banking once again." He went after the way custodial eCash gets sold: as he put it, the whole arrangement is one where the mint is 100% trusted and can defraud you.

I pushed on the history, because Chaumian eCash is older than Bitcoin and Satoshi did not invent the idea of private digital cash. His point was that Satoshi "was able to create a decentralized version of electronic cash," which is the part the earlier systems never managed. When I asked whether centralized mints could still be acceptable for small amounts, he answered that "Fractional Reserve Banking is the natural state of banking," and that it appeared "again and again and again and again" long before central banks existed. In his view custodial eCash lets that pattern grow inside Bitcoin.

He has done work for Cashu himself, on DLEQ proofs and fraud proofs, which is the research that lets a user prove a mint misbehaved. I told him that made his skepticism sound odd coming from someone who helps build Cashu. He said the proofs make a trusted mint less dangerous, and that this is a different thing from making the trust go away.

Paper Bitcoin and Price Discovery

From there he went to the part of the argument I found hardest to answer. "Paper Bitcoin does not have any limit on it whatsoever," he said, describing custodians and leveraged products that manufacture exposure with no coins behind it on-chain. His conclusion was that "I don't think Bitcoin's on-chain scarcity has any bearing on price discovery anymore."

I asked how that squares with the 21 million cap, which every Bitcoiner has memorized. His answer was a line of arithmetic: "Infinity divided by infinity can be anything." If the claims on bitcoin are unlimited and the coins are not, the cap tells you very little about the price of the claims. He added a detail that surprised me, that "the Bitcoin that is free range is almost trading at a discount."

We took a detour through leverage culture, where the advice to "got to lever up" is treated as gospel on the timeline. He thinks it feeds the same machine. I reminded him that I have sold bitcoin and bought a car after Kraken froze my account, so I am not above using a custodian when it suits me, and he did not argue the point.

BitMEX, Coconuts and a Correction

I came into this section with a prepared line, because I have been critical of BitMEX for years. Moonsettler's position was "I'm not sure BitMEX is the problem, by the way." He said the regulatory trouble started when Arthur Hayes made a comment about paying "two coconuts" to a Seychelles official, a joke that drew attention the exchange did not need. When he walked through it I changed my mind on the spot and said so on air: the exchange was a symptom of how the industry gets squeezed, and I had been aiming at the wrong target.

The wider worry for him is adoption by way of intermediaries. "And if that is how the world adopts Bitcoin, then Bitcoin is a giant failure," he said, speaking of a future in which most people only touch Bitcoin through regulated companies. I asked whether any adoption at all beats none, and he held that adoption built on custody leaves the thing Satoshi published untouched but unused.

I also took the chance to tell the Maribor story, about confronting Saifedean Ammous in person, and about being blocked on X afterward. Moonsettler laughed and said that being blocked by the right people is a kind of credential.

Bankrupt the Compliant

The KYC section was the loudest part of the night. Moonsettler believes complying with identity requirements is a failure of Bitcoin culture, and he put it in the strongest terms I have heard on this show: "You have to bankrupt any business that is complying with this bullshit." For him this is a line to draw now: "This is the moment where you make your stand."

I asked what ordinary users are supposed to do when the only on-ramp in their country demands a passport. He said "you cannot comply your way out of tyranny," and that every compromise teaches the regulator how far it can push. He has no illusions about the exchanges either: "I have zero hope of any significant amount getting withdrawn from exchanges." I mentioned that I wrote the hosts of a hundred conferences into my contacts and none of them runs a swap without KYC, and he said that is the point.

We argued about a middle path, the kind of no-KYC swap service like SideShift that keeps one foot in the old rails. He did not defend it as pure, but he said it is better than a regulated exchange that treats every withdrawal as a favor.

A Promise You Cannot Break

Then the covenants. I asked him for a definition a non-developer could keep, and he gave me one: a covenant is "a promise that you absolutely cannot break." The mechanism, he said, is simple enough: "If someone fulfills the conditions in a covenant, then that is going to happen and it is provable." A signature says someone agreed. A covenant says the coins can only move one way, no matter who holds the keys.

He tied it to the entry-level proposal, OP_CHECKTEMPLATEVERIFY, which started life under the name OP_SECURETHEBAG, a name that describes what it does: the coins are locked to the bag you set up in advance. CTV commits a transaction to its exact outputs ahead of time. His example is paying out many people from a single on-chain footprint: "So you can pay 10,000 people in 34 bytes." He also pointed out that parts of this are in reach already: "So this is already possible today."

I asked about the part where a payer might later claim they never got paid, and he gave me a line I am keeping: "I don't know who you paid, but you did not pay me." The covenant answers that argument with a transaction that either exists or does not. This led to a long stretch where I tried to explain the same idea to a hypothetical grandmother, and I only half succeeded.

I also made a joke about Jeremy Rubin, the CTV author, and an invitation to Japan that involved Jeffrey Epstein. It was a bad joke.

OP_PAIRCOMMIT, LNHANCE and the Code Nobody Wants to Ship

This was the technical center of the show. OP_PAIRCOMMIT is BIP 442, Moonsettler's own opcode, and it is one piece of LNHANCE, a package that also contains OP_CTV, OP_CHECKSIGFROMSTACK and OP_INTERNALKEY. I asked how it came to be, and he said Anthony Towns contributed to it. He is also precise about its limits: "OP_PAIRCOMMIT is fucking useless if you just activate OP_PAIRCOMMIT." On its own it does little, and it needs the rest of the package to matter.

LNHANCE as a bundle is a compromise, and he said so: "It's a good compromise that doesn't make anyone super happy, but it is kind of acceptable." I asked whether miners could simply run it, and he told me "So if miners really wanted to have LNHANCE, the code is there." The activation client exists. What does not exist is a consensus anyone can point at. On the loop of reinvention he was blunt: "It's impossible for a developer to resist the urge to reinvent CTV," and "We literally waste years on it."

The BIP numbering has a story too, and he told it with relish. BIP 444, later renumbered to BIP 410, was assigned by Luke Dashjr, and Moonsettler said the original number came out of Christian numerology. I asked whether there is a rule against that, and he said there is not, which is how we ended up here.

On OP_CAT he was cautious. It could enable state-carrying scripts and automated market makers, which he sees as a potential misdirection pushed by large companies. His comment on the opposing camp was that "They think OP_RETURN makes Bitcoin more like Ethereum," and on the standing fight over the annex: "If you want to subject yourself to another three years of crying over the annex, then Do it."

Quantum Migration and Soft Fork Semantics

Paul Sztorc texted me in the middle of the broadcast. He said BIP 300 was created in 2018 because he recognized Core development was gate-kept. I read it out, and Moonsettler took it as proof of a pattern. He has no faith in the process: "I'm so disappointed in Bitcoin culture and the way development is handled." Paul Sztorc recorded his own episode on it: Paul Sztorc's own episode on activating drivechains via CUSF.

The quantum discussion produced our most heated semantic fight. I argued that any post-quantum migration that makes old coins invalid is a hard fork. Moonsettler's definition was the textbook one: "If something that was previously not valid is now valid, that's a hard fork." We spent a while on which direction counts. He wants a different emphasis altogether: restoring a general script language so that signature schemes can be swapped without freezing coins, rather than mandating a one-shot migration. He also said "You don't need to replace your cryptography. You can stack them and make them stronger." and noted that "They have to be finite in their use. You have to retire them periodically and move people to new keys."

When it came to timing he gave a flat answer: "As far as I can tell, we don't know shit." I spoke with Hunter Beast about Bitcoin's quantum resistance and BIP 360 earlier in the season. At one point in this debate Moonsettler said, "I admit that I was wrong," about a technical detail he had gotten backward, which he fixed in real time.

Rough Consensus, Hardware Entropy and Seeds You Can Verify

The last big stretch was about how Bitcoin decides things. He complained about "the idea that you can have rough consensus without someone being able to call rough consensus," and said that "we don't have consensus because we don't have consensus." His advice to everyone watching was practical: "If you like something, then tell people you like it." He described the process as running on reputation, and said it worked "on social capita. Personal follow the leader preferences and social capital and reputation. and Not on the merits of the proposal whatsoever."

He was equally direct about hardware wallets: "If you generate your seed phrase with a hardware device, you do not have any idea of the true entropy of that." His own recommendation is dice and manual verification. We went back and forth on the "proof of keys" ritual, where people withdraw from exchanges to prove they hold their own coins, and I argued it is mostly theater. He agreed it is mostly theater, but he likes it anyway, and said "I like that paper burns."

On wallet software he said that "it's a very good sign if the wallet you are using is open source and reproducible." I brought up WalletScrutiny, the project that checks whether wallets build reproducibly, and mid-stream I had to correct something I said about reproducible builds, because a viewer in chat caught me. I acknowledged it live.

On the Bitcoin Cash side he said he went to the Blaze 2025 hackathon and came away impressed. "Like objectively looking at what they have accomplished, how they tackled their challenges, how they How they move forward. I have to say, they did the work that I thought we will Do," he said. He was sharp about the fork itself and its history, but in his view the scripting-language work there was technically productive. I later recorded Calin Culianu, Steve Thurmond and the Phenomenal Big Blockers on nine years of Bitcoin Cash.

He also had harsh words for the maximalists who dismiss all of it, and told me what the original attitude was meant to be: "Really, the maximalist thing was all about, no, bro, I'm not buying your bags. Like, if you build something good, we are just going to take it."

Fighting Without Hope of Winning

Late in the night I played "Why We Build the Wall" by Anaïs Mitchell, and we talked about what it means to keep working on something that may not get activated. Moonsettler said "And while I don't see any hope of success, that doesn't mean I should stop fighting for what I believe in." He also said that "The way I see things, the way I think Bitcoin should be developed and the things I disagree on, I think those are my greatest contributions."

He has a theory about why the system drifts: "money has this gravity-like property, like money begets money. When a pile of money is big enough, it's going to grow faster than any small Change scattered around the landscape." On the question of who still cares about this, he was dismissive of passive holders: "Bitcoin holders that are holding for four years and signing one transaction every ten years, they don't give a flying fuck."

I asked him about what Bitcoin lost along the way, and he turned to something bigger than any opcode: "If you think about it, the biggest sickness of this world that we live in today, is that frontier culture got strangled out of existence." On the trust problem he said Satoshi "Wanted a system that works without trusted third party intermediaries. Bitcoin, as of now, We are absolutely fucking not working without that like this is not going to scale for shit." When I asked about Bitcoin Core, he said one developer in particular "actually trusts the gatekeepers," and pointed to the Bitcoin Core review process as the place where that trust turns into a veto.

What comes next for him is more of the same work. He plans to keep pushing LNHANCE, with the activation client ready for any miners who want it, to keep maintaining the covenants support table on the Bitcoin Wiki, and to keep working on Cashu's DLEQ and fraud proofs. On quantum, he wants the discussion to move toward restoring a general script language rather than waiting for a mandatory migration. And on the process, he will keep telling people to say what they like out loud.

Listen to Moonsettler on Spotify, Apple Podcasts, YouTube, and More

Time stamps:

  1. 00:01:16– Welcome Moonsettler (Doomsettler)
  2. 00:02:40– Delayed Interview and Original eCash Debate
  3. 00:03:14– Why eCash (Chaumian Cash) Never Took Off
  4. 00:04:00– Criticism of Custodial Scaling Solutions
  5. 00:05:14– Bitcoin as Decentralized Chaumian eCash
  6. 00:06:13– Fake Austrian Economics and Full Reserve Myths
  7. 00:08:32– Loss of "No Trusted Third Parties" Culture
  8. 00:09:52– Verifiable Supply vs Historical Fraud
  9. 00:13:40– Proof of Liabilities in eCash Mints
  10. 00:15:42– Cashu Fraud Proofs and Bug Bounty
  11. 00:18:20– Chaumian Blind Signatures Explained
  12. 00:24:48– Non-Custodial Credit eCash Ideas
  13. 00:30:39– Why Debit eCash Won't Scale Bitcoin
  14. 00:36:34– Bitcoin Like Linux – Oppose Custodial Layers
  15. 00:37:13– Unlimited Paper Bitcoin vs 21M Cap
  16. 00:41:25– Loss of Proof of Keys Culture
  17. 00:46:26– Doomsettler Mindset on Bitcoin's Future
  18. 01:09:30– Early Exchange Compliance Issues
  19. 01:11:37– Satoshi's Peer-to-Peer Vision
  20. 01:15:13– Satoshi's OPSEC and Disappearance
  21. 01:19:13– Craig Wright Not Satoshi
  22. 01:26:05– Libertaria and Frontier Culture
  23. 01:28:31– No More Frontiers for Freedom
  24. 01:39:21– App Delistings and PWA Debate
  25. 01:49:16– Twitter Worse Under Elon Musk
  26. 01:55:35– AI Ruining Internet Trust
  27. 01:56:33– Introduction to Covenants
  28. 01:57:04– Covenant = Unbreakable Promise
  29. 02:00:55– History of Covenant Discussions
  30. 02:01:29– Permanent Encumbrance FUD Debunked
  31. 02:03:38– Control Today via Multisig (No Covenants)
  32. 02:07:26– Covenants Don't Break Fungibility
  33. 02:08:35– Covenants Reduce Trust in L2
  34. 02:11:46– Post-Quantum Covenant Advantages
  35. 02:13:46– OP_CTV Explained
  36. 02:15:42– Non-Interactive L2 Settlements
  37. 02:20:23– Congestion Control with Covenants
  38. 02:29:08– Ordinals Drama & OP_CAT Risks
  39. 02:31:43– Jeremy Rubin Context
  40. 02:33:49– LNHANCE Package (CTV + More)
  41. 02:36:51– Why LNHANCE is Conservative
  42. 02:44:26– 2022 CTV Activation Drama
  43. 02:47:27– Curiosity vs Annoyance Motivation
  44. 02:49:04– Andreas Antonopoulos FUD Clip
  45. 02:51:15– Need for Covenant FUD FAQ
  46. 02:53:47– Persistent CTV Critics
  47. 03:55:27– Covenant FUD Knowledge Base Need
  48. 03:56:26– Steven Roose Support
  49. 03:57:40– Covenant Table on Wiki
  50. 03:58:56– Isolated Op Code Comparisons Issues
  51. 04:00:34– OPCAT vs CTV Preferences
  52. 04:01:48– Table Inconsistencies
  53. 04:02:19– Ordinals Devs Pushing OPCAT
  54. 04:03:26– CTV Strengths and Risks
  55. 04:10:22– Ideal Packages (Great Script Restoration)
  56. 04:43:24– Pink Floyd "The Wall" Analogy
  57. 04:45:49– Citadel Critique
  58. 04:49:49– Need for New Frontiers
  59. 04:51:56– Disagreeable Societies Preserve Freedom
  60. 04:54:56– Special Economic Zones for Renewal
  61. 04:57:50– Altcoins as Competition/Experiments
  62. 04:59:20– Privacy Coins Driving Response
  63. 06:00:34– Monero Privacy & Community
  64. 06:04:42– FCMP++ Upgrade
  65. 06:05:37– Monero Quantum Roadmap
  66. 06:07:16– Quantum Risks to Monero
  67. 06:09:47– Zcash Preference & Compatibility
  68. 06:11:34– ZK Privacy Advantages
  69. 06:13:16– Drivechains & Peg Risks
  70. 06:17:45– Spacechains
  71. 06:20:31– Quantum Threats to ECDSA
  72. 06:26:49– PQ Soft/Hard Fork Debate
  73. 06:34:57– Covenants for PQ Vaults
  74. 06:38:14– Ark Protocol
  75. 06:42:33– Lightning Custodial Risks
  76. 06:50:19– BitVM & Optimistic Rollups
  77. 06:55:44– Bitcoin Dev Culture Disappointment
  78. 07:49:05– Austrian vs Cypherpunk Values
  79. 07:53:20– Austrians Dislike Data
  80. 07:54:39– Full Reserve Myth
  81. 07:55:56– Core Dev Covenant Silence
  82. 07:57:32– Core Ignoring Covenants
  83. 07:58:22– Floppy's Drunk Posting
  84. 08:00:38– Calle's Cashu Story
  85. 08:02:02– Privacy Respect & Avoiding Doxing
  86. 08:02:29– Floppy's Drunk Tweets
  87. 08:03:48– Tolerance for Abusive Behavior
  88. 08:04:15– Understanding Non-Engagement with Floppy
  89. 08:04:32– Floppy as Builder (Joinstr Plugin)
  90. 08:04:57– Luke Dashjr Funding Complaints
  91. 08:05:23– Luke's Likability & Hack
  92. 08:06:36– Ocean Mining Business Model
  93. 08:08:36– Reducing Antpool Hash Dominance
  94. 08:08:56– Miner Template Building Debate
  95. 08:09:02– Mining Centralization Concerns
  96. 09:38:04– 9+ Hour Marathon Reflection
  97. 09:38:45– Girlfriend & Cat Interruptions
  98. 09:39:12– How to Follow Moonsettler
  99. 09:39:45– Moonsettler's Twitter Content Focus
  100. 09:40:38– Shoutout to SimulXXX (CTV Advocate)
  101. 09:41:29– Moonsettler as Crypto Hobbyist
  102. 09:42:37– Major Contributions Discussion
  103. 09:43:38– Non-Interactive Hardware Wallet Proofs
  104. 09:44:36– Sharing Personal Bitcoin Vision
  105. 09:45:14– Coldcard Experimental Implementation
  106. 10:03:18– Seed Backup Durability & Preference for Burnable Paper Backups
  107. 10:04:22– Manual Entropy & Seed Splitting
  108. 10:05:01– Early Self-Custody Cheat Sheets
  109. 10:05:25– Hardware Wallet Entropy Risks
  110. 10:06:30– Dice-Rolled Seeds vs Hardware
  111. 10:07:27– 2-of-3 Backup Scheme
  112. 10:07:59– Crypto Steel Promo
  113. 10:08:24– 10-Hour Mark, No Bathroom Break
  114. 10:08:49– Thanks & Merry Christmas
  115. 10:09:41– Next Episode Tease

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
fbce19db228e555f8398a4da4b92f72f9e64e15e14ada2aad55df752b7e2a054
Proof
2025-12-26_s16_e65_moonsettler_on_op_ctv_failing_to_improve_bitcoin_compressed.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 26 Dec 2025, but this proof was made on 3 Nov 2026 and anchored in block 974,312, so it proves this exact file existed by 3 Nov 2026, not on the release date.
How to check it yourself
  1. Download the MP3 and the proof into the same folder.
  2. Run sha256sum 2025-12-26_s16_e65_moonsettler_on_op_ctv_failing_to_improve_bitcoin_compressed.mp3 (on a Mac: shasum -a 256 2025-12-26_s16_e65_moonsettler_on_op_ctv_failing_to_improve_bitcoin_compressed.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2025-12-26_s16_e65_moonsettler_on_op_ctv_failing_to_improve_bitcoin_compressed.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-12-26_s16_e65_moonsettler_on_op_ctv_failing_to_improve_bitcoin_compressed.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