Skip to main content
Bankless

The Holy Grail of Crypto Privacy: Encrypted Ethereum, FHE & Living Forever | Rand Hindi, Zama Co-Founder

·
Rand Hindi

Read time

2 min

Topics

Startups, Crypto & Web3, Science & Discovery

AI-Generated Summary

Key Takeaways

  • FHE vs ZK for Privacy: Fully homomorphic encryption enables computation on encrypted data with composability, unlike zero-knowledge proofs which only prove statements without allowing programmable privacy. FHE achieves security, public verifiability, and composability simultaneously, making it optimal for confidential blockchain applications.
  • Shielding Mechanism: Users convert ERC-20 tokens like USDC into confidential tokens through smart contracts on Ethereum, paying standard gas fees plus small Zama token fees for encryption verification and decryption. The process requires no bridging, maintaining Ethereum's liquidity and security.
  • Decentralized Decryption: Thirteen reputable entities including Ledger, Fireblocks, and Layer Zero split the decryption key using multi-party computation, requiring two-thirds majority to decrypt any data. This prevents single points of failure while maintaining cryptographic security against quantum computers.
  • Performance Scaling: Zama currently supports thousands of transactions per second on CPUs, with GPU deployment planned for early 2026 targeting 500-1000 TPS per chain. Custom ASIC chips in development could enable 100,000 TPS on single servers at fraction of current costs.

What It Covers

Rand Hindi explains how Zama uses fully homomorphic encryption (FHE) to bring privacy to Ethereum transactions without bridging to new chains, enabling confidential balances and transfers while maintaining composability and public verifiability.

Key Questions Answered

  • FHE vs ZK for Privacy: Fully homomorphic encryption enables computation on encrypted data with composability, unlike zero-knowledge proofs which only prove statements without allowing programmable privacy. FHE achieves security, public verifiability, and composability simultaneously, making it optimal for confidential blockchain applications.
  • Shielding Mechanism: Users convert ERC-20 tokens like USDC into confidential tokens through smart contracts on Ethereum, paying standard gas fees plus small Zama token fees for encryption verification and decryption. The process requires no bridging, maintaining Ethereum's liquidity and security.
  • Decentralized Decryption: Thirteen reputable entities including Ledger, Fireblocks, and Layer Zero split the decryption key using multi-party computation, requiring two-thirds majority to decrypt any data. This prevents single points of failure while maintaining cryptographic security against quantum computers.
  • Performance Scaling: Zama currently supports thousands of transactions per second on CPUs, with GPU deployment planned for early 2026 targeting 500-1000 TPS per chain. Custom ASIC chips in development could enable 100,000 TPS on single servers at fraction of current costs.

Notable Moment

Hindi reveals he intentionally gained 70 pounds in one year to experience being unhealthy for an AI nutrition startup, then reversed it completely before pursuing extreme fitness optimization with a live-in coach for six months.

Know someone who'd find this useful?

Episode Transcript

It'll feel just like using Ethereum, right? For developers, it'll feel like just like building for Ethereum. Everything is in solidity, and you're pushing your contract to Ethereum. For users, everything's gonna feel like Ethereum. You're using a wallet to make a transaction to Ethereum. And and and that's really how we thought about this. Right? It's we don't want people to use something else. We want people to use Ethereum confidentially. Rand, I think everyone listening to Bankless knows that crypto has a privacy problem. We want privacy. We don't have it yet. Here's how you put it in a recent tweet. You said, go to anyone on the street and ask them to show you their bank account. That's blockchain today. It's obvious we need confidentiality. Why don't we have privacy yet? Well, I think you should look at the history of blockchain. Maybe the first thing we have to understand is why is data public in the first place? The reason why data is public on a public blockchain is because you want public verifiability. If you want anybody to be able to recompute the states, they need to be able to use and see the data that was part of computing that state. And so there was really no other way if you wanted decentralization and public verifiability, but to make the data public. This was never a feature of blockchain, right? It was, It was kind of like an artifact of not having homomorphic encryption in these techniques fifteen years ago. But what you really want is public verifiability. And I think there are many, many attempts to doing that. For example, some early privacy protocols like Zcash, big fan of Zcash. You know, being a long time I've been a long time holder, I'm very happy it's finally happening. It's totally happening. Right? It's one call style. Yes. So Zcash use zero knowledge proofs as a way to effectively prove that you had the tokens that you wanted to transfer. Right? And so in this case, what you would publicly verify was the proof. You didn't need the data. But the problem is that you didn't have composability on this proof. So you were stuck with basically just doing confidential transfers. And I think this is why a lot of other people started looking at other techniques like FHE, like multi party computation, like Tease to try and create this shared private state that you could build DeFi on, that you could build other blockchain applications. For the non cryptographers, Rand just mentioned, teas and multi party computation, all of that. Don't worry. We will define those things. And I hope we will simplify those later in the episode, but let's stick on this for a moment. So I think you're saying, Rand, that the reason we had public blockchains in the first place and they were constructed as such is because we were tech limited. We didn't have the cryptography at the time. …

Get the full transcript (16,802 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Bankless transcripts →

Get Bankless summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

company

  • Thirteen reputable entities including Ledger, Fireblocks, and Layer Zero split the decryption key using multi-party computation
  • ZamaBy guest
    Rand Hindi explains how Zama uses fully homomorphic encryption (FHE) to bring privacy to Ethereum transactions without bridging to new chains
  • SPONSORS: Frax, frax.com/r/bankless
  • SPONSORS: Coinbase, coinbase.com/borrow
  • SPONSORS: Eight Sleep, 8sleep.com/bankless
  • SPONSORS: Mantle, x.com/mantle_official
  • Thirteen reputable entities including Ledger, Fireblocks, and Layer Zero split the decryption key using multi-party computation
  • Thirteen reputable entities including Ledger, Fireblocks, and Layer Zero split the decryption key using multi-party computation

More from Bankless

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Crypto Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Bankless.

Every Monday, we deliver AI summaries of the latest episodes from Bankless and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime