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 · E5 · 4:12:39

S16 E5: Reuben Yap on Firo & ZK Privacy

30 Jan 2025 · by Vlad Costea · 16 min read
Published at block 881,485
Cover art for S16 E5, Reuben Yap on Firo & ZK Privacy
MP3 (347 MB)

The audio keeps playing while you browse the site.

Read the transcript39,690 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

Reuben Yap has been called a scammer so many times that he has a ready answer for it. "I must be a really bad scammer," he told me. "It takes me nine years and I'm still here." He drives a car he says is worth about $2,500, his team lives on 16,000 FIRO a month plus donations, and the coin he has stewarded since 2016 was trading about 99% below its December 2017 peak on the night we recorded.

That last fact was the lowest-hanging fruit of the evening, and I picked it. But the reason I wanted Firo on the show had little to do with price. Firo started life as Zcoin, the first coin to implement the 2013 Zerocoin paper, one of the two academic proposals (the other was Zerocash, which became Zcash) that tried to bolt zero-knowledge privacy onto Bitcoin when the price first touched $1,000. Bitcoin developers judged that cryptography too young. A handful of altcoins decided to find out for themselves, and Reuben's project has now burned through four privacy protocols in the process.

We went live at the end of January 2025, on Chinese New Year. I had made my background red for luck, Reuben showed up in a red shirt, and the Firo logo is red too, which in Chinese markets is the color of a candle going up. It ran for more than four hours. Reuben had also contributed a four-page essay on tribalism, "Moving Past Tribalism, Embracing Diverse Approaches to Privacy in Cryptocurrency," to the privacy magazine I had on my desk, and that essay turned out to be the thread running through the whole night.

From Zerocoin to Lelantus Spark

I asked the obvious question first: what separates today's Firo from Zcash, given that both descend from those 2013 papers? Reuben's answer was that the current protocol "bears, I guess, very little resemblance to the original Zerocoin."

The lineage goes like this. Zerocoin was an RSA accumulator: you burn coins and redeem fresh ones with no transaction history, but only in fixed denominations, which leaks patterns "very similar to like early CoinJoins." Zcoin went live on September 28, 2016, a month before Zcash. Sigma came next and removed the trusted setup, using one-out-of-many proofs from the line of work by Jens Groth and later Jonathan Bootle. Lelantus dropped the fixed denominations, so you could mint 176.3 coins and redeem 13. Then came Lelantus Spark, designed by Aram Jivanyan and Aaron Feickert, with stealth addresses and hidden amounts. In Reuben's words, it delivers "what we want from a privacy protocol, which is hidden sender, hidden receiver and hidden amounts."

The design choice that matters most, as he explained it, is modularity. Zcash proves everything inside "very complicated ZK circuits." Firo stitches together a membership proof, a balance proof and a range proof, each of which can be swapped out. That simplicity, he said, is why Monero researchers took the work seriously and why Seraphis is "based, I would say, largely off our work." Beam built Lelantus-MW on top of the original Lelantus to plug Mimblewimble's transaction-graph leak. A small team, in other words, ended up seeding a whole family of protocols at bigger projects.

The next step he mentioned is full-chain membership proofs for Spark, with help from Luke Parker (kayabaNerve), the developer behind Serai who has also worked on full-chain membership proofs for Monero. Because of the modular setup, Reuben said, it is "actually a bit simpler than it needs to be done on Monero."

When Is Cryptography Ready for Bitcoin?

I asked Reuben when this kind of cryptography becomes boring enough for Bitcoin. Confidential transactions, the amount-hiding scheme Greg Maxwell proposed, are "pretty much ready to go into Bitcoin," in his view, and hiding amounts alone "would already be a huge improvement to Bitcoin's privacy." For something like Zcash's Sapling, his ballpark was "another five to ten years of better testing."

Then he added a twist I did not expect from a privacy-coin founder. All of this cryptography rests on hardness assumptions, and a quantum computer that breaks the discrete log problem would let an attacker print coins and unmask Monero's rings. Using Monero or Firo today, he said, means "you're buying yourself time for the privacy." He thinks that is a further argument for keeping heavy privacy machinery off Bitcoin and letting coins like his take the risk. "Cryptography is always cat and mouse," he said. "You cannot just stay still."

I reminded him that Satoshi used to talk about buying a few years of protection, and wondered aloud how Bitcoin went from that attitude to treating every change as a scam. Reuben's answer came back to the hammer and the screwdriver. One privacy protocol for the entire industry would be "a really bad idea." Imagine "everyone's using the same privacy protocol and that protocol breaks, that would be horrible."

A Frozen Bank Account and a VPN Business

This fight is personal for him. Reuben, a former lawyer, started a VPN business in 2007, and that is how he found cryptocurrency: his banks cut off card payments because they were "not comfortable with VPN," even though the business was legal and paid its taxes. At the time of our interview, one of his biggest bank accounts had been frozen for two and a half months because about $500 had reached him from someone one step removed from a scammer.

"I had to explain to them why I was spending so much money on Magic the Gathering cards," he told me. He hopes privacy coins follow the path of VPNs, which went from suspicious to bundled with your antivirus suite. Meanwhile, he pointed out, banks keep getting caught facilitating money laundering and "no one of significance went to jail," while privacy developers like the Tornado Cash team are prosecuted. Later in the night he compared it to Aaron Day, who was selling health products when the law decided his business was not legal. That, Reuben said, is how people get radicalized.

I told him about buying a Nintendo 64 with Monero on XMR Bazaar, and about my Kraken account getting frozen after I sold bitcoin to buy a car. Reuben's stories went further. He said Zcoin was once used to get donations to Iranians during the floods there, that a Firo community manager in Syria used his earnings to build a solar-powered well pump, and that Venezuelans had mined Firo on GPU rigs to support their families. "They are a class of people that need to be served," he said.

Nine Years of Battle Scars

The history of the project, as Reuben told it, is a list of near-death experiences. Poramin Insom, a Thai developer who studied under Matthew Green (one of the Zerocoin and Zerocash authors) and whom Reuben credits with starting Vertcoin, wanted to build Zerocoin and spent about two years doing it almost alone. Not long after launch, the two founders fell out over money and Poramin's partner left the project. Then, in December 2016, a basic coding error, "missing some equal sign or something like that," let someone create about 400,000 coins out of thin air. That is why Firo's supply schedule ends near 21.4 million instead of 21 million.

Later, a flaw in the Zerocoin protocol itself was exploited by an attacker calling himself Pink Panther. Firo disclosed it to the many projects then using Zerocoin, including PIVX, and asked everyone to patch quietly before going public. One project did not wait. Reuben also admitted that, when his team found the bug, the thought of exploiting every other Zerocoin project to fund Firo "did cross my mind," before they chose responsible disclosure. Getting backstabbed afterwards, he said, shook his moral values. I compared it to Amaury Séchet, who told me on the show that exploiting a Bitcoin inflation bug never crossed his mind. Reuben said he has met Amaury and considers him "one of the good guys."

The 2020 rebrand to Firo, he insisted, was about escaping constant confusion with Zcash and a protocol it no longer used, not hiding history. He now concedes that "in retrospect, it probably wasn't a good idea." There was also the 2018 Thai Democrat Party leadership vote run on the Zcoin blockchain, which he described as about 127,000 votes cast nationwide.

The Price, the Whale and the Masternodes

So, the price. The December 2017 high of $139.77, Reuben said, was "a one off thing" driven by the masternode craze, not privacy. What followed was worse than a bear market. In his account, a seed investor wanted to make masternodes so expensive that only whales could run them, and when the community refused, that investor spent about two years dumping coins at strategic moments, including the day of the rebrand and the day a new privacy protocol shipped, "as a way to say fuck you to us."

Masternodes are a lightning rod, and Reuben asked me directly why Bitcoiners see them as a scam. In Firo's version, 1,000 FIRO of collateral is a Sybil-resistance measure, it can be withdrawn at any time, and there is deliberately no masternode voting, a lesson he says he learned from Dash. I offered the usual objection that it resembles proof of stake. He offered the story of why Firo went hybrid at all: after years of fighting ASICs and then botnets, the team moved to FiroPoW, a ProgPoW-based algorithm for modern GPUs, and discovered that GPU miners had no loyalty. When a pool controlled most of the hash rate and the project begged miners to move, "there was no meaningful shift in hash rate." Firo was 51% attacked anyway. His conclusion: "We were the biggest GPU mining supporters, fair mining, and we spent so much resources on that, but that never was appreciated."

He also prefers a tail emission like Monero's, which Firo has adopted, to betting Bitcoin's long-term security on a fee market. When Ordinals filled blocks with fee-paying data, he found the backlash ironic: small blocks were supposed to create exactly that fee market. "I'm like, wow you know that's so freaking ironic."

Dealing With Binance and MiCA

The part of the episode Reuben most wanted to talk about was regulation, and it is where he takes the most heat from fellow privacy advocates. He thinks the very category "privacy coin" is arbitrary. Under MiCA, coins with "inbuilt" anonymity features are singled out, yet Litecoin with MWEB is not treated like Firo, and Verge, which he said has no on-chain privacy, gets the label because a price-tracking site gave it one.

When Binance, under pressure from MiCA and its settlement with the U.S. Department of Justice, was preparing to delist privacy coins, Reuben used his legal background to negotiate. Wallet-level view keys, he argued, would be worse for privacy, because they would give the exchange visibility into everything that wallet ever did. Binance's real requirement was the ability to refund a deposit to the address it came from. Firo's answer was the exchange address, a new type of transparent address that cannot receive directly from a shielded source. A user unshields to a fresh transparent address and deposits from there.

"I felt that that was a reasonable trade off that satisfied the word of the law," he said. According to Reuben, Binance then asked Zcash and others to do something similar, and Zcash shipped TEX addresses. He claims that without this work, "all privacy coins would have been delisted from Binance." His position on the Monero purists is generous but firm: they are doing what is best for their project, "but don't hate on us who are also trying to find, I would say, a decent compromise." The goal, he said, is to keep privacy from being pushed into "the little corners or niche people."

He was realistic about the alternatives. Most no-KYC swap services rely on centralized exchange liquidity, atomic swaps are clunky for normal users, and Serai's AMM is transparent by design. He was most hopeful about newer swap designs that allow multi-hop routes without both parties staying online.

Dandelion++ and Proofs of Innocence

When I brought the conversation back to the technology, Reuben corrected my description of Dandelion++ right away: it does not hide nodes, it "prevents the correlation of a transaction to a particular IP address." His explanation was the clearest I have heard. Normal gossip spreads a transaction like ripples from a stone dropped in a pond, and an observer can work backward to the splash. With Dandelion++, each node mostly passes a new transaction to just one peer (the stem) until a random roll triggers a broadcast (the fluff). On Firo it adds maybe 20 to 30 seconds and is on by default.

It was proposed for Bitcoin as BIP 156, which annoys me, because it needs no soft fork. Reuben noted the catch: it works well only if most nodes run it.

A viewer asked about ZK-STARKs. Reuben likes their speed and hash-based quantum resistance, but said the proof sizes are "still a magnitude or two larger than even our existing transactions." He was blunter about privacy pools, the Vitalik Buterin-backed idea of proving you are not on a blacklist, as implemented in Railgun. He uses Railgun for stablecoin payments and thinks it is better than nothing, but generating the "proof of innocence" takes about half a minute and raises the question of whose blacklist counts. "I just think it's a horrible way to approach privacy," he said.

Rollups, Spark Assets and Spark Names

I asked whether Firo could ever become a ZK rollup on Bitcoin, the way Amir Taaki has said DarkFi might. Reuben would support it if a good team ran it, and said proposals for a Lelantus Spark layer 2 had been considered. But that would mean effectively abandoning Firo and raising new money. In his darkest moments, he told me, he made peace with a different kind of legacy: "even if Firo dies, our work, our privacy protocols, I think will live on."

The plan he described instead was a private asset layer. Spark assets would let tokens share Firo's anonymity set, so "I don't know whether your transaction Firo, maybe some stablecoin, maybe it's some dot coin or meme coin." Bridged assets would arrive through Confidential Layer, which he said announced Zano first and Firo second. He was candid that Zano is heading in a similar direction, said he has "immense respect" for its team, and said he was happy to see Zano's success after years of struggle. Spark names, announced a few hours before we went live, are on-chain aliases with registration and renewal fees, a first experiment in funding the project with something other than the block reward.

Lightning, Taproot and the Samourai Shadow

The last hour wandered, in the way four-hour livestreams do. Reuben thinks Taproot was oversold as a privacy upgrade, and he described it with a joke about a sticker that I will leave in the audio. He believes Lightning has its place but was never the cure-all it was marketed as during the block size wars, and he said he got so jaded that he stopped following Bitcoin for a long time. Whatever you think of Ethereum, he said, he found "a lot more intellectual honesty" in how its community discussed the limits of its own system.

On the toxic rivalry between Wasabi and Samourai, he said he thought Wasabi's protocol was better, and that it was a shame two teams with the same goal spent so much energy fighting. He worries about the opposite failure in his own corner: privacy maximalists who celebrate criminal use as proof that their coin works. "Privacy should be normalized," he argued, and cheering on ransomware is not how you do it. He also mentioned that he and Poramin had both received Google warnings that a state actor was trying to break into their accounts, which says something about what building privacy software involves.

For all the drama, Reuben does not ask for much. He wants the right to build, the right to fail in public and fix it, and a little less hatred from people who share his goal. "We're building for a future that we don't want to see," he said of privacy coins. It is a strange business plan. As a hedge, though, it is easier to understand every time somebody's bank account gets frozen.

For more from the same corner of the map, try my conversations with David Burkett on MWEB, Josh Swihart and Kris Nuttycombe on Zcash and Kruw on running a Wasabi coordinator. The full corrected transcript of this episode is on its transcript page.

Listen to Reuben Yap on Spotify, Apple Podcasts, YouTube, and More

Time stamps:

  1. 00:00:48– Introducing Reuben Yap
  2. 00:01:35– Reuben's Article on Tribalism
  3. 00:04:29– History of Privacy Proposals Zero Coin & Zero Cash
  4. 00:06:25– Firo vs. Zcash
  5. 00:10:47– Lelantus Protocol Explanation
  6. 00:14:48– Importance of Lelantus
  7. 00:17:33– Testing and Integration of Privacy Features
  8. 00:19:24– Challenges of Confidential Transactions
  9. 00:21:57– Cryptocurrency Features and Use Cases
  10. 00:22:53– Privacy Sacrifices in Scalability
  11. 00:23:48– Introduction of CoinJoin
  12. 00:24:05– CoinJoin vs. Mixing
  13. 00:25:27– Privacy Limitations of CoinJoin
  14. 00:27:35– User Experience Challenges
  15. 00:28:42– Regulatory Concerns for Mixing Services
  16. 00:29:22– Confidential Transactions and Tracking
  17. 00:29:43– Chainalysis and CoinJoin Analysis
  18. 00:30:43– Trust in Cryptography vs. Arithmetic
  19. 00:31:55– Evolution of Privacy Protocols
  20. 00:32:03– Quantum Computing Threats
  21. 00:34:23– Importance of Privacy Innovations
  22. 00:35:48– Historical Context of Privacy Protocols
  23. 00:36:42– Diversity in Cryptocurrency Solutions
  24. 00:37:12– Trade-offs in Cryptocurrency Design
  25. 00:39:49– Acceptance of Experimental Protocols
  26. 00:40:47– Funding and Development Challenges
  27. 00:41:48– Bank Account Freeze and VPN Business
  28. 00:42:57– Challenges with Privacy Perception
  29. 00:43:54– War on Privacy
  30. 00:45:05– Surveillance in Finance
  31. 00:46:09– Building for Financial Freedom
  32. 00:47:18– Monero Purchase Anecdote
  33. 00:52:00– History of Firo
  34. 00:54:04– Founding and Initial Challenges
  35. 00:56:35– Technical Issues at Launch
  36. 01:00:49– Transition and Evolution
  37. 01:01:59– Introduction to Zero Cash Protocol
  38. 01:03:00– Rebranding from Zcoin to Firo
  39. 01:04:03– Political Election on Firo’s Blockchain
  40. 01:06:17– Transition to Spark Assets
  41. 01:07:17– Comparison with Other Projects
  42. 01:10:40– Innovations in DeFi
  43. 01:12:05– MimbleWimble Extension Blocks
  44. 01:16:11– Critique of Liquid and Alternative Solutions
  45. 01:20:23– Real-World Use Cases for Firo
  46. 01:22:03– Discussion on Serving Privacy Needs
  47. 01:23:00– Regulatory Challenges for Privacy Coins
  48. 01:23:39– Defining Privacy Coins
  49. 01:24:08– Regulatory Definitions and Arbitrary Distinctions
  50. 01:25:12– Frustrations with Privacy Coin Classification
  51. 01:26:16– Impact of Regulations on Exchanges
  52. 01:27:02– Personal Experience with Kraken Regulations
  53. 01:28:32– Peer-to-Peer Solutions
  54. 01:29:15– Compliance Burdens on Exchanges
  55. 01:29:41– Banking Compliance Issues
  56. 01:31:36– Monero's Approach to Regulations
  57. 01:32:39– Negotiations with Binance
  58. 01:33:38– Challenges with View Keys
  59. 01:34:41– Exchange Address Proposal
  60. 01:37:11– Navigating Regulatory Requirements
  61. 01:38:17– Zcash's Response to Regulations
  62. 01:39:18– Compromise for Privacy Coins
  63. 01:40:20– Value of Diverse Approaches
  64. 01:41:03– Decentralized Exchanges as a Solution
  65. 01:41:21– The Role of Middlemen in Cryptocurrency
  66. 01:43:24– Liquidity Challenges in Decentralized Swaps
  67. 01:46:00– Innovations in Atomic Swaps
  68. 01:48:08– Price Decline of Firo
  69. 01:52:02– Community Resistance and Market Manipulation
  70. 01:54:55– Sustaining Development Amidst Price Fluctuations
  71. 01:57:50– Reflections on Project Value and Longevity
  72. 01:59:22– Building Through Market Cycles
  73. 02:01:25– Privacy Coins and Future Concerns
  74. 02:02:03– The Importance of Privacy
  75. 02:05:04– Lessons from the Canadian Trucker Protests
  76. 02:06:17– First World Country Realities
  77. 02:08:17– Risks in Privacy Development
  78. 02:09:11– Dandelion++ Protocol Explanation
  79. 02:10:43– Gossip Protocol Vulnerabilities
  80. 02:11:46– Mechanics of Dandelion++
  81. 02:15:34– Comparing Privacy Solutions
  82. 02:17:27– ZK-STARKs Discussion
  83. 02:20:05– Clarifying Bittrex Connection
  84. 02:20:57– Chinese New Year and Symbolism
  85. 02:21:34– Chinese Market Color Symbolism
  86. 02:21:57– Centralization Attempts in Crypto
  87. 02:22:08– Ethereum Classic Development Controversy
  88. 02:23:11– Hostile Environment in Crypto Development
  89. 02:24:32– Resilience Through Challenges
  90. 02:25:13– Community Support and Motivation
  91. 02:26:39– Future of Firo as a Bitcoin Rollup?
  92. 02:27:08– Impact of Privacy Protocols
  93. 02:29:28– Confidential Layer Collaboration
  94. 02:32:01– Spot Names Introduction
  95. 02:34:31– Future Vision for Firo
  96. 02:38:52– Meme Coin Market Dynamics
  97. 02:39:56– Elon Musk's Influence on Crypto
  98. 02:41:41– Discussion on Michael Saylor's Influence
  99. 02:42:13– Bitcoin as Digital Gold
  100. 02:44:32– Concerns about Centralization
  101. 02:45:52– ETF Allegations and CoinJoin Fund
  102. 02:46:35– John Dillon's Influence on CoinJoin
  103. 02:47:42– Dark Wallet Controversy
  104. 02:48:53– Open Source Software Contributions
  105. 02:49:57– Ethical Considerations in Exploiting Bugs
  106. 02:51:01– Amaury Sechet's Integrity
  107. 02:52:20– E-Cash and Alternative Protocols
  108. 02:53:15– The Need for Healthy Market Dynamics
  109. 02:54:20– Concerns Over Bitcoin's Security Model
  110. 02:55:51– Ordinals and Node Operations
  111. 02:57:16– Incentives for Node Operators
  112. 02:58:55– Covenants and Layer Two Systems
  113. 03:00:01– Limitations of the Lightning Network
  114. 03:01:11– Intellectual Honesty in Crypto Discussions
  115. 03:02:07– Centralization in Altcoins
  116. 03:02:12– Discussion on Taproot
  117. 03:03:18– Expectations vs. Reality of Taproot
  118. 03:04:20– Ordinals and Stamps
  119. 03:05:49– Confidential Transactions Impact
  120. 03:06:33– Masternodes and Network Incentives
  121. 03:09:04– Criticism of Masternodes
  122. 03:10:03– Masternodes vs. Proof of Stake
  123. 03:12:25– Mining Centralization Issues
  124. 03:15:50– Mining Distribution and Community
  125. 03:18:06– Governance Challenges
  126. 03:20:32– Evolving Perspectives on Proof of Work
  127. 03:22:51– Proof of Stake vs. Hybrid Systems
  128. 03:23:47– Masternodes and Rewards
  129. 03:24:00– ASICs and Proof of Work
  130. 03:25:48– Centralization in ASIC Production
  131. 03:26:23– Geographical Disadvantages in Mining
  132. 03:27:46– Zcash's ASIC Dilemma
  133. 03:28:01– Zooko and Zcash Origins
  134. 03:29:00– Privacy Pools Explained
  135. 03:30:18– Challenges with Privacy Pools
  136. 03:31:30– User Experience Issues with Railgun
  137. 03:32:58– Blacklists and Compliance
  138. 03:34:32– CoinJoin and User Experience
  139. 03:36:20– Efficiency of CoinJoin Protocols
  140. 03:37:01– Cost of Privacy Solutions
  141. 03:38:05– Lightning Network Experiences
  142. 03:40:28– Profitability of Running a Node
  143. 03:41:47– Yield and Passive Income Misconceptions
  144. 03:42:09– Optimism About Lightning Network
  145. 03:42:50– Lightning Network Use Case
  146. 03:44:03– Debate on Lightning Network's Role
  147. 03:45:01– Centralization Concerns
  148. 03:46:06– Comparative Privacy Technologies
  149. 03:47:17– Bitcoin Privacy Tools Landscape
  150. 03:48:23– Open Source Project Resilience
  151. 03:49:01– Rivalry between Wasabi and Samourai
  152. 03:52:25– Privacy Technology and Centralization Issues
  153. 03:55:16– Legal Precedents and Privacy
  154. 03:59:39– Narratives Surrounding Privacy Tools
  155. 04:02:42– Privacy Normalization vs. Criminality
  156. 04:03:55– Technology and Accountability
  157. 04:05:14– Challenges in Privacy Development
  158. 04:07:11– Firo's Evolution and Name Changes
  159. 04:08:14– Accessing Firo Without Exchanges
  160. 04:09:56– Market Impact of the Interview
  161. 04:10:33– Community Engagement and Follow-Up
  162. 04:12:24– Closing Remarks and Gratitude

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
beb372c7f7a81aa628693a845b5d7e411b298b70f54eee8f385128e4a5ac8a05
Proof
2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 30 Jan 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-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3 (on a Mac: shasum -a 256 2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.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-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.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