Key takeaways
- Panther Protocol uses zero-knowledge proofs to enable privacy and compliance in DeFi through partitioned zones with individual compliance programs.
- Institutions require privacy protections to prevent competitors and data analytics firms from extracting trading information and strategies.
- Privacy-native tokens like Monero face institutional adoption barriers due to regulatory scrutiny and lack of integration with existing financial workflows.
- Regulatory clarity has shifted from surveillance-resistant privacy toward compliant privacy solutions that allow zone managers to set their own AML programs.
- Panther's multi-chain infrastructure addresses institutional needs for both privacy protection and regulatory compliance in tokenized asset trading.
Privacy and compliance in one stack
Ashton Addison: What are you and your team building at Panther Protocol?▶ 00:40
Oliver Gale: Panther has been in development for three and a half years. My co-founder and I have been building a team and a protocol with the vision of enabling compliance and privacy in onchain finance. Over that time there has been a major shift in regulatory approach, in the direction we thought at inception was inevitable. Privacy is very much needed, particularly for power users like financial institutions. And unstoppable privacy was not going to be embraced, or even allowed, in most markets. Panther builds onchain financial tools that use ZK-SNARKs for confidentiality, but which also partition the protocol into zones. Zone managers set their own AML programs, custody data, onboard users and interoperate selectively with one another. You end up with a heterogeneous cloud of zone managers, each with its own jurisdictions, user bases, use cases and compliance programs, and yet they can share users and transactions. We're close to mainnet. Early Panther evangelists would remember a focus on unstoppable privacy and surveillance resistance. We still hold those core values, but the implementation now focuses on providing multi-chain infrastructure to anyone with a financial institution license, a market and a go-to-market strategy.
Ashton: Why is blockchain transparency a problem for institutions, and what has to be solved before they come on chain?▶ 03:43
Oliver: Crypto has been around for well over a decade, and banks and institutions have been tracking it. It can no longer be ignored or written off. The requirements for entering are fairly universal: trust, security, and a service that is affordable and useful and can generate revenue. Then comes the question of whether you are allowed to do it. Outside the scope of all licenses is where most DeFi sits today, and that's been the biggest blocker to institutional adoption. Many privacy protocols have focused on private tokens, which Panther does not, and they have been delisted from exchanges and barred from usage. If you solve compliance, you face a trade-off. You inherit the network effects, composability, innovation and inflows of capital and new users. But everything you do is transparent. Arkham, Nansen, Elliptic, Chainalysis and other data analytics firms are adversarially extracting information and trading against you. With real-world assets arriving, the question is how to make DeFi compliant and protect your alpha. Panther addresses both problems.
Ashton: Why not just use a privacy coin like Monero?▶ 07:43
Oliver: An institution could technically accept Monero, but it would have to do a source-of-funds check. That's equivalent to carrying a big bag of cash to a bank and asking to deposit it. They will have questions, it will be highly scrutinized, and if you don't provide the tools and integrations, you change people's workflow. That's a real disincentive. It's what has happened with privacy-native tokens and projects that don't enforce honest behavior. Panther takes a different approach. There is a shielded pool, it is partitioned into zones, and every zone manager can configure and control their own zone. Our business development conversations have gone very well, particularly around tokenized assets. It's unacceptable for someone who owns LP shares in a fund to have that information disclosed to the market. Privacy is a right, but there are also practical economic drivers. I might lose money if people counter-trade or front-run my entries and exits. We take a chain-agnostic approach, but our fundamental bet is that pseudonymous public blockchains are the prevailing standard, because network effects like Ethereum's and Solana's will be very difficult to overcome.
Outside the scope of all licenses is where most DeFi sits today, and that's been the biggest blocker to institutional adoption.
How verification and trading work
Ashton: How does Panther handle compliance while keeping user data private, and what does the Purify partnership add?▶ 12:10
Oliver: The Purify partnership was completed last year. Its purpose was to enable the first compliance layer for access to Panther V1, which is slated for a Q1 launch, though Q1 to Q2 is a timeline I'm quite comfortable with. V1 has one zone. It is DAO-controlled and requires strict KYC and AML, including transaction monitoring limits and user verification. Purify aggregates traditional finance compliance tools and provides them onchain. We built the ZK circuits for the Purify team to prove and verify, for example, that a user is over 18 and that the submitted ID and selfie were verified. We use ZK-SNARKs so this happens without disclosing the underlying data. The user self-verifies directly with Purify, and a zero-knowledge proof is generated through the Panther protocol. The user then submits that proof to access the Panther zone. By default the protocol has not collected any information. The data is stored in a data vault controlled by the DAO and secured with multi-party computation. If there is an enforcement action, or licenses are required later, the user's data can be disclosed so that business as usual can continue. Purify is one KYC and AML vendor. We are in discussions with other digital identity providers and with institutions that don't want to change their compliance systems at all. If a licensed institution says its users are verified, Panther generates a credential, and those users can access DeFi by submitting it in a zero-knowledge fashion.
Ashton: What would it look like for an institution to put a large amount of capital into a Panther zone?▶ 18:52
Oliver: The institution either sets up its own zone under its own licenses, or it becomes a customer of someone else's zone, such as a broker with brokerage and custody licenses. Either way there has to be KYC or KYB. It can be done in advance for existing customers, or as the wallet connects. Step one is connect the wallet, step two is select your verification method. Nothing really changes from what AML compliance looks like in traditional finance today. Once inside, you deposit assets through the interface. They are self-custodied: the institution controls them, not the protocol, and there is no third-party custodian. You receive a one-to-one representation of the asset. Panther manages a subledger in which every user has an account with balances and a transaction graph, and that graph is protected by ZK-SNARKs. We've built adapters into Uniswap, ParaSwap and Curve. We focus on DEXs because swapping is the first use case, and building into existing protocols lets us tap their liquidity. Institutions need liquidity before they're even interested in the conversation. Onchain, you see Panther contracts interacting with those protocols. The institution doesn't pay gas, because bundlers cover execution costs, which would otherwise de-anonymize the actor. When the institution takes assets back to its native wallet, it withdraws to a clean address, so the linkage between deposit and withdrawal addresses is broken. The information is not lost. It's just confidentially and securely custodied with a regulated institution. The zone manager has access to the transaction data and can carry out AML transaction monitoring.
ETFs, adoption and the road to mainnet
Ashton: What do the Bitcoin ETF approvals mean for institutions moving into DeFi and for Panther?▶ 26:16
Oliver: The spot Bitcoin ETF approval in US markets is a massive achievement. It was a fantasy of bitcoiners a decade ago. It's the biggest signal yet that Bitcoin is being adopted as a global monetary system, and it happened despite staunch opposition from the SEC. Many people who swallow the Bitcoin pill don't come back out. They end up investigating the blockchain technology that powers it. Once institutions see there is a regulatory path to adoption, a spot ETH ETF is very likely to follow, and applications have already gone in for a Solana spot ETF. We have these discussions in practice all the time. Institutions are in the middle of tokenizing real-world assets and find the compliance or privacy systems lacking on their chain. One option is to migrate to another chain without the same liquidity and services. That's what permissioned chains run by banks attempted, and they've had no success gaining network effects. Our pitch is that you keep your compliance systems, your data storage and your user journey. What changes is the linkage onchain, because we break the transaction linkage. You maintain your licenses and reporting, and we deploy on any blockchain where it makes sense.
Ashton: Where do mainnet and the testnet stand?▶ 32:33
Oliver: We've regretted putting timelines on things in the past, because dependencies come up. Stage three of the testnet was delayed because libraries were missing and had bugs our development team had to find. We were wrong about when we'd release it, but that's behind us. The testnet has nine phases, and stage three was more or less the heaviest lift, so stages four through nine should be faster. Last year there was a lot of re-architecture and research. We published papers on using monomial SNARKs to make proving times 140 times faster for cross-chain messaging. Q1 is the target for V1, and Q1 to Q2 is a reasonable time frame. We've focused on communicating what we did last week, what we're doing this week and what's next, rather than promising dates. The testnet is incentivized, so testers are rewarded in ZKP for helping us find bugs and process improvements. The way to get involved now is to join the community, ask questions and start testing.
The information is not lost. It's just confidentially and securely custodied with a regulated institution.
This interview has been edited for length and clarity. Recorded January 2024.

