Encryption
Last Updated: November 19, 2026
Encryption is the process of turning readable data (plaintext) into scrambled data (ciphertext) with an algorithm and a key, so that only someone holding the right key can read it.
In crypto, encryption mostly protects the things around the blockchain: wallet files, backups and the connections between your device and an app or exchange. Public blockchains such as Bitcoin and Ethereum do not encrypt their ledgers. Anyone can read every transaction, which is exactly how nodes check them.
How Encryption Works
Encryption uses mathematical algorithms and keys to scramble data. There are two main types. Symmetric encryption, such as AES, uses the same key to lock and unlock data. Asymmetric encryption, also called public-key encryption, uses a public key to lock data and a matching private key to unlock it, a step called decryption. Symmetric ciphers are much faster, so most systems use key pairs only to agree on a shared symmetric key.
Encryption vs Hashing vs Signing
These three tools are often mixed up. Encryption can be reversed by anyone who has the key. A hash cannot be reversed at all. It only proves that data has not changed. A digital signature proves who approved a message, but it does not hide the message. Blockchains rely mainly on hashing and signing, while encryption guards the keys and data that users keep off-chain.
Role of Encryption in Blockchain
Wallet files are the clearest case. Ethereum’s standard keystore format, set out in the Web3 Secret Storage definition on ethereum.org, locks a private key with AES-128-CTR. The locking key comes from your password through a deliberately slow function, PBKDF2 or scrypt. That slowness makes each password guess expensive for an attacker.
Connections are the second case. Wallets, exchanges and RPC providers use TLS, the same encryption behind the padlock in a web browser, to protect data in transit. Some wallets also offer encrypted cloud backups of the recovery phrase, locked with a password that only the user knows.
A newer field tries to keep on-chain data encrypted too. Fully homomorphic encryption, or FHE, lets a computer run math on encrypted data without decrypting it first. Zama uses FHE to add confidential balances and transfers to Ethereum, as our Zama explainer describes.
Example: Encrypted Balances on Ethereum in 2026
Zama’s protocol went live on Ethereum at the end of December 2025. Zama said the value held in private, encrypted form on the protocol passed $122 million on October 31, 2026. FHE is still slow. The Zama Protocol litepaper puts current capacity at over 20 transactions per second per chain on standard processors, far below ordinary public transfers.
Limits and Risks
Encryption is only as strong as the key and the password behind it. A weak password lets attackers guess their way into a stolen wallet file, and malware can capture a password as it is typed. Encryption also does not hide on-chain activity. Once a transaction is broadcast, its amounts and addresses are public unless the network itself uses privacy technology.
Encryption and Quantum Computers
Large quantum computers would affect the two types of encryption differently. Grover’s algorithm would roughly halve the strength of symmetric keys, so a 256-bit AES key would still offer about 128 bits of security. Shor’s algorithm is the bigger threat. It could break public-key systems such as RSA and the elliptic curve cryptography used for blockchain signatures.
Standards bodies are preparing. In August 2024, the US National Institute of Standards and Technology published FIPS 203, a key exchange standard called ML-KEM that is designed to resist quantum attacks. Experts disagree on when machines large enough to run Shor’s algorithm against real keys might exist.
In Transit, At Rest and End to End
Security guides often name three cases. Data in transit is protected while it moves, for example by TLS between an app and an exchange. Data at rest is protected while stored, such as an encrypted wallet file or backup. End-to-end encryption means only the sender and receiver can read a message, and the service in the middle cannot. Crypto users rely on all three, often without noticing.
Frequently Asked Questions
Is the blockchain encrypted?
Usually not. Public blockchains such as Bitcoin and Ethereum store transactions in plain form so that every node can check them. What protects your coins is a digital signature made with your private key, not encryption of the ledger. Encryption mainly protects the things around the chain, such as wallet files, backups and the connections between your device and an exchange.
What is the difference between encryption and hashing?
Encryption is reversible: anyone with the right key can turn ciphertext back into the original data. Hashing is one-way: it turns data into a fixed-length fingerprint that cannot be turned back. Blockchains use hashes to link blocks and detect changes, while wallets use encryption to lock private keys with a password. Both protect data, but they answer different questions.
Does encryption protect my crypto if my password is weak?
Only partly. An encrypted wallet file is safe from anyone who cannot guess the password, but attackers who steal the file can try huge numbers of guesses offline. Slow key functions such as scrypt raise the cost of each guess, yet a short or reused password can still fall. A long, unique passphrase and an offline seed phrase backup work far better.
Will quantum computers break crypto encryption?
Not with today’s machines. A large, error-corrected quantum computer could in theory break the public-key cryptography behind most wallet signatures, while symmetric encryption such as AES-256 would stay strong. Researchers and standards bodies are already publishing quantum-resistant algorithms, and several blockchain communities are discussing how to move to them before such machines exist.
Data sources: ethereum.org Web3 Secret Storage definition; Zama Protocol figures as reported on Blockchainreporter’s Zama explainer (value held privately as of October 31, 2026; litepaper capacity); all read November 16, 2026; NIST FIPS 203 (August 2024).