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 · E6 · 2:29:39

S16 E6: Super Testnet on Monero vs Lightning Network Privacy

4 Feb 2025 · by Vlad Costea · 12 min read
Published at block 882,315
Cover art for S16 E6, Super Testnet on Monero vs Lightning Network Privacy
MP3 (206 MB)

The audio keeps playing while you browse the site.

Read the transcript26,577 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 found a darknet market that accepts Lightning and posted it, a listing for chocolates that were not quite chocolates. Then he went further and argued in public that the Lightning Network is more private than Monero, which is the kind of sentence that gets a Bitcoin developer surrounded online very quickly. I invited him on to defend it.

He did, for two and a half hours, live, in front of a chat full of Monero users who were not shy about pushing back. Super Testnet is a pseudonymous developer and educator who seems to ship a new project every few weeks, from Lightning tools to state chain experiments to his own testnet. He is also unusually honest about the limits of what he knows. Several times during the episode he stopped mid-sentence because he was not sure a claim was true and did not want to finish it. That habit made this a better debate than most of the ones I see on Twitter.

I came armed with the usual objections: thin liquidity for big payments, invoices that reveal too much, "private" channels that are not private, custodial wallets everywhere. His argument turned out to be more careful than the headline, and most of the episode was him walking through exactly which party learns what.

Four Kinds of Privacy

I broke the question into four parts: sender privacy, receiver privacy, amount privacy and network-level privacy. Which does Lightning have? "It has aspects of all four," he said. "I think the one it's the worst at is amount privacy and then it's really good at the other ones."

The sender side is the easy case. Lightning payments travel through onion-encrypted routes, so each hop knows only its immediate neighbors, and the recipient at the end, in his example Kraken, knows only that "Dave forwarded this payment to us." I had used exactly that property when I sold bitcoin to buy my car, sending through Lightning so that whatever blockchain analysis Kraken ran would not flag coins that had once been through a CoinJoin.

The receiver side is where his argument got provocative. "I think that Lightning invoices have better privacy than Monero stealth addresses," he said. In Monero, the sender derives the one-time address the money lands on, so the sender knows exactly where the funds went. In Lightning, the pubkey in an invoice is only used for communication, and the sender never sees which channel or HTLC the money ends up in. If someone subpoenas you, "you can honestly say on Lightning, I don't even know, even if I kept logs, I wouldn't have that information." That, he argued, is how investigators work Monero cases: they ask swap services like MorphToken or FixedFloat which address a payment was sent to.

On amounts, Lightning does not broadcast payments to a gossip network at all, so only nodes on the route see anything. Multipath payments split amounts into shards, which means a routing node only learns a lower bound. Fifty dollars passing through might be one fifth of a $250 payment.

What Monero Gets Right

To his credit, Super Testnet spent as much time praising Monero as attacking it. He likes its non-interactive decoys, which he compared to CoinJoins without the coordination, and the encryption of amounts with "a really cool encryption standard that has a property called perfect blinding." He likes the wallet convention of ignoring a second payment to the same one-time address, because it means nobody reuses addresses. "So thank you, Monero for making good privacy tech," he said.

His critique was about two specific leaks. First, the ring of 16 is obscurity rather than encryption. "Obscurity is good, but in my opinion, encryption is better." Second, the fee is public, and in the leaked Chainalysis video that circulated the year before, the analysts use the fee to tell exchanges from ordinary users. Lightning, he noted, hides the total fee too: routing nodes know only what you paid them.

He also gave fair credit to full-chain membership proofs, the upgrade Luke Parker has been building for Monero, which would make the anonymity set the entire chain instead of 16 outputs. He told Luke to call it "Oops! All Decoys," after the cereal. "It sounds like a wonderful piece of technology," he said, and promised to redo the comparison once it ships. Then he asked whether Lightning's encrypted senders achieve something similar, since any Lightning wallet could have created the blob a routing node sees. Later he conceded it is "definitely not" the same thing, only that it has a similar effect.

I asked why he compared Lightning to Monero instead of Zcash, which already has stronger cryptography. He admitted he had not thought about Zcash when he wrote the post, and suspected it was subconscious: "it's more useful to win over the Monero users, because there's more of them."

Dandelion, Tor and the RPC Leak

Network-level privacy was where the chat pushed hardest. Monero has Dandelion++, which Bitcoin wallets could copy without any consensus change. "Just copy-paste, cheat, and that would be great," he said. On Lightning, about 70% of routing nodes run over Tor according to Clark Moody's dashboard, which he credits largely to node-in-a-box products like Umbrel and Start9. And a non-routing Lightning node does not gossip its IP address at all. "So people like to say, you know, a Lightning invoice doxes your IP address. It doesn't. Unless you're a routing node."

His sharpest point was about how mobile Monero wallets broadcast. Many use remote procedure calls to a server instead of joining the peer-to-peer network, and Dandelion++ only protects peer-to-peer relays. In the Chainalysis video, he said, about a third of the transactions the analysts clicked on had been sent to servers owned by or partnered with Chainalysis. A viewer objected that every wallet talks to some node. Super Testnet's reply was that there are two ways to talk to a node, and the RPC way "leaks a lot of information." His conclusion for Monero users was blunt: run your own node and use Tor.

Another viewer argued that LSPs plus KYC would destroy Lightning privacy. He disagreed: an LSP cannot tell whether you are an end user or a routing node. Custodial Lightning wallets are a different story. Use one and "you're only getting recipient privacy." When I showed him my Phoenix wallet, he gave it a mixed report: good receiver privacy, no amount privacy because Phoenix hands the whole payment to its own node to route instead of splitting it into sender-built shards, and an "I don't know" on sender privacy. He used the moment to ask Phoenix to implement sender-constructed multipath payments.

Reading the Chainalysis Fine Print

I put Chainalysis's December 2021 announcement on screen, the one titled "Chainalysis Launches Support for Lightning Network as Layer 2 Payment Protocol Gains Popularity," as the obvious gotcha. Super Testnet read the fine print live. The product is KYT, a compliance screen for exchanges. "It's not tracing the transaction," he said. "They're just checking if the pubkey listed in the Lightning invoice that you give them is on the OFAC list or not. It's a pass fail."

Then he turned it around. Chainalysis sells a Monero tracing tool, and from about the 30-minute mark the leaked video shows a custom Monero block explorer fed with off-chain data from swap services, which lets analysts eliminate decoys one by one. The trail in that video ends with a user who broadcast through an RPC server without a VPN. "People will say it's overblown, they can't really trace Monero," he said. "But if you watch the video, they trace Monero." On Lightning, there is no public transaction graph to start from: investigators would have to subpoena every routing node, and even then the sender is encrypted. "I think it would have been safer if he was using Lightning than if he used Monero."

The caveat, which he repeated, is that neither system is plug and play. A careful Monero user needs a node and Tor. A careful Lightning user needs a node, Tor and discipline. "As long as you're going through the trouble of doing that setup, why not do the Lightning setup and get better privacy?"

Citrea, Drivechains and Ossification

Because LayerTwo Labs sponsored the show, I asked about Paul Sztorc's Core Untouched Soft Fork. Super Testnet loves it. His read is that miners have not activated BIP 300 because they do not want to run Paul's fork of Bitcoin Core. The CUSF approach lets them keep running Bitcoin Core while a sidecar program rejects blocks and transactions that break the BIP 300 rules. "I think that's a brilliant idea," he said. (Paul explained the design himself in Season 15, and LayerTwo Labs publishes the enforcer code.)

On ossification he did not hedge. "I think it already happened. I don't think Bitcoin will ever see a soft fork again, or a hard fork." He thinks that is bad, because ossification "means you stop fixing problems." When I played the devil's advocate and said he just wants a paycheck, he cheerfully agreed. "Well, they're not wrong about the latter. I am trying to get a paycheck. So you caught me."

Citrea also sponsored the show, so I asked about his old fight with them. His memory was hazy and he said so. He recalled objecting that Citrea's website claimed the first ZK rollup on Bitcoin when, in his view, it had posted one proof of one block, and that Orkun Kilic answered by asking how many blocks a blockchain needs. "And I had to concede only one." He still did not have a good feeling about Citrea, and allowed that part of it might be jealousy. That is as candid as sponsor talk gets on this show.

More broadly, he likes rollups but is frustrated that BitVM teams are building EVM clones. He thinks a BitVM sidechain needed only SHA-256 and a Merkle tree, and that "all these smart people chasing Ethereum" is a waste. The one Ethereum contract he would happily import is Tornado Cash, whose pool model he prefers to CoinJoin because it is non-interactive. He was working on a Bitcoin coin pool with some of the same properties, to be demoed at btc++ in Floripa.

Shopstr, BOLT 12 and a Muscle Car

We then went shopping. Shopstr pulls Nostr classified ads from relays and lets buyers pay over Lightning, and the Tor instance he showed me counts, in his view, as a darknet market because a few listings were for drugs. Most were not. I saw an Atari 2600, a Canon camera, a Kindle Paperwhite and an iPhone priced in sats. He warned there is no escrow: if a seller never ships your banana taped to a wall, "all you can do is leave him a bad review." He had also persuaded the Shopstr developers to drop the login requirement for buyers. For me, it looked a lot like XMR Bazaar, where I once bought a Nintendo 64.

On BOLT 12, he was unimpressed with the privacy claims. A decoded BOLT 12 invoice still has a pubkey, and the network address it supposedly hides is already private in BOLT 11 unless you run a routing node. "I think BOLT 11 has really good recipient privacy," he said, while granting that a reusable payment string is nice to have.

Then the personal stuff. He lived in a tent for a year and was living in a hostel in Guadalajara when we spoke. He had been swimming two hours a day since December 30 on a 1,300-calorie diet. He once owned a Chevrolet Monte Carlo, "a muscle car for mass adoption" with a throttled engine. When I told him about the KYC trouble I ran into after selling bitcoin by the book, his advice was a single word: "leave."

Witness Two and Free Workshops

I closed with my usual question about block size. His answer was a proposal I had not heard before: a 16x increase through a soft fork, using a new witness field. "Create a new witness field and call it witness two." Old nodes would simply never download it, so inscriptions and other data could go there for those who want it. When I asked whether that data would be less valuable, he answered with the subjective theory of value and a line I told him to print on a t-shirt: "Options are good."

His backlog of project ideas is an eight-page Google Doc, which he shared on screen. It included a Polymarket-style prediction market on Bitcoin built on state chains, which he believes needs no soft fork and adds only the oracle as a new trust assumption. He also sold his workshops on Shopstr for $5 each, next to a link to the same workshop for free. "I like information to be free," he said.

By his own account, Super Testnet's case holds for a disciplined user who runs a node, uses Tor and stays away from custodians, and he admitted there is "no plug and play solution for privacy on the Lightning Network." What he did well was replace slogans with specifics about which party learns what, and when, and promise to rerun the comparison once full-chain membership proofs arrive. Whoever wins the argument, that is a better conversation than the one Twitter usually has.

If you want more of Super Testnet, start with his episode with Shinobi on projects that suck and the improving Bitcoin roundtable with John Light and Alexei Zamyatin. For the Monero side, my conversation with Riccardo "fluffypony" Spagni is the natural counterweight. His code lives on GitHub.

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

Time stamps:

  1. 00:00:48– Introducing Super Testnet
  2. 00:01:08– Lightning on Dark Web Markets
  3. 00:01:40– Lightning Network Privacy Features
  4. 00:02:02– Analysis of Sender and Receiver Privacy
  5. 00:03:07– Onion Routing Explanation
  6. 00:04:36– Invoice Privacy Comparison
  7. 00:06:08– Transaction Visibility in Monero?
  8. 00:07:12– Information Storage in Lightning
  9. 00:08:10– Liquidity and Large Transactions
  10. 00:09:34– Amount Privacy in Lightning
  11. 00:11:25– Private Channels in Lightning
  12. 00:13:59– Routing Nodes and Privacy
  13. 00:15:08– How Monero Transactions Work
  14. 00:16:01– Encryption Standards in Monero
  15. 00:17:54– Recipient Privacy in Monero
  16. 00:18:52– Privacy Tech
  17. 00:19:02– Network Level Privacy
  18. 00:19:44– Tor Usage in Lightning Network
  19. 00:20:07– Routing Node Configuration
  20. 00:21:00– Dandelion++
  21. 00:21:22– IP Address Association in Lightning
  22. 00:22:50– Encryption in Lightning Transactions
  23. 00:23:18– Monero's Network Privacy by Default
  24. 00:23:40– Chainalysis Video Reference
  25. 00:24:38– Remote Procedure Call Limitations
  26. 00:26:31– Custodial Solutions and Privacy
  27. 00:28:08– Privacy Advantages of Mints
  28. 00:29:53– Full Chain Membership Proofs
  29. 00:31:52– Encrypted Senders in Lightning
  30. 00:32:30– Comparison with Zcash
  31. 00:34:05– Barriers for Lightning Network Adoption
  32. 00:35:02– Exploring XMR Bazaar
  33. 00:36:03– SideShift
  34. 00:37:14– Paul Sztorc's Core Untouched Soft Fork
  35. 00:38:27– Drivechains Activation
  36. 00:41:09– Ossification of Bitcoin
  37. 00:41:51– Concerns About Ossification
  38. 00:42:35– ZK Rollups Discussion
  39. 00:45:05– Citrea’s Zero Knowledge Proof Rollup
  40. 00:48:34– Community Concerns on Lightning Network
  41. 00:50:23– Chainalysis and Dandelion Protocol
  42. 00:52:39– LSP and KYC Privacy Issues
  43. 00:53:28– Receiver Privacy in Lightning Network
  44. 00:54:15– Phoenix Wallet Setup
  45. 00:55:30– Sender Privacy Concerns
  46. 00:57:10– View Key and Monero
  47. 01:02:08– Chainalysis and Lightning Network
  48. 01:06:01– Monero Tracing Capabilities
  49. 01:07:02– User Input Error in Privacy
  50. 01:10:56– The Lightning Network vs. Monero Privacy
  51. 01:12:00– Conference Plans in Romania
  52. 01:14:36– Monero Payment Channel Network
  53. 01:15:21– Full Chain Membership Proofs
  54. 01:15:32– Lightning Network and Sender Encryption
  55. 01:16:22– Stablecoins and Lightning Network
  56. 01:18:05– Monero Transaction Validation
  57. 01:18:56– Zero Knowledge Proofs in Monero
  58. 01:21:04– Rollups and Bitcoin Scalability
  59. 01:23:46– Trojan Horse Concept in Bitcoin
  60. 01:25:36– Tornado Cash vs. Coinjoin
  61. 01:27:34– Coin Pool on Bitcoin
  62. 01:29:13– Darknet Market Listings
  63. 01:29:34– Nostr and Classified Ads
  64. 01:30:50– Privacy in Darknet Transactions
  65. 01:31:54– Risks of Direct Payments
  66. 01:32:43– Exploring Shopstr Listings
  67. 01:35:00– Comparing Shopstr and XMR Bazaar
  68. 01:37:13– Privacy Improvements in Shopstr
  69. 01:44:42– Lightning Network Developments
  70. 01:48:24– KYC and Banking Issues
  71. 01:48:59– Introduction to Bank Privacy Issues
  72. 01:49:48– Financial Regulations in Romania
  73. 01:50:12– Advice on Relocation for Financial Privacy
  74. 01:51:03– Intrusiveness of Banking Regulations
  75. 01:51:34– Personal Experience with Banking Scrutiny
  76. 01:52:13– Living Arrangements
  77. 01:53:16– Lightning Network Implementations Privacy
  78. 01:54:03– Privacy Implications of Lightning Wallets
  79. 01:54:57– User-Friendliness of Lightning Wallets
  80. 01:56:29– BOLT 12 and Privacy Claims
  81. 01:57:09– Improvements in BOLT 12
  82. 01:59:30– Critique of BOLT 12's Privacy Features
  83. 02:00:15– Super Testnet’s Current Projects and Work Focus
  84. 02:01:30– Development of Mint Market Cap Tool
  85. 02:02:30– Title Transfer App and State Chains
  86. 02:03:32– Ensuring Security in State Chains
  87. 02:04:26– Nostr Wallet Connect Protocol
  88. 02:05:40– Creation of Faucet Generator
  89. 02:06:36– Creating a Testnet
  90. 02:07:12– State Chains Discussion
  91. 02:08:14– Prediction Market Concept
  92. 02:10:14– Project Backlog Overview
  93. 02:12:29– Super Testnet’s Music Career
  94. 02:14:39– Upcoming Conferences
  95. 02:15:41– Coin Pools Advantages
  96. 02:17:25– Planning Conference Attendance
  97. 02:17:56– Workshops and Commitments
  98. 02:19:08– Health and Fitness Journey
  99. 02:20:13– Should Bitcoin Increase the Block Size?
  100. 02:21:04– Soft Fork Proposal
  101. 02:22:47– Market Value of Transactions
  102. 02:24:02– Workshop Availability
  103. 02:25:14– Social Media Presence
  104. 02:26:02– Scams and Fake Accounts
  105. 02:26:39– Social Engineering Tactics
  106. 02:27:34– Money Requests Clarification
  107. 02:27:58– Social Links and Resources
  108. 02:28:28– Audience Engagement
  109. 02:29:01– Closing Remarks

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
3a6e99e6eadf17e07042d90bb481b3ff0ab020f6ec330c4bba6d8fadf31db21b
Proof
2025-02-04_s16_e6_super_testnet_on_monero_vs_lightning_network_privacy_-_04.02.2025_20.16.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 4 Feb 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-02-04_s16_e6_super_testnet_on_monero_vs_lightning_network_privacy_-_04.02.2025_20.16.mp3 (on a Mac: shasum -a 256 2025-02-04_s16_e6_super_testnet_on_monero_vs_lightning_network_privacy_-_04.02.2025_20.16.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2025-02-04_s16_e6_super_testnet_on_monero_vs_lightning_network_privacy_-_04.02.2025_20.16.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-02-04_s16_e6_super_testnet_on_monero_vs_lightning_network_privacy_-_04.02.2025_20.16.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