Research
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 · E56 · 2:59:50

S16 E56: Super Testnet on Papa Swaps, BIP 444 & Prediction Markets

4 Nov 2025 · by Vlad Costea · 17 min read
Published at block 922,215
Cover art for S16 E56, Super Testnet on Papa Swaps, BIP 444 & Prediction Markets
MP3 (247 MB)

The audio keeps playing while you browse the site.

Read the transcript30,631 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

Super Testnet joined my livestream, described his newest protocol, and then warned the audience that "you'll probably lose your money because I'm a bad coder." A few minutes later he explained why he supports a soft fork proposal he is fairly sure will end up "dead in the water". Rarely does a developer pitch a project and handicap it in the same breath.

This was his second appearance on the show this season. We last spoke in February about his campaign to prove that Lightning is more private than Monero. Since then he has built Papa Swaps, a way to do submarine swaps with a single on-chain transaction, presented it at Bitcoin++ in Istanbul, and kept shipping: a Spam Tester page, Arkash (a Hedgehog-style payment idea on top of Ark) and Aggeus, a prediction market design that runs natively on Bitcoin. He also says he helped Robin Linus on the work that became BitVM, which I asked him about at the very end.

The episode ran almost three hours, with questions coming in from Nostr, Twitter and YouTube. We covered Papa Swaps, the BIP 444 fight (where we disagree, politely), Spark's privacy problem, a half-formed idea for range proofs on Bitcoin, and a story about Paul Sztorc and the oracle problem.

One Transaction Instead of Two

Super's setup was a short primer. Lightning invoices are not something an old-style wallet can pay, because "a normal Bitcoin address can't pay them." A submarine swap links the two sides atomically, so the invoice only gets paid if the on-chain payment goes through too. The usual version costs two transactions: one to fund an HTLC and one to sweep it.

The idea for Papa Swaps came out of a conversation in Mexico. He was praising Phoenix, which uses splicing (one transaction, close the channel and reopen it smaller), when a friend objected that "whenever I pay someone on the base layer, my capacity drops." The friend used submarine swaps instead, since only the balance shifts inside the channel. Super's reaction: "I think there's a way to do submarine swaps in one transaction." Splicing already proved it was possible, so he went looking for a protocol that does it without Phoenix.

The result is faster, cheaper and lighter on block space than the two-transaction version, all for the same reason: one transaction instead of two.

The name is a Cold War joke. The fastest submarine ever built was the Soviet K-222, which the Americans classified as the Papa class, and "Papa Swaps sounds funny." I suggested the Hedgehog protocol was a similar nod to Sonic. He said he picked it because all the Lightning puns were used up. A question from Saunter on Nostr asked "When Hedgehog?", and the answer was disarming: "the answer is probably never." He explained that "I seem to be the only developer who is interested in hedgehog channels, and even I don't really work on them, except when I want to do a show and tell at a conference." These things take off when somebody commercializes them, and he does not want to.

Happy Path, Sad Path

The mechanism is a two-of-two multisig plus a relative time lock. Instead of an absolute block height, the timer starts when money enters the address: "just once money enters the address, that's when the timer starts ticking." The roles also flip. In Papa Swaps the party on the base layer generates the secret, and the Lightning side buys it by paying an invoice. Once the secret is known, the buyer can spend the multisig unilaterally, and the whole swap used one on-chain transaction.

If the other side balks, the fallback is to put the money into the time-locked HTLC, which costs more. In his words: "Papa Swaps are worse in the sad path because there's three transactions instead of two." My view was that over 90 percent of swaps end well, so the trade seemed fine.

I pushed on double spends, since the Lightning payer reveals value before the on-chain money is final. He agreed this is the risk: "what he has to do is wait for a confirmation." RBF does not change the picture, because it was only ever a mempool policy. In practice, he admitted he usually skips the wait with well-known swap providers, and "I haven't gotten wrecked on my little small $10 transactions of using submarine swaps." He would not do that with a large amount.

On block space savings, he had not run the numbers. His guess was hundreds of transactions a day across Boltz, Muun and Lightning Loop, "but that's just a guess." Muun in particular, which needs two base layer transactions per swap, would hold up better when fees rise.

Adoption is early. The code is "a proof of concept" that works on mainnet if you are brave. A developer from PeerSwap who saw the Istanbul talk said he would implement it. Boltz seemed less moved, though Super reported that "if wallets adopted, then he would do it." (He first named the person as Michael Bumann; I corrected him, since Bumann runs Alby. I looked it up on air: Boltz's CEO is Kilian Rausch, and the coder is a pseudonymous co-founder named Michael.) Evan Kaloudis at Zeus has seen a demo and likes his stuff, though without a commitment. Super's advice to the audience: "Nagging is a great way to get things done in stuff like this."

That led to a tangent about Joule and Bottlepay, two browser tipping tools I miss. Super's request to Nostr developers: "recreate that using Nostr Wallet Connect." Right after that I read the sponsor spots for LayerTwo Labs and SideShift, and we moved on to BIP 444.

Spam Filters and the Bandwidth Argument

Then we hit BIP 444. Super prefaced it with the case he has been making lately: spam filters have an objective, selfish benefit. His Spam Tester page on GitHub finds a recent transaction that Knots filtered but Core accepted, and compares bandwidth on both. Filtered transactions are not relayed, so "Bitcoin Knots nodes use objectively less bandwidth than Bitcoin Core node when it comes to spam transactions."

I countered that filters do not stop a determined miner. He agreed: "They don't completely stop spam from getting into blocks." His longer-term argument is about compact block relay. If enough nodes filtered a transaction, blocks containing it would propagate more slowly and lose more stale-block races, which hurts small miners most. He granted that the effect only appears at something like 50 percent adoption, not at today's roughly 20.

I raised the mempool.space block painting episode: Portland.HODL wrote software that orders transactions to draw pictures in mempool.space's color scheme, which I took as evidence that miners do not simply follow the mempool. Super said he was told "other mining pools who didn't have this software were paying MARA to paint blocks for them," which he called a great marketing move, though he is no fan of building on a proprietary API.

The harder question was what counts as spam. A viewer insisted spam does not exist, since all transactions are permissionless. Super's definition separates moving value from UTXO A to UTXO B from everything else: "I consider the extra data spam." He thinks his definition has "objective technical" consequences (your node uses less bandwidth), while the other side "just has opinions." I observed that we now disagree about what a soft fork is and what spam means, so we talk past each other. He offered a theory that "transaction" itself is a collision of two vocabularies, since Bitcoin is both a database system and a financial system.

I brought up the Pikachu idea he floated when we met two years ago: catching one on Bitcoin with BitVM. By today's standards, would that be spam? No, he said, because in BitVM's happy path "you keep the junk stuff off the blockchain and only put the financial part on the blockchain."

I told him my understanding, which is that Citrea's mainnet design will use ordinary inscriptions, not OP_RETURN, because that code is already audited. His reply was "That sounds like an improvement." He still opposes both, and would rather rollup data not go on Bitcoin at all, though he said he would read their papers before making a final call.

BIP 444, Odds and an Emergency Switch

I asked Super to define BIP 444 for listeners who had been offline. He read from the text: the name is Reduced Data Temporary Softfork. By his reading, it makes invalid a list of places where data hides: oversized output scripts (capped at 34 bytes), push data (256 bytes), OP_RETURN (83 bytes), undefined witness and tap leaf versions, and a few more. The rules would lapse after about a year. A miner who included such a transaction would produce a block that adopting nodes would reject.

His forecast was sober. He thought roughly 20 percent of node runners had moved to Knots, that maybe half of those would run a BIP 444 build, and that perhaps a quarter of everyone else would run software rejecting blocks from miners who enforce it. He doubted even OCEAN would enforce it: "I don't think they're going to have the guts to go ahead and do it." The best he could imagine is OCEAN losing some hashrate.

He likes the idea but not the deployment. He fondly remembers the Taproot signaling campaign, with Hampus Sjöberg's block counter website and the green and red square hats, and wants to do it that way again. What bothers him is the emergency path, where miners reject a block with an offensive image and start enforcing immediately. "I really don't like the emergency deployment part of the proposal. But the rest of it seems decent." He added that it "sounds fun, but it's fun in a scary way." A chat viewer joked that some people will emergency-deploy changes to the whole network at once, to which Super replied, "Welcome to Inscriptions."

Slippery Slopes and Name-Calling

On a government-mandated OFAC filter he left no doubt: "Money that you can't send to people in Russia or people in Cuba or people in North Korea is a worse money than a money where you can do that." Then: "I'm not running that on my node." He also rejected a viewer's claim that filtering makes miners money transmitters: "I don't think there's any law that says or implies that if a miner says no to a certain transaction, that makes them a money transmitter." And "I do want to filter other people's transactions."

Our disagreement boiled down to default settings. I am pro-choice about relay policy, but I dislike a one-size-fits-all default. Super took that as a design brief. Neither Core nor Knots makes it easy to choose a policy before first launch, so he suggested a setup wizard with checkboxes (inscription envelopes: yes or no?) as a hackathon project. Windows 98 setup wizards were his model. He admitted, "I get like seven ideas a day. I think I've gotten four of them just talking to you."

On tone, he said he first read "Knotzis" as good-natured teasing, but using it in place of an argument "is a fallacy called ad hominem." I told him I was disappointed to see Nick Szabo use "Coretards."

I asked whether the real problem is cultural and whether a soft fork can happen again. Super is pessimistic: "I don't think we're going to ever see a soft fork again in Bitcoin." He also doubts that CTV ever had consensus among influencers, to which I replied, "since when are the influencers the one that make up the consensus?" He meant developers, he explained, and he does not think most of them ever liked the idea.

Spark, Arkash and the Check in Your Pocket

A question from Nostr asked whether Spark is spying on Lightning users. Super said it effectively is. Spark has a block explorer that shows the balance and full history of any Spark address, and, he said, "This is also not necessary. They don't need to do this." He still praised the UX and the fact that a state chain finally has real usage: "state chains have been possible in Bitcoin since 2017. And no one ever used them until now."

I reminded him of Mercury Wallet. He said he used it once for the state chain torch and that its shutdown suggests "not very much demand for it." Both his own state chain implementation and Mercury used blinded servers, meaning the server did not know your balance. Spark could do the same but chose not to. Until then, the mitigations are familiar: Tor or a VPN, avoiding public key reuse and avoiding co-spends. He pointed to Bull Bitcoin, which cited GDPR compliance as a reason to CoinJoin its outgoing transactions, as a template for pressuring Spark.

Another viewer asked about Arkash, which he described as recreating Hedgehog's goal on top of Ark: sending money without first asking the recipient for an address. His analogy was cash or a check, where "if I want to write you a check, I don't need anything from you." The sender creates an Ark private key, funds it, and shares the string by email or DM. The recipient opens a web page that generates a wallet and imports it. It is not finished: "I don't even think it's really self custodial yet," since it does not validate the server's data.

The sender can also reclaim the funds, which Super likes on purpose: "often when I'm onboarding people to Bitcoin, I'll give them $5 in Bitcoin." If they never spend it, he can take it back after a year.

Range Proofs Out of a Payjoin

At my prompting he talked about making Bitcoin more private. His idea started from Payjoin: when the receiver contributes inputs, an outside observer cannot tell how much was really sent. If I send you five coins and you add an input holding two, the transaction shows seven. He realized that this works as a range proof "if you do my usual trick of redefining things and saying that now I'm gonna use this word to mean this other thing and it's close enough."

Scale it up to ten inputs and ten outputs, and the possibilities explode (he floated something like 10 factorial). Add a Papa Swap and the receiver can send the change back over Lightning, so any amount from zero to the total becomes plausible. "I think we have native range proofs on Bitcoin," he said, though he has not written a proof of concept. I noted this is "just like a deniability for the amount", and he replied, "one out of three is something."

I also mentioned Shielded CSV and ZKCoins. He answered, "I don't actually know anything about Shielded CSV, other than I think it's similar to ZKCoins." I took the chance to talk up Zcash, which grew out of the Zerocoin and Zerocash research that early Bitcoin privacy debates once expected to arrive via soft fork. He has not studied it ("I haven't looked into the Zcash whitepaper yet or how Zcash works") and added that if I sent him any, "I'm immediately converting them into Bitcoin."

A Prediction Market Without a Side Chain

His other new project, which he suggested I put in the title, is a prediction market. He started from discrete log contracts, where two people bet on an outcome and an oracle decides who gets the money. The sticking point is that a DLC address needs both parties' keys, so you cannot just show a "yes" address on a website and let anyone pay in. The fix he implemented in a project called Aggeus combines two borrowed ideas. First, a proxy takes the opposite side of each bet and passes along a mirror-image contract to the real counterparty, an idea that was proposed for Lightning DLCs but, as he puts it, never implemented. Second, PSBT auctions from the Ordinals world let a user pre-sign a transaction so the proxy can complete it when a counterparty appears.

The user does not need to be online for the match. And "the proxy never holds custody of any user funds." A third piece, selling your position early like on Polymarket (cash out at $120 after your $100 bet gains 20 percent), is specified but not coded: "which I actually have not implemented yet."

Predyx, a custodial Bitcoin prediction market, was due to hear the pitch later that day, as Super told it, since they want to go non-custodial.

The reality check came from Paul Sztorc at a recent conference. Paul was unimpressed: "You're like the hundredth person who's come up with a way to do prediction markets." His real question was how Super solved the oracle problem. Super's answer: "I just said you have to have an honest oracle." Paul pointed him to the Hivemind paper (the project once called Truthcoin), which Super described as 80 pages of "advanced mathematics that I don't understand yet." His verdict on his own work was gracious: "it turns out I was solving the wrong problem." He still offered the code to anyone who wants to take it further: "It's all open source. Public domain." When I raised the "don't be a dick" principle of paying credit forward, he said, "I make no such stipulation."

Credit for BitVM, Earned the Hard Way

Near the end I asked about his favorite mathematicians and cryptographers. He named Robin Linus and Liam Eagen. I filled in that Robin created BitVM, and Super quickly added, "Regarding that Robin Linus created BitVM, I also helped." I told him he should get credit, and he replied, "I think so. And Robin thinks so. We all think so."

The backstory he told is amusing. Before BitVM, he had tried to recreate on Bitcoin the Turing machine experiments that BSV developers built with old opcodes like OP_CAT. His versions were limited by script size, but "It was my work on that stuff that got Robin's attention", and Robin figured out how to make programs arbitrarily long. Robin also taught him about Lamport signatures. Super even went on a BSV podcast to talk about it. I recounted the 2015 conference panel where Craig Wright insisted Bitcoin was Turing complete and Nick Szabo told him to write a paper, and joked that Super's group made the effort that paper never did. Super's summary: "The precursors to BitVM came from me trying to recreate BSV's technology." The same BitVM idea got me thinking about layer twos and spam all over again, as earlier in the show.

We ended on the block size wars versus today's fights. I said the earlier arguments happened at conferences like Scaling Bitcoin, with more mutual respect, and that next week I would host Jonathan from BitMEX Research, who has written about a similar spam argument from 2010 involving Satoshi and Hal Finney. Super pointed listeners to his Nostr thread with Aaron van Wirdum as a respectful take on this debate. A commenter said altcoins exist precisely because of situations like this, and I agreed in a way that annoyed nobody in particular: "Last time it was Ethereum. This time it's probably Zcash." Then Super had to leave to prepare his slides for the Predyx call. His website, supertestnet.org, lists his projects and his handles.

This conversation follows our earlier one on Monero versus Lightning privacy, and the prediction market idea has an older ancestor on this show in Paul Sztorc on the philosophy of drivechains and prediction markets.

Listen to Super Testnet on Spotify, Apple Podcasts, YouTube, and More

Time stamps:

  1. 00:01:28– Intro: Super Testnet's Return to the Bitcoin Takeover Podcast
  2. 00:03:03– Lightning Privacy Wars: Recapping Super's Monero Challenge & Layer 2 Debates
  3. 00:03:43– Papa Swaps Unleashed: Super's Lightning-Fast Innovation Explained
  4. 00:04:57– Submarine Swaps 101: From Layer 1 to Layer 2 in a Flash
  5. 00:06:04– Phoenix Wallet Magic: Splicing vs. Submarine Swaps – Why Capacity Matters
  6. 00:07:55– Birth of Papa Swaps: From Mexico Chats to Single-Transaction Breakthrough
  7. 00:09:19– Why "Papa"? The Hilarious Submarine Speed Pun Behind the Name
  8. 00:10:23– Hedgehog Protocol Update: When Will It Launch? (Spoiler: Probably Never)
  9. 00:12:00– Hedgehog's Fate & Super's Conference Show-and-Tells
  10. 00:12:47– Papa Swaps Deep Dive: Relative Time Locks & Happy vs. Sad Paths
  11. 00:14:47– How Papa Swaps Work: Secrets, HTLCs, & Atomic Swaps Simplified
  12. 00:18:33– Risks & Tradeoffs: Double Spends, RBF, & Trust in Small Transactions
  13. 00:21:02– Block Space Savings: Papa Swaps vs. Boltz, Moon Wallet, & Lightning Loop
  14. 00:22:29– Papa Swaps' Edge in a Crowded Layer 2 World
  15. 00:23:29– Sidechain Shoutouts: Citrea, Alpen, & Scaling Debates Revisited
  16. 00:24:32– Papa Swaps Today: Proof-of-Concept, Mainnet Risks, & Wallet Adoption
  17. 00:27:02– Will Phoenix & Breeze Integrate Papa or Hedgehog?
  18. 00:28:47– Boltz Exchange Scoop: CEO Kilian Rausch & Co-Founder Michael
  19. 00:29:35– Lightning History: Joule, Bottle Pay, & Nostr Wallet Connect Ideas
  20. 00:33:06– Ad Break: Layer 2 Labs' Drivechains
  21. 00:34:57– Sideshift.ai: Swap Stables for BTC
  22. 00:37:10– BIP 444 Drama
  23. 00:38:18– Spam Filters Work for Bandwidth Savings
  24. 00:39:32– Miners' Risks: Orphan Blocks & 50% Filter Adoption Scenarios
  25. 00:42:44– Mempool Art: Portland Hodl's Block Painting Software & Mara Pool Deals
  26. 00:44:28– Spam Defined: Extra Data vs. Permissionless Purity Debate
  27. 00:48:21– BitVM Dreams: Catching Pikachu on Bitcoin Without Spam
  28. 00:50:29– Citrea & Alpen: BitVM 2/3, ZK Proofs, & Data Availability Concerns
  29. 00:52:55– Citrea Marketing Myths: Inscriptions Over OP_RETURN in Launch
  30. 00:53:29– OP_RETURN vs. Inscriptions: Base Space Scarcity & Pruning Debates
  31. 00:56:35– BIP 444 Breakdown: Temporary Spam Ban & Consensus Changes
  32. 01:00:06– Legal Slippery Slope? OFAC Lists, Sanctions, & Permissionless Fears
  33. 01:02:05– BIP 444 Odds & Details
  34. 01:07:15– Inscriptions as Anchors: Layer 2 Onboarding or Hidden Spam?
  35. 01:10:26– OP_RETURN Drama: V30 Update vs Filters
  36. 01:13:31– Community Toxicity: "Knotzis," "Coretards," & Ad Hominem Fallacies
  37. 01:16:40– Pleb Slop & Purity Quests: Dogma vs. Base Layer Privacy Push
  38. 01:20:01– Spam Doesn't Pay Node Runners – Miners Only
  39. 01:21:42– Pro-Choice Nodes: Custom Policies, Wizards, & Hackathon Ideas
  40. 01:25:18– Windows Wizards & Idea Generation: Super's Creative Process
  41. 01:26:24– Ad Break: Bitcoin.com News – Balanced Global Crypto Coverage
  42. 01:27:28– NoOnes: Ray Youssef's P2P Marketplace for the Global South
  43. 01:29:57– Chat Q&A: Money Transmitters, Legal Fears, & Miner Roles
  44. 01:34:00– Spark Wallet Exposed: Privacy Leaks & Statechain Explorer Risks
  45. 01:35:31– Mercury Wallet Nod: Statechains' Real-World Usage Milestone
  46. 01:36:05– Blinded Servers: Hiding Balances & History in Statechains
  47. 01:37:20– Privacy Mitigations: IP Hiding, VPNs, & Avoiding Key Reuse
  48. 01:38:43– Spark Improvements: CoinJoins & Future Privacy Features
  49. 01:40:27– GDPR Compliance: Bull Bitcoin's CoinJoins & Legal Privacy Push
  50. 01:41:57– Nostr Frustrations: Searching Old Posts Sucks
  51. 01:42:58– ARCash DExplained
  52. 01:48:31– Spam Subjectivity & Consensus Rules Debate
  53. 01:51:08– Objective vs. Subjective: Mempool Policies as Good Rules
  54. 01:53:10– No Hard Fork: BIP 444's Low Adoption & Hash Rate Doubts
  55. 01:54:41– Cultural Conflicts: Ossified Bitcoin & Soft Fork Stalls
  56. 01:55:26– Influencer Consensus
  57. 02:37:56– Bitcoin Prediction Markets: Non-Interactive DLCs & Proxies
  58. 02:38:41– Poly Market UX: Early Exits & Position Transfers
  59. 02:40:03– PSBT Auctions: Non-Interactive Sales Explained
  60. 02:41:48– Agias Protocol: Native Bitcoin Prediction Markets
  61. 02:43:03– Paul Sztorc Story
  62. 02:44:19– Oracle Problem
  63. 02:45:48– Hivemind Insights
  64. 02:46:57– Build Agias
  65. 02:48:39– Predix Collaboration
  66. 02:49:16– Favorite Thinkers: Robin Linus, Liam Eagen
  67. 02:50:24– BitVM's BSV Origins
  68. 02:52:52– Turing Completeness & Craig Wright
  69. 02:54:58– BitVM Evolution
  70. 02:55:24– 2010 Spam Debates with Satoshi & OGs
  71. 02:56:52– Block Size Wars vs. Current Fights
  72. 02:57:28– Nostr Threads with Aaron van Wirdum
  73. 02:58:01– Follow Super: Supertestnet.org
  74. 02:59:03– Infighting Fuels Ethereum & Zcash Growth
  75. 02:59:29– Outro: Thanks to Sponsors & Farewell

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
722f820ce180ccd1aec1efc5e4514d2d2b146422d6d5dcf0f223edbf43e650bf
Proof
2025-11-08_s16_e56_super_testnet_on_papa_swaps_bip_444_prediction_markets.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 8 Nov 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-11-08_s16_e56_super_testnet_on_papa_swaps_bip_444_prediction_markets.mp3 (on a Mac: shasum -a 256 2025-11-08_s16_e56_super_testnet_on_papa_swaps_bip_444_prediction_markets.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2025-11-08_s16_e56_super_testnet_on_papa_swaps_bip_444_prediction_markets.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-11-08_s16_e56_super_testnet_on_papa_swaps_bip_444_prediction_markets.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