0%
← Back to blog

Why Solana Needs FHE (And Why FHE Needs Solana)

Solana moves 65,000 transactions per second with 400-millisecond block times. It has the throughput, the finality speed, and the DeFi ecosystem density to be the dominant chain for financial applications.

It has one structural weakness that is holding it back from institutional adoption: every transaction is a postcard. Everyone can read it.

The $1.5 Billion Leak

In 2025, MEV bots extracted over $1.5 billion from DeFi users across chains. Solana's share of that extraction is growing faster than any other ecosystem, because Solana's speed actually makes certain forms of MEV more profitable — sandwich attacks execute in sub-second windows, making the capital efficiency of the attack extremely high.

Jito bundles have brought MEV into the open on Solana. Validators can auction off transaction ordering. Bots bid for the right to front-run your trade. It is not a bug. It is the system working as designed, because the system was designed with all-public state.

Why Privacy Layers Have Not Fixed This

Confidential Transfers (SPL Token Extension): Encrypts token balances and transfer amounts using ElGamal encryption. Meaningful progress, but only covers transfer amounts. MEV bots do not need your exact balance; they need your trade direction and size.

ZK Compression: Reduces on-chain data storage through zero-knowledge proofs, but proves data correctness, not data privacy.

Private mempools / block builders: Delay visibility of transactions. Helpful, but the data is still plaintext once revealed.

None of these approaches encrypt the computation itself.

What FHE Actually Gives Solana

  1. Your swap instruction is encrypted. The input token, output token, amount, and slippage parameters are ciphertexts.

  2. The AMM computation runs on encrypted inputs. Price calculation, fee deduction, slippage check — all performed on ciphertext.

  3. Threshold decryption reveals the result only to you. A 3-of-5 validator threshold network produces partial decryption shares.

MEV bots see encrypted bytes in the mempool. Sandwich attacks become mathematically impossible — there is nothing to sandwich.

Why FHE Needs Solana

High throughput: Solana's parallel execution via Sealevel and raw TPS capacity provide the headroom FHE needs.

Low block times: Solana's 400ms slots mean total FHE latency stays under 3 seconds — acceptable for users.

Affordable data availability: FHE ciphertexts are large (~4KB per value). Ethereum calldata costs would be prohibitive. Solana's account model makes this economically viable.

Developer ecosystem: Solana has the fastest-growing developer ecosystem in crypto, with teams culturally inclined toward new infrastructure.

The Architecture: Coprocessor Model

User encrypts data locally (FHE public key)
        |
        v
Solana transaction with encrypted instruction data
        |
        v
Aura coprocessor receives ciphertext
        |
        v
Homomorphic computation (add, multiply, compare)
        |
        v
Encrypted result posted back to Solana
        |
        v
Threshold decryption (3-of-5 validators)
        |
        v
User decrypts with local secret key

What This Enables for Solana DeFi

For DEXs (Jupiter, Raydium, Orca): Encrypt order flow before it hits the AMM. Eliminate sandwich MEV.

For lending protocols (Kamino, Marginfi): Hide position sizes and collateral ratios. Prevent liquidation sniping.

For governance (Realms): Encrypted votes tallied homomorphically and revealed only after voting period ends.

For NFT markets (Tensor, Magic Eden): Sealed-bid auctions where bids are encrypted until auction closes.

The Timeline

  • April 7, 2026: SDK announcement + litepaper

  • April 24: Alpha program opens (10 builder spots)

  • May 6-7: Public beta

  • Q3 2026: Mainnet

Solana was built for speed. Aura adds privacy. Together, they are the first blockchain stack that gives you both.

Join the builder waitlist at afhe.io/sdk. Follow at @AfheLabs. Come to discord.gg/aurafhe.