Fully Homomorphic Encryption

An encryption method that lets arbitrary computations run on ciphertext, producing the same result as on plaintext.

Fully homomorphic encryption (FHE) is a cryptographic technique that enables arbitrary computations to be performed on data while it remains encrypted. The key idea is that a party can process ciphertext and produce a new ciphertext which, once decrypted by the data owner, matches the result that would have been obtained by computing on the original plaintext.

How FHE works conceptually

Traditional encryption protects data at rest and in transit, but typically requires decryption before any meaningful processing can occur. FHE changes that workflow. A user encrypts data and sends it to a server, smart contract environment, or analytics provider. That provider runs supported computations directly on the encrypted inputs and returns an encrypted output. Only the user, or whoever holds the decryption key, can decrypt the final result.
In practical terms, this means sensitive information can stay confidential even while being used. For example, an exchange or wallet service could compute risk checks, limits, or scoring functions on encrypted customer attributes, returning an encrypted decision without ever seeing the underlying personal data.

Relevance to crypto, blockchains, and privacy

Blockchains are transparent by default, which is useful for auditability but challenging for privacy. FHE is explored as a way to keep data hidden while still enabling computation, such as encrypted voting, private identity checks, sealed-bid auctions, or confidential analytics over on-chain and off-chain data.
FHE is related to, but distinct from, zero-knowledge proofs. Zero-knowledge proofs are often used to prove a statement about data without revealing it, while FHE focuses on performing the computation itself on encrypted inputs. It is also different from confidential computing, which relies on trusted hardware, whereas FHE relies on cryptography.
FHE matters in the crypto ecosystem because it offers a path to building applications that preserve user confidentiality while retaining programmability, which can help reconcile privacy, compliance needs, and open verification.