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
S15 · E62 · 1:37:22

S15 E62: Josh Swihart & Kris Nuttycombe on Zcash, Zero-Knowledge Proofs & Cash for the Internet

6 Nov 2026 · by Vlad Costea · 22 min read
Published at block 974,769
Cover art for S15 E62, Josh Swihart & Kris Nuttycombe on Zcash & Privacy
MP3 (134 MB)

The audio keeps playing while you browse the site.

Read the transcript15,073 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

I announced an episode about Zcash and the replies wrote themselves. Why do you still care? It is a failure. It is a shitcoin. It has been around for eight years and the chart does not care. "Apparently the metric to measure the success of something is just the price," I said at the top of the recording, which is how a lot of Bitcoin Twitter decides whether a piece of cryptography is allowed to exist.

So I sat down with Josh Swihart, CEO of the Electric Coin Company, and Kris Nuttycombe, a Zcash core developer, to talk about the thing the price chart cannot see. This was November 2024, eight years after launch, with Cake Wallet joining as a new sponsor alongside SideShift, Hodling.ch and LayerTwo Labs. If Zcash did not "win," what did all that work actually buy?

Josh did not start with a candle. He started with Satoshi. "Satoshi's kind of belief was that having pseudonymity would be sufficient for privacy," he said, "without kind of recognizing all of the capabilities that would be developed to be able to tag and trace." The same Satoshi, he added, "very famously stated that if he could figure out how to get zero knowledge to work on Bitcoin, it would be better." That line was a dare to a handful of academics. Zero-knowledge proofs were theoretical math, a way of proving statements, with no obvious practical application. A group of them figured out how to do it, took the idea to Bitcoin Core, and heard what Josh still thinks was probably the right answer at the time: the cryptography was too novel, too computationally intensive, and it came with a trusted setup that made people skittish.

Zcash launched anyway, as "this grand experiment" asking whether you could add encryption to Bitcoin and make it work. The two projects then walked in opposite directions. Bitcoin's story moved "from peer-to-peer electronic cash to digital gold," with ETFs and number-go-up attached. ECC stayed with the original job. "That's not what we're here to build," Josh told me. "We're here to build tools for financial freedom, allow people to transact peer to peer."

Kris put the same point in cash terms. "We still don't really, in widespread adoption, have cash for the internet," he said. You cannot have it "on a system where your bank balance is connected when you buy anything." You need privacy and unlinkability from one payment to the next. The trusted setup is gone now, and the breakthroughs that enable recursive proving are on the table. "There are now options for how to build this out at scale," he said, "to really make that thing that we want, which is cash online."

A Blessing, a Curse, and a Wallet You Can Actually Use

A lot of people still talk about Zcash as if 2016 never ended: slow proofs, desktop nodes, a transparent chain that looks like Bitcoin with extra steps. I remembered Amir Taaki going on about Halo and a mixing pool he wanted for DarkFi. He was looking forward. Most of the timeline commenters were not.

Josh called the transparent T-address "both a blessing and a curse." Because Zcash uses a UTXO model, exchanges could list it the way they list Bitcoin. That got coins into the world while the hard cryptography was still being made performant, including the HSM and curve work exchanges would eventually need for shielded support. The curse is the meme that followed: Zcash is "not private by default," a line that tracks the historical volume of transparent transactions more than the current design. For years you simply could not create a shielded proof on the devices people actually carry. "I think we've still got a road ahead to make those transparent addresses obsolete," Josh said, "so nobody wants to use them" and unified addresses, the Z-address family, are "completely pervasive."

The regulatory excuse is thinner than it sounds. "Folks like Gemini support sending to a shielded address and NYDFS is fine with it," he said, meaning the New York regulator. Some people still argue that transparent outputs are required for compliance. He did not buy that as a complete story.

Kris added an engineering reason I had underweighted. Because the cryptography was so novel at launch, "having the transparent pool available also as a fallback in the case that there were problems with the cryptography" was a decision that "made sense at the time." Viewing keys now let you share what happened in a wallet with relatively fine-grained permissions, and there are even finer techniques for disclosing a single transaction. "The time is coming," he said, "where, like Josh said, transparent addresses will just be obsolete." They mattered to get here. They do not have to matter forever.

I had treated transparent addresses as an exchange-and-regulator hack. Kris corrected the frame. "Zcash was the first production deployment of zero-knowledge proofs," he said. You see them everywhere now, including in Ethereum apps that "all build on the work that the engineers at ECC and the Zcash Foundation did to make zero-knowledge proofs practical." At launch, "it was truly an experiment. We didn't really know whether it was going to work."

The user experience finally caught up. Unified addresses and shielded sends now run on something as small as Zashi on a phone. Kris said they were "just now really getting to a point where it's usable enough that [we] can really onboard a broader variety of users and not just the most hardcore." Zashi had an active Coinbase integration so you could buy ZEC straight into the wallet, and an upcoming Flexa integration in testing that would let you spend it "when you go to buy a burrito."

Six Laptops in a Desert, Then No Trusted Setup at All

Zcash's origin story is the opposite of a flame war. I contrasted it with Monero, which began in conflict (a disputed leadership, a fork from Bytecoin's child, a community that learned to fight). Zcash was closer to: put some of the sharpest people in a room and see if the math works. I am biased. I own one of the props.

On the call I held up Peter Todd's compute node from the first trusted setup, one of six machines used to generate the original parameters. I bought it from him after he destroyed the CPU and everything that had touched the computation: Faraday cage, back seat of a car, a drive across Canada, data on DVDs, then a meeting in the desert where they wrecked the computers. Years later I had him unbox that same ceremony laptop on camera. Peter also had a legitimate complaint: everyone used a single software implementation, which he did not think had been audited enough.

Josh filled in the rest of the cast. "There were two ceremonies, the initial one with six, and actually I would love to get Edward Snowden's computer. He's got that for sale somewhere." Snowden was a participant. "Nobody knew who each other was." Radiolab later covered Zooko's part in it. That first rite created Sprout, the original shielded pool, "really not performant." The next ceremony was Powers of Tau, for Sapling, which still had a trusted setup but let you create proofs on smaller devices. Then came Orchard, "based on Halo 2," which "doesn't require any trusted setup" and can do the recursive proofs Kris had been hinting at.

The chart did not throw a party for any of this. Josh had a more specific scar: 2018, Equihash, ASICs. "I think the Antminer was the first, from Bitmain," he said. The community discussed changing the parameters the way Monero did. They voted, through a process the Foundation hosted, not to. "Personally, looking at it in hindsight, I think it was a mistake." Hobby miners disappeared. A lot of ASIC operators converted inventory to Bitcoin "because they're in it for the money." Zcash has the same issuance curve as Bitcoin, so a huge amount of new coins hit a broken market in the first four years. "In my opinion [it's] way undervalued for the technology that's there," he said. "This story, we're still infants."

Not a Zero-Sum Game

Mid-episode I had to read the ads, including the new one from Cake Wallet. Before the taping I messaged Vik, Cake's CEO, about an old, messy Zcash integration that looked from the outside like a cancellation. He said he was open to it and sent his hellos. Privacy projects that should be natural allies have a habit of punching each other in public.

Monero, I said, had spent years slamming Zcash and was now preparing to take something from it: full-chain membership proofs, so the anonymity set would no longer be a handful of decoys (I said about 17) but something closer to the whole chain. Josh treated the borrowing as good news. "It's not so tribal. We wouldn't want another project that is bringing freedom to the world to be damaged." They are "rooting for the best tools available."

Kris was sharper about the heat. "This is not a zero-sum game," he said. All of crypto is tiny next to fiat. Private crypto is tinier still. "The more options that we get of privacy-preserving cash for the internet, the better it is for everyone." ECC had collaborated with kayaba and with the Penumbra team. "Recently the Penumbra [team] hired ECC developers to do an audit of Penumbra code." The meme that you can only win if someone else loses, he said, is "ridiculous." Regulation and "the powers that be that would like to have visibility everywhere" are the actual common risk.

I pointed out that the whole privacy scene loves a flame war, the same reflex you used to get between Samourai and Wasabi. Kris separated honest technical argument from "bad-faith trashing of competing projects." Josh was happy to say the quiet part: "We think Zcash is the best option for electronic cash, like hands down, like no competition."

The Most Influential Project You Are Not Supposed to Like

The first time I read about zero-knowledge proofs in a serious way, it was because of Zcash. I later found the idea sitting, very theoretically, in Bruce Schneier's early-1990s Applied Cryptography, a book Sergio Demian Lerner has talked about learning from. I am not aware of another project that spent this much time and money making that chapter run in production. So I flattered them, on purpose. ZK rollups are being built on Bitcoin (I talked through that later with Orkun Kılıç about Citrea) and on Ethereum, which if anything has taken more of the lesson. Paul Sztorc wants a Zcash sidechain, privacy by default, if drivechains ever land, and he did not pick Monero for that experiment. I think Zcash is the most influential project in the room right now, which is an awkward sentence to say on a Bitcoin podcast.

Josh walked through why the first version was so hard. The proofs had to be non-interactive, which is where SNARKs come from, and that is why they needed a trusted setup. "Maybe two dozen people around the world understood how to spell ZK." Then other people took the work and ran. Kris described the feedback loop: implementation teaches you the next theoretical step. "That's how we went from Sprout, which required minutes on high-end machines to do proofs, to Sapling, which requires seconds on mobile phones," and from there to "Sean Bowe's revelations about how to get rid of the trusted setup and create Halo 2."

I asked the nervous question: so few people understand this that a bug could break everything. Kris said that worry is permanent in cryptography, and that "there is a formal proof of security for the Halo 2 protocol." The Zcash team, he said, has been "relentless" about those proofs through every upgrade. Josh would not sell a fairy tale. In Sprout, "there was a bug in the underlying math and it was in the paper, it was buried in the paper," and if someone had found it they "would have [been] allowed to counterfeit Zcash." An ECC cryptographer found it by going back to the paper, not by staring at application code. It was fixed in Sapling, then disclosed to every project they knew was using the same cryptography "without having checked all the way back down to the bottom." The other side of that risk is incentive. This is money. "There's a little bit of a Lindy effect here," Josh said. Bitcoiners still treat an undetectable inflation bug as the knockdown argument against privacy, while staying oddly relaxed about institutions selling paper bitcoin. Kris did not think Monero's decoy model gave you more certainty, especially as full-chain membership proofs move Monero toward a Zcash-style design.

Then I asked why Ethereum seems to have hugged this research harder than Bitcoin has. Some StarkWare fans had told me STARKs would make Zcash obsolete by living on a busier network. Josh disclosed that ECC was an early investor in StarkWare and still was. Eli Ben-Sasson, StarkWare's founder, was one of Zcash's founding scientists. "Great guy, great project." Their focus had been scalability more than private cash, and Josh saw the proving layer as fairly centralized: "you've got to run those servers, the StarkWare servers." He had not seen them push STARKs as internet cash. Kris's answer to obsolescence was shorter. "It's really hard to obsolete something that is continuing to evolve and innovate."

I could not resist the cruel comparison. A meme coin that takes five minutes to launch on Solana can get more market action than a decade of SNARK research. Josh called that use case "kind of bunk": pump a token, dump it on somebody else. What they are trying to do is "a Gutenberg moment for money." Bitcoin and Satoshi opened the press. Privacy is the unsigned pamphlet, the ability to publish without putting your name on the sheet. You can spend your one life on Dogwifhat, he said, or on something that changes things for the next generation. "I can look at the price chart and I can say the market doesn't care, but the world will care."

Kris does not even really watch the casino. Meme coins, to him, are the same zero-sum reflex: make a buck by taking it from someone else and leave nothing behind. "You can't have an economy, you can't build an economy on transparent coins." "We are in the early days of the implications of internet cash. We haven't really started yet." I floated the maximalist endgame in which only 21 million bitcoin survive as money. Kris reached for ecology: "Monocultures fail. Monocultures always have weak spots." Josh piled on that you would not have practical zero-knowledge at all if Bitcoin had been the only permitted culture. "It's like saying we're going to have one book and it's going to be the Bible."

Why Zcash, then, and not Zerocoin, or clones that advertise themselves as Zcash without a trusted setup? I named Pirate Chain. Josh noted that they "used the Sapling parameters" and had been shielded-only, without a transparent pool. (Ycash tried different rules and never found a mainstream audience.) Open source means anyone can copy the code. Survival, he said, is "up to people and what they want to choose." Kris's test is simpler: watch where the innovation is coming from, "and who's copying it." "We see Monero adopting Zcash tech." The day before our recording they had held an online birthday celebration, and the ecosystem did not look like a ghost chain: Zcash Shielded Assets almost ready for Network Upgrade 7 the following year, Sean Bowe now on scalability, "the brightest minds in the industry still pushing forward on problems that the whole industry has."

The Dev Fund Is a Social Contract, Not Zooko's Grocery List

This is usually where Bitcoin Twitter mentions the Foundation, the Electric Coin Company, and a meme about paying for Zooko's groceries. Miners, in that telling, are being robbed to fund a company. I said the quiet counter: miners sign up for a visible social contract, they can leave, and the work product is not imaginary.

Kris treated it as philosophy, not PR. Bitcoin's founding contract sent new issuance to miners. Zcash's early observation was "we don't want to do a huge premine," because a premine is a one-time shot later arrivals cannot opt out of. An ongoing dev fund is different. If miners decide "the value that we're getting from the development funding is [not] sufficient, then they can go elsewhere. This is competition. This is part of a healthy ecosystem." They had just authorized another year of funding starting that November, still 20 percent of issuance. The first four years went to a small pool. The next four (their next halving was "just in a little bit less than a month") split the slice among the Zcash Foundation, ECC and Zcash Community Grants. The Foundation built Zebra, the second node they wanted the network to move toward. ECC kept zcashd and the proving research. For the year ahead, Community Grants would still get a slice, and the rest would go into a pool "not under the control of a single entity," pending a community governance process "that's still being argued about."

"It's not a scam if it's transparent," I said, "when people know what they sign up for and it's part of the social contract and the users agree, or they can exit." I also said something ruder about how little research Bitcoin miners have funded, and how often the same crowd that praises other companies will look at Zcash's output and then try to bring the good parts home. That argument has not gotten quieter since.

The culture complaint I cannot drop is older than the fund. Bitcoin maximalism used to mean stealing every good idea and, after enough caution, putting it in Bitcoin. The current mood is closer to: if this group did not build it, disregard the merits. People like Robin Linus working on BitVM and shielded transactions on a ZK rollup still struck me as the interesting path, and a lot of that path runs through work Zcash already paid for.

"The Best Surveillance Coin Ever Invented"

When I tell bitcoiners that Bitcoin needs privacy, a common shrug is: I withdrew from an exchange to a fresh hardware-wallet address. Nobody knows it is mine. Random hex. Good enough.

Kris took that one. "It's not a random address. It's the address that you withdrew to from the exchange." The exchange knows you. Any later counterparty can see that the coins came from that withdrawal. Change coming back to a new address gets re-linked the next time you spend it. "All of that history is so incredibly linkable." If any one of the people or companies you interacted with can tie an identity or an IP address to your wallet, "you are traceable, you are known." Then the line he clearly wanted on the record: "Bitcoin is the best surveillance coin ever invented. It is the best currency for surveillance. You get more privacy from transacting through your bank than you do when transacting with Bitcoin."

He had a concrete picture. There is a coffee shop in Boulder that accepts Zcash. Pay with ZEC and "that coffee shop doesn't even know my address... they see nothing of my history." Pay with bitcoin and they can see how much you hold and who else you transact with. Scale that to a business and every vendor watching every other vendor: "There's no way that you can build an economy when all of that history is public." Fungibility dies the same way, two degrees from someone who did something ugly, with law enforcement walking the whole graph. I have written about the limitations of Bitcoin privacy before. Privacy degrades even if you mine the coinbase yourself: you do not know when the person you paid will be forced to identify every input, or when you leak an xpub to a third-party service.

Kris said Zcash development is done "perpetually with an adversarial view." If you submit a transaction to a light-client server without Tor, your IP address just created a Zcash transaction, so they made Tor submission possible. Even showing the fiat price of ZEC took a long time, because they did not want the wallet talking straight to an exchange. It contacts a mix of data sources over Tor and takes a median. "Every step of the way there are possible leaks," and the worst ones glue themselves to "publicly visible stuff on an immutable blockchain." Bitcoin transactions "are public forever."

I asked the obvious follow-up about Zcash's own transparent history. If coins later move into a shielded or unified address, does that old trail vanish? "There's some nuance here," Kris said. The way to obtain true privacy, "not specific to Zcash," is "to store your wealth in private." If you send 3.14159 ZEC from the transparent pool into the shielded pool and send almost the same amount back out a few hours later, someone can match the fingerprints. "People trying to just use the shielded pool as a pass-through don't actually gain benefits of privacy." The same trick fails on Monero if you enter and exit with an identifiable amount. Store the wealth shielded, and later spends are "unlinked from any public information," unless you hand someone a viewing key. The history is not something an observer can reconstruct from the chain alone.

Would it have been nicer to start private-by-default? Yes. Is it still better than Bitcoin, and getting better? Also yes. I floated the other cope: Bitcoin privacy will happen on second layers, so the base chain can stay a glass house. Kris said it depends who those layers are, what they can see, and how they settle back to the main chain. "I think that Zcash has implemented the best privacy that's possible to have on the internet with money today." That does not mean nobody else can recreate it. It does mean settlement and the layer-two operator's view are not details. Josh was not impressed by Ethereum's layer-two mess as a model. "We're going to continue to build scalable privacy on L1 with Zcash."

They are even willing to run the movie in reverse. With Zcash Shielded Assets you could imagine zBTC: bitcoin bridged over, stored and spent privately. "Maybe the evolution goes the other way around," Josh said, "where instead of Bitcoin gaining privacy, privacy gains Bitcoin." I laughed, because WBTC was already bigger than Lightning and Liquid. The first-mover chain that could have integrated everything chose narratives and institutions instead. That is a big part of why I still do this show.

On the decentralization jab (only two or three funded teams, a double point of failure) Josh did not puff his chest. "I agree." He pointed to growth: Shielded Labs, a new Swiss organization, with Zooko newly involved on product and Jason McGee as executive director, funded by third-party donations rather than the dev fund. Independent people were building shielded assets and extra wallets and infrastructure. Early ZK had required a tiny, highly qualified team. "This is changing."

They had about an hour. After a Hodling.ch read I took questions from the live chat, which was already huge: later I thanked something like 950 people, most of them on Twitter.

ToastyJoe wanted to know whether the recursive zero-knowledge theory that ebfull (Sean Bowe) had found years earlier was implemented, or even on the roadmap. They already had a trustless proving pool, but scaling, the question implied, still wants recursion. Kris said Sean was now fully on scalability and he was "pretty confident that the recursive proving is going to be part of that." "Not implemented yet in Zcash," partly from resource constraints. "I see that coming."

Marius asked about quantum resistance, Zcash as a hedge. Josh started with the big picture. If quantum computers break cryptography in general, "we've got much bigger problems, because it's going to break the internet." Transaction history itself is not sitting on the chain as plaintext waiting to be decrypted. The proofs use cryptography to convince verifiers without publishing the secrets. There is an encrypted memo field, and there is other machinery around the protocol that will want post-quantum primitives. Daira-Emma Hopwood, on the ECC team, had been looking at that. "Your privacy, in terms of your transaction, will be protected." Kris added the nuance. "Zcash is post-quantum resistant for the note encryption so long as someone doesn't know the address that the note was sent to." If they already know that a specific transaction went to a specific address, "we don't have full post-quantum privacy." That pairing is not something the chain reveals by default.

Then came proof of stake. I mentioned that Slush Pool, the first Bitcoin mining pool, had supported Zcash for years, and that Zooko wrote about Bitcoin days after launch as Chaumian e-cash done without a center. The project has always had one foot in Bitcoin. So what was this move? "It's a proposal," Josh said, "that has momentum and I think broad support in the ecosystem." Not a full cutover: a hybrid of proof of work and proof of stake called Crosslink. Shielded Labs, with Zooko, was taking point. The early research had been done at ECC by Daira-Emma and Nate Wilcox, with a prototype hoped for within about twelve months. Kris explained the security pitch: an attacker who wants to rewrite history would have to subvert both sides at once, "which is harder than subverting one or the other individually." Josh said ViaBTC had "about 60 percent" of Zcash hashrate, and people in the ecosystem also wanted a way to earn yield on ZEC while helping to secure the network.

Josh added a reason that does not get enough airtime: "I move in some spaces where there's a strong anti-crypto sentiment, and a lot of that is about environmental costs." The risk that people will try "to regulate proof of work out of existence" is "maybe underrated by the pure proof-of-work chains." I pushed back that proof of work is the fairest way to acquire coins, using electricity and machines you already have. "Ideally that's true," Kris said. In practice, especially in Bitcoin, economies of scale, cheap power and volume hardware discounts are "a centralizing force, not a decentralizing one."

I said I still admire the people who kept mining Zcash. Bitcoin without privacy, pushed to global adoption, is a prison we built ourselves and then defend because we recognize the bricks. I thought about Sergio Lerner looking at Satoshi's coins under the Patoshi theory, and the Bitcointalk chorus telling him not to, as if fungibility were a gentleman's agreement.

Someone in chat asked whether Zcash needs a Michael Saylor figure. Josh's first reaction was "oh dear lord," then the version of Saylor who tells people to give up self-custody and keep everything at regulated entities. "This is not what we're trying to build." They did not need that kind of capture, or that kind of savior. "We're going to build great tech and build a great community and hope the community carries it forward." The questioner clarified: they meant a bullish mouthpiece. "Wouldn't hurt," Josh said. He knows there are Zcash whales, some public, "others that are choosing to remain private, and I would love for them to get up and speak... but they don't want to. It's their right. It's a right to privacy." Awareness helps. It is not the mission. "We're here [to] build electronic cash."

I thanked them for the pragmatism, for not bending the knee to the people who want no privacy and the people who want nothing except Bitcoin. If you want to follow along, Josh pointed to @zcash (they had to get the handle donated), @ElectricCoinCo, the Foundation, @Zashi, himself at @jswihart, and Kris at @nuttycom. I later sat down with Josh again for S17 E28, and with Kris again for S17 E49. In November 2024, the assignment was still the original one: cash for the internet, built in public, with no savior required.

None of this was financial advice. A listener sent 0.0069 ZEC to the wallet on stream, called me a name, and added a pointing emoji and a clown. Kris, dry as ever, noted that "at least there's an economic cost to it." It was a fitting last image: a project that has been declared dead more times than I can count, still answering questions at the end of the hour.

Listen to Josh Swihart & Kris Nuttycombe on Spotify, Apple Podcasts, YouTube, and More

Time stamps:

  1. 00:00:00– Intro & Sponsors
  2. 00:00:50– Introducing Josh & Kris
  3. 00:01:44– Criticism of Zcash
  4. 00:02:18– Origins of Zero-Knowledge Proofs
  5. 00:04:00– Technological Challenges
  6. 00:05:45– Need for Internet Cash
  7. 00:07:01– Radicalization & Maximalism
  8. 00:08:19– Evolution of Zcash Addresses
  9. 00:09:00– Transparent vs. Shielded Addresses
  10. 00:12:14– Misconceptions About Transparent Addresses
  11. 00:13:12– Zcash's Unique Development Story
  12. 00:14:04– The Trusted Setup Ceremony
  13. 00:15:35– Price and Perception Issues
  14. 00:17:18– Impact of ASIC Miners on Zcash
  15. 00:18:21– Market Dynamics and Tokenomics
  16. 00:19:30– User Experience Developments
  17. 00:20:54– Integration with Wallets
  18. 00:23:51– Historical Context of Zcash
  19. 00:24:34– Community Collaboration
  20. 00:25:40– Zero-Sum Game Myth
  21. 00:27:14– Toxicity in the Privacy Space
  22. 00:29:13– Influence of Zcash
  23. 00:31:18– Technical Challenges and Innovations
  24. 00:32:48– Implementation Insights
  25. 00:34:15– Concerns Over Security
  26. 00:36:43– Cryptographic Challenges and Disclosure
  27. 00:37:49– Privacy Concerns in Bitcoin
  28. 00:38:34– Engineering Confidence in Zcash
  29. 00:39:44– Zcash's Relationship with Ethereum
  30. 00:41:53– Competition and Innovation in Crypto
  31. 00:42:29– Market Perception of Meme Coins
  32. 00:44:00– The Gutenberg Moment for Money
  33. 00:46:35– Zero-Sum Mindset in Crypto
  34. 00:49:10– Diversity in the Crypto Ecosystem
  35. 00:51:12– Zcash's Competitive Edge
  36. 00:53:39– Innovation within Zcash
  37. 00:55:03– The Evolution of Bitcoin Maximalism
  38. 00:57:01– Technological Edge and Zcash
  39. 00:59:25– Development Funding and Governance
  40. 01:01:38– Transparency in Social Contracts
  41. 01:02:51– Linkability of Bitcoin Transactions
  42. 01:05:06– Privacy Challenges in Bitcoin
  43. 01:06:28– Degradation of Bitcoin Privacy
  44. 01:08:00– Adversarial Design in Zcash
  45. 01:10:31– Tracing Transparent Zcash Transactions
  46. 01:13:25– Future of Bitcoin Privacy
  47. 01:14:27– Zcash Shielded Assets
  48. 01:14:47– Bitcoin's Privacy Evolution
  49. 01:15:56– Zcash's Potential
  50. 01:16:36– Decentralization Concerns
  51. 01:17:07– Growth of Zcash Community
  52. 01:18:01– Audience Questions
  53. 01:19:11– Recursive DHDC Implementation
  54. 01:20:02– Quantum Resistance
  55. 01:22:10– Proof of Stake Proposal
  56. 01:23:02– Security Enhancements
  57. 01:26:15– Environmental Concerns
  58. 01:27:14– Mining vs. Proof of Stake
  59. 01:28:22– Zcash's Future
  60. 01:30:44– Zcash's Michael Saylor Figure
  61. 01:31:29– Community Building
  62. 01:33:21– Long-term Perspective
  63. 01:33:58– Closing Remarks and Gratitude
  64. 01:35:26– Encouragement to Follow Zcash Developments
  65. 01:36:05– Disclaimer and Listener Engagement
  66. 01:36:36– Humorous Interaction and Trolls
  67. 01:37:04– Economic Cost of Spam

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
1cab91b7714c0512d2eb4253a8bb33b43c98a0989ef29fb67d4f4380bb84b9d9
Proof
2024-11-01_s15_e62-_josh_swihart_kris_on_zcash_-_01.11.2024_22.13.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 1 Nov 2024, 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 2024-11-01_s15_e62-_josh_swihart_kris_on_zcash_-_01.11.2024_22.13.mp3 (on a Mac: shasum -a 256 2024-11-01_s15_e62-_josh_swihart_kris_on_zcash_-_01.11.2024_22.13.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2024-11-01_s15_e62-_josh_swihart_kris_on_zcash_-_01.11.2024_22.13.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 2024-11-01_s15_e62-_josh_swihart_kris_on_zcash_-_01.11.2024_22.13.mp3.ots shows the block height to look up in any block explorer.

Share: X · Email · Link

Comments

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

0:000:00