The Holy Grail of Crypto Privacy: Encrypted Ethereum, FHE & Living Forever

Key Concepts

• Confidentiality vs. Privacy: Confidentiality is a broader term encompassing the protection of sensitive data, which can include personal data (privacy) as well as other types of non-public information.
• Public Verifiability: The ability for anyone to recompute and verify the state of a blockchain, which historically necessitated public data.
• Homomorphic Encryption (HE): A type of encryption that allows computations to be performed on encrypted data without decrypting it.
  • Fully Homomorphic Encryption (FHE): A more advanced form of HE that allows for an arbitrary number of operations on encrypted data.
• Zero-Knowledge Proofs (ZKPs): Cryptographic methods that allow one party to prove to another that a statement is true, without revealing any information beyond the truth of the statement itself.
• Multi-Party Computation (MPC): A cryptographic technique that allows multiple parties to jointly compute a function over their inputs while keeping those inputs private.
• Trusted Execution Environments (TEEs): Secure areas within a processor that are isolated from the rest of the system, designed to protect sensitive data and code.
• Zama Protocol: A protocol designed to add a layer of confidentiality to existing blockchains, enabling private transactions and smart contract interactions.
• ERC-7984: A proposed standard for confidential tokens, aiming to enable interoperability for confidential assets across different privacy technologies.
• Longevity and Biohacking: Practices and research focused on extending human lifespan and improving healthspan.

Summary

The Privacy Problem in Blockchain and the Need for Confidentiality

The discussion begins by highlighting the inherent privacy problem in current blockchain technology, where all data is publicly visible. This public nature, while enabling public verifiability, is seen as a significant drawback, akin to displaying one's bank account to anyone. The speaker, Rand, argues that this was an artifact of technological limitations from the past, not a fundamental design choice. While early privacy solutions like Zcash utilized Zero-Knowledge Proofs (ZKPs) for confidential transfers, they lacked composability, limiting their application to simple transfers. This led to exploration of other techniques like Fully Homomorphic Encryption (FHE), Multi-Party Computation (MPC), and Trusted Execution Environments (TEEs) to create shared private states for DeFi and other blockchain applications.

The conversation touches upon potential reasons for the initial public nature of blockchains, including technological limitations, lack of demand for privacy, and regulatory concerns. Rand suggests that while tech limitations were a factor, the demand for privacy has always existed, but users lacked options. The analogy of the shift towards end-to-end encrypted messaging (SMS vs. Signal/Telegram) is used to illustrate how user adoption of privacy features can be rapid once the technology becomes readily available and offers comparable or superior functionality.

Defining Confidentiality and Privacy

A distinction is made between "privacy" and "confidentiality." Privacy is specifically related to personal data (e.g., bank accounts, DNA), while confidentiality is a broader term encompassing any data that is not public, even if it's not personal. Confidentiality is presented as a superset of privacy.

Zama's Vision: Confidentiality for Every Blockchain Transaction

Rand's project, Zama, aims to bring confidentiality to every blockchain transaction, not just Ethereum. Their approach is to build a layer of confidentiality on top of existing blockchains, rather than creating a new private chain. This allows users to maintain the benefits of existing ecosystems, such as Ethereum's liquidity and security, while transacting confidentially. The goal is to make using blockchains feel like using Ethereum, but with privacy, integrated directly into existing wallets and applications, akin to the seamless integration of HTTPS for web browsing.

Cryptographic Families and Their Superpowers

The discussion delves into different families of cryptography:

1. Classic Cryptography (Bitcoin/Ethereum): Includes hashes and signatures (e.g., ECDSA) for security, authentication, and integrity.
2. "Moon Math" Cryptography (Advanced Techniques):
   • Zero-Knowledge Proofs (ZKPs): Used for proving statements without revealing underlying data (e.g., Zcash, Tornado Cash, Railgun, Aztec). While excellent for privacy and scalability, ZKPs lack composability for on-chain computation.
   • Multi-Party Computation (MPC): Primarily used for key management and secret sharing (e.g., Fireblocks, Coinbase wallets). It allows for decentralizing private keys, but doesn't scale well for complex computations due to communication overhead. Zama uses MPC for the decryption phase of its protocol, splitting the decryption key among reputable entities like Ledger and Fireblocks.
   • Fully Homomorphic Encryption (FHE): Enables computation on encrypted data without decryption, offering programmable privacy. This is the core technology Zama leverages for its computation layer.

Rand posits that the optimal blockchain stack for privacy, verifiability, and composability is: FHE for privacy, ZK for scaling, and MPC for key management.

FHE vs. ZK for Blockchain Privacy

Rand argues that FHE is the superior technology for bringing privacy to existing blockchains due to its ability to provide security (even against quantum computers), public verifiability (by re-running computations), and crucially, composability. While ZKPs are effective for privacy and scaling, they do not offer the same level of composability needed for complex smart contract interactions.

Addressing Criticisms of FHE

Rand addresses criticisms regarding FHE's integrity and scalability:

• Integrity: He clarifies that integrity for FHE computations can be achieved by leveraging existing blockchain consensus mechanisms, fraud proofs, or even ZK proofs for verification, similar to how smart contracts on existing blockchains achieve integrity.
• Scalability and Performance: Historically a bottleneck, FHE performance has improved significantly, with Zama claiming a thousand-fold increase in speed. They are on track to achieve 10x year-on-year improvements and are developing dedicated ASICs for FHE, aiming for 100,000 TPS on a single machine. This addresses concerns about high computational requirements and potential centralization.

Zama's Construction and Security Model

Zama's protocol involves two main components: computation and decryption.

• Computation: Performed using FHE, allowing smart contracts to operate on encrypted data. This part benefits from existing blockchain integrity mechanisms.
• Decryption: Handled by a threshold decryption scheme using MPC, where a key is split among 13 reputable entities. A two-thirds majority is required for decryption. This model aims to mitigate the risk of a single point of failure or malicious actor.

Rand acknowledges the concern about trusting these entities but emphasizes the high bar for collusion (two-thirds of 13 reputable companies) and the implementation of hardware enclaves and encrypted communication to further secure the process. He likens the internet's reliance on a few DNS root servers to this model, suggesting it's a practical approach to achieving a high level of security.

Programmable Compliance and the 99% Use Case

Zama focuses on providing tools for developers to build compliant applications. They do not force a specific privacy model but allow token issuers to programmatically define compliance levels, enabling features like user-controlled data access and issuer visibility, mirroring traditional finance compliance. Zama aims to serve the "99%" of legitimate financial use cases, not illicit activities.

The "Privacy Season" and Institutional Demand

The recent surge in interest in privacy solutions (dubbed "privacy season") is attributed to the increasing institutional adoption of blockchain for finance. Financial institutions require confidentiality for their on-chain activities, driving the demand for privacy technologies.

Regulatory Landscape and Developer Safety

The conversation touches upon the challenging regulatory environment for privacy developers, citing cases like the prosecution of a private Bitcoin wallet developer. Rand's approach is to build Zama as a tool for developers to implement confidentiality, rather than offering a direct privacy feature, thus shifting compliance responsibility to the application layer. He believes that the demand from institutions will eventually drive regulatory clarity and acceptance of encrypted financial transactions.

Zama's Mainnet Launch and Use Cases

Zama is launching its mainnet on Ethereum in early December, with multi-chain deployment planned for 2026. Initial use cases include:

• On-chain Banking (e.g., Rayash): Enabling confidential stablecoin balances and transactions within self-custodial on-chain banking applications, offering protection against central bank failures.
• Confidential Vesting and Token Distribution: Allowing crypto teams to distribute tokens and manage vesting schedules confidentially, addressing the private nature of salary and compensation information.

The Future of Confidential Tokens and User Experience

Zama has developed the ERC-7984 standard for confidential tokens, aiming for seamless integration into existing wallets and DeFi protocols. The goal is for users to have a "confidentiality button" within their wallets, allowing them to shield assets without bridging to separate chains or complex procedures. This is seen as a significant improvement over current privacy solutions that often require bridging or are less user-friendly.

The Zama Protocol Flow

1. Shielding: Users convert existing tokens (e.g., USDC) into confidential tokens via a smart contract on Ethereum, incurring standard gas fees.
2. Confidential Transaction: To send confidential tokens, users encrypt the amount using Zama's public key and generate a ZKP to prove correct encryption. This process incurs a small fee paid in Zama tokens to the Zama protocol operators.
3. Decryption: Users pay a small fee to the Zama protocol to trigger MPC threshold decryption, allowing them to view their confidential balance.

The Zama token is a utility token used for fees and rewards for operators. Operators are incentivized through staking and token rewards, with slashing mechanisms governed by the community to handle issues like downtime or malicious behavior.

Longevity and Biohacking Interests

Rand shares his personal interests in longevity and biohacking, including achieving a low "longevity score" (indicating slower aging) and his involvement with competitive biohacking. He discusses his approach to optimizing health through sleep, diet, exercise, and supplements, aiming for a biological age younger than his chronological age. He also mentions his plan B of cryopreservation.

The Future of Privacy in Crypto

Rand predicts that by 2026, privacy and confidentiality features will become mainstream, integrated by default into wallets, exchanges, DeFi protocols, and stablecoins, representing a significant net benefit for all users.