Pod Insights Markets Outlook Inside the Race to Fix Zcash's Shielded Pool Vulnerability | Markets Outlook About this episode The bug that tanked ZEC with Josh Swihart.
On today's Markets Outlook, ZODL CEO Josh Swihart joins CoinDesk's Jennifer Sanasie to break down the Zcash vulnerability discovered with the help of AI, including how it was found, fixed, and what it means for the protocol's future. Plus, he weighs in on privacy coins vs. government pushback, formal verification as the new security standard, and why Zcash is more battle-hardened than ever.
-
Timecodes:
00:00 - Zcash Bug Found by AI After Four Years
03:26 - What Went Through Josh’s Mind When He Found Out
04:47 - Could the Bug Have Been Exploited?
05:47 - How the Bug Helps the Zcash Ecosystem
07:27 - Zcash vs. Other Privacy Protocols
09:54 - Will Governments Push Back on Privacy Coins?
11:45 - Formal Verification and Finding Future Vulnerabilities
14:08 - What Other Protocols Can Learn from This
-
Check out CoinDesk's latest episode of Public Keys from the NYSE: https://youtu.be/zn3D_adn6nI
-
Register now for CoinDesk’s Policy and Regulation event on September 24, 2026: https://policy-regulation.coindesk.com/.
-
This episode was hosted by Jennifer Sanasie.
Transcript 0:00 Speaker 00 It was a masterclass in how to handle a security incident. And I think anybody that is working on a protocol or any software like this needs to have a very tight security process,
0:11 Speaker 00 needs to be auditing their code and hammering it with these AI tools, not just by like bug bounty programs where you have random people just looking to cash in, but people that really kind of understand the underlying protocol that can ask very targeted and specific questions.
0:32 Speaker 01 Markets move fast, crypto moves faster. From the floor of the New York Stock Exchange, CoinDesk's public keys tracks the money, markets, and moves shaping digital assets.
1:03 Speaker 01 Josh Swihart, welcome to Markets Outlook.
1:06 Speaker 00 Good morning.
1:07 Speaker 01 Good morning. I got to say, I called you Josh sweetheart at consensus and there was a pretty hilarious reaction to it online. So number one, I'm sorry for calling you Josh sweetheart. But number two, I'm kind of happy I did because we got an amazing meme out of it.
1:23 Speaker 00 Yeah, so I'll take that any day. People can call me sweetheart any day.
1:28 Speaker 01 I know. What a lovely thing for people to call you. All right, we're not here to talk about how much sweetheart you are. We're here to talk about Zcash. And Zcash has been in the headlines a lot over the past few weeks over a bug that was found, a bug that had been there for about four years. AI was able to identify it. Take us back to when that happened and just lay a groundwork for us. What happened?
1:55 Speaker 00 Yeah, so a security researcher, Taylor Hornby, he's he's been around. He was like the electric coin company. Had a security for years, knows the protocol really well. And so I, you know, AI, I would say it's like a combination of human and AI that found the bug. So he's very good. He knows, he knows Zcash, he knows the underlying Orchard Circuit. And he was able to use tools where, you know, he had audited, lots of people had audited the code for years and years and years, had never noticed that this could be an issue. But with with Opus 4.8, which had just come out that day or the day before, he was able to kind of
2:35 Speaker 00 find an issue where theoretically for the exploiter had had found it or or knew about it and knew how to exploit it, could have created additional Zcash in the in the Zcash shielded pool. So he notified my team. So I'm the CEO of Zcash Development Labs, Auto. It's a former ECC team. It's the team that built the cash to begin with, notified three members of of our core team here.
3:11 Speaker 00 They remediated the issue, notified me, and then we went and coordinated a response which included a soft fork
3:21 Speaker 00 about two days later and then a hard fork another 24 hours after that to completely remediate the issue.
3:26 Speaker 01 What's going through your head when you get this notification?
3:31 Speaker 00 Dear Lord. So I was sitting having a cup of coffee on my Saturday morning and our head of research, Dara Emma, called me on Signal. Everything happens on Signal, right? So we have very tight security protocols in terms of who gets notified, when they get notified. So Dara read me in, but as per our protocol, I didn't need to know exactly where the bug was or what the bug was. But I needed to know certain things about it in order to coordinate the response. And so we kind of limit, again, who gets read in, who has information about it, how it works. And so,
4:14 Speaker 00 yeah, it wasn't, it just, you just go into a mode of, okay, you know, what?
4:22 Speaker 00 Kind of where do things sit today? What do we need to do? How do we put the proper response coordinated? In this case, we've got to work with miners and exchanges and people running nodes all around the world. So some folks in China, some people in New York, in order to to remediate it as quickly as we could. And it was pretty amazing. We remediated it within the time that we did.
4:48 Speaker 01 So the bug essentially could have allowed malicious actors to print Zcash in the shielded pool. Is there any way to know if that actually happened?
5:00 Speaker 00 No, there's no way to know that if it actually happened. I think there's certain heuristics, there's certain patterns that you would see.
5:07 Speaker 00 So, you know, generally if somebody had, you know, exploits a vulnerability, they'll kind of sit on it quietly. They'll start to move money out in order, because it's in their own best interest. They don't know who else may have exploited it or found an issue.
5:21 Speaker 00 So we have something in Zcash called a turnstile, which limits the total supply. So it protects the total supply.
5:28 Speaker 00 And so just gave theoretically, we would have seen a different kind of movement or different kind of activity. Likely if somebody had been able to exploit the vulnerability, but but we haven't seen any such thing.
5:41 Speaker 01 And I guess talk me through this, you know, there have been a bunch of headlines. This has been unpacked in several different ways since it happened. But what impact does this have on the ecosystem moving forward?
5:51 Speaker 00 It hardens it. One, number one, with the vulnerability, the manner in which the ecosystem, which is more decentralized than it has ever been, was able to kind of come together to, number one, address the vulnerability. And number two, we're working on a form, what's something, a new protocol that's formally verified, that will be out in in July, and it's across organization, various developers with different groups that are working on this and working on it to make it happen.
6:27 Speaker 00 Formal verification is also new. So while AI was used to assist in finding the vulnerability, AI will be used to assist to ensure this vulnerability doesn't exist or anything like it in the future.
6:41 Speaker 00 And I think so ultimately, you know, we we demonstrated we can very move very fast in a crisis. We can execute very professionally. We're very transparent and both the community and I think the the protocol we even more hardened kind of coming out.
6:59 Speaker 01 Now, I had a guest on the show recently. We were talking about the privacy narrative. He said, you know, there are so many privacy solutions out there and was kind of skeptical of Zcash as the privacy solution to answer all of the privacy challenges that we have. And something he told me was, you know, I don't know a lot of people who have sold their Bitcoin to get Zcash. I'm just, I just want you to respond to that. Tell me a little bit about how you see Zcash in the privacy ecosystem. And for you, what makes it stand out amongst some of the other privacy protocols out there?
7:37 Speaker 00 The irony with that statement, right, is there's data out there. So we enabled swaps from various coins to to Zcash. I think that the top, and you can see when the swaps happen, right? Because half of the transaction is transparent. The people that are coming in from Bitcoin or USDC or Tether or whatever, you can see that coming in and coming into the Zcash shield pool. So the top two coins traditionally that swap into Zach are USDT and USDC. But post that, it's like Bitcoin. And so he can say he doesn't know anybody, but people are doing it. And the data is there to show that. I think he had a whole bunch of replies to that interview where people are saying, I'm, I'm one of them.
8:20 Speaker 00 And actually, I am one of them. Right? So, you know, I started as a Bitcoiner. I was a Bitcoiner long before Zcash existed. And so like, I think that's like, I don't know. It's a narrative he was kind of throwing around. But the reality is like, Zcash has been around since 2016. It was proof of work. So at fair distribution, people have been accumulating or not for a long period of time. It's had price discovery. Typically, price discovery takes about 10 years before you see it. And so you can't recreate that that 10 years of history by taking some tech and throwing it on another chain.
9:14 Speaker 01 Markets move fast, crypto moves faster. From the floor of the New York Stock Exchange, CoinDesk's Public Keys tracks the money, markets, and moves shaping digital assets.
9:30 Speaker 01 Another guest that was on the show recently was a trader, and we were talking about some of the more prominent narratives that are happening right now, and Zcash came up. And while he acknowledged how well Zcash is doing, he said, you know, where he lives and amongst his group, the worry is that governments are not going to be as bought into privacy as the end users. Is that something you think about? What if governments decide, you know what? We don't actually want people using private currency, and we're going to make it really, really hard for them to get their hands on Zcash and use Zcash?
10:06 Speaker 00 I don't think you can put all governments in the same bucket. I think there's some differences. We have somebody that works full time in Washington DC that was out there meeting with people on the Hill yesterday. And I think there's a general openness and a recognition that actually not having privacy is actually a bigger problem. That if all of US citizens are able to be exposed to four powers and hackers and that kind of thing, it's actually a massive, massive economic risk. We saw this with the early days of the internet, right? So the early days of the internet, the government fought encryption on the internet using the same kind of jargon, not jargon, but language of like, we need to protect the children,
10:49 Speaker 00 we need to protect against terrorists and that kind of thing. But the reality is, we couldn't do commerce on the internet. The internet could not exist as it exists today without encryption, without HTTPS. And so because...
11:03 Speaker 00 Because of that, economic forces changed things with the government where now that same government that was trying to kill encryption on the internet now says it's mandated and should be mandated. And I think we are headed to that, to that kind of world. I think that's possible. But at the same time, we need to, where there are governments that are more dystopian or they're more authoritarian, we need access to things like DeFi and things like that where it's just, it's just quite frankly, outside their control.
11:34 Speaker 01 I want to come back to the, the vulnerability. We started this conversation on, I can only imagine that you're, you're there in the war room, trying to figure out what happened, how to fix it and what happens next. How are you thinking about finding other vulnerabilities or protecting against other issues of this magnitude, not being discovered because you want to discover, discover these things. But how are you thinking about protecting the ecosystem and, and finding vulnerabilities and avoiding them?
12:03 Speaker 00 Yeah, there's two things. There's one is simplification. The other's something called formal verification. So historically, something like Orchard, it uses a thing called a circuit, which is kind of a rulebook for how things get managed within the, within the protocol. And that rulebook is very complicated. And historically, it's hand checked. And so you have cryptographers that kind of understands your knowledge of cryptography that are in there, looking at it. You get multiple parties to look at it. You get third party audits to kind of certify everything, all the rules are correct and everything like that. And that's what's been happening for the last four years. And because it's so complicated and so many edge cases, computers historically have not been able to, to do that rule checking,
12:48 Speaker 00 to make sure everything is right. And so what that means is that now we have with, with, with AI tools, we have the ability to formally verify. So that means the AI tool can look at those rules and verify that they're, they're accurate and it's doing exactly what it is supposed to do, exactly what you want it to do essentially. And you can have multiple people that are, that are doing that and the code is all open source. So anybody can go formally verify, work on that. Now there are multiple groups that are formally verifying. It created like this big because of the news. Like I'm sure lots of people were hammering it with AI to see if they could find anything else.
13:28 Speaker 00 And so that will help the formal verification will help. And then you know that a computer has verified that everything is sound. And then the second thing is just to simplify the that that rulebook. And there's a project called Project Tachyon. So the first thing we're doing is with Orchard Pool, which is the current one, we're formally verifying and we'll have an update. Called Ironwood. In the target is the end of July or mid mid to end of July. And then Tachyon, which is the next generation, which will be out some months from now, is a simpler rulebook. And so by both simplifying and formally verifying, I think we can get pretty rock solid.
14:07 Speaker 01 Okay. And lastly, what what can other protocols learn from this experience? How would you advise folks who are running other protocols to operate when it comes to security and finding vulnerabilities?
14:21 Speaker 00 It's like patting my teams on the back a little bit, but it was a masterclass in and how to handle a security incident. And if you don't, and we have again, a very tight process that's well documented.
14:35 Speaker 00 We use tools that are encrypted for how we exchange certain information that gets exchanged. We're not posting information on Google Docs or something like that. That's on somebody's cloud somewhere. Information gets passed very privately as well. And and so we have this process of of how we handle security incident. And I think anybody that is
14:58 Speaker 00 working on a protocol or any software like this needs to have a very tight security process. Needs to be auditing their code and hammering it with these AI tools. Not just by like bug bounty programs where you have random people just looking to to cash in, but people that really kind of understand the underlying protocol that can ask very targeted and specific questions. And so I I think I don't know that that a lot of of groups in the industry have like this kind of security process set up in such a way that that will allow them to kind of effectively remediate and then be able to kind of fully disclose kind of what happened and in the way that we did. But maybe there are, but I but I think. If they don't, they should.
15:40 Speaker 01 Yeah, my hope is, you know, after they see instances like this, that people are reevaluating their systems and taking action before before it it happens again, but
15:51 Speaker 00 Yep.
15:51 Speaker 01 Um, I think we've we've seen that maybe, maybe if it doesn't hit home, people just kind of feel like they're safe.
15:58 Speaker 00 I think they they kind of assume safety. You get you have a tendency to kind of get lazy if something's not happened over some period of time. We've seen like with Litecoin got exploited, um, that, you know, there's all these Bitcoin back in the day got exploited.
16:12 Speaker 00 There is just inherently going to be bugs in software that are created by humans. It's just going to happen. So, um, if you building software, there's a bug there, a question of of how, um, how it can be exploited, how severe it is. I mean, those it it depends, but, um, but now we have these tools that we should be formally verifying,
16:34 Speaker 00 uh, our software before we kind of, uh, there's there's no reason not to, uh, anymore.
16:41 Speaker 01 Josh, thanks so much for joining Markets Outlook today. As always, it was a pleasure.
16:45 Speaker 00 Thank you so much.
Previous Arthur Hayes Sold HYPE and NEAR, Mert Mumtaz Says That’s Missing the Point | Markets Outlook Next Why Arthur Hayes Says Fed Chair Kevin Warsh Is a Dove Despite Hawkish Reputation | Markets Outlook Page updated November 13, 2026 · transcript and summary are machine-generated