Summary: Fhenix is a privacy infrastructure project built around fully homomorphic encryption rather than TEEs or a standalone privacy chain. Its current primary materials show a notable product shift: what began as an FHE-powered Layer 2 is now framed as CoFHE, an off-chain FHE coprocessor and toolchain for EVM-compatible apps. The docs describe a layered system with Solidity libraries, a client SDK, on-chain task-management and access-control contracts, and off-chain execution, decryption, and proof-verification services. That makes Fhenix most legible today as confidential-compute middleware for Ethereum apps, not simply as another L2.
What it does:
Provides a Solidity FHE library and client SDK so developers can encrypt inputs, operate on encrypted values, and manage decryption permits in EVM-compatible applications
Runs CoFHE, a modular off-chain computation layer that executes FHE operations while coordinating with on-chain contracts such as the Task Manager, ACL, and ciphertext registry
Uses a threshold-decryption network plus ZK-verified encrypted inputs to keep data encrypted through most of the computation lifecycle
Publishes active code and examples across contracts, SDKs, docs, and proof-of-concept applications, including Redact and shielded stablecoin demos
Key claims:
The current homepage says Fhenix has evolved from an FHE Layer 2 into a confidential DeFi infrastructure company centered on CoFHE, positioning privacy as an add-on for Ethereum apps rather than only a separate chain environment
CoFHE architecture docs describe a hybrid system of on-chain contracts plus off-chain services including FHEOS Server, Slim Listener, Result Processor, Threshold Network, and ZK Verifier
The docs say encrypted inputs are accompanied by zero-knowledge proofs of knowledge before entering contract workflows, and decryption access is managed through permits and threshold cryptography rather than public plaintext exposure
The public roadmap is unusually explicit about current trust assumptions: Fhenix says threshold-network parties are run by Fhenix, key generation still involves a trusted dealer, parts of the system remain centralized, the codebase is unaudited, and not all code is yet fully open-source
The GitHub organization shows recent activity across developer docs, contracts, SDKs, and example applications, suggesting the current center of gravity is developer tooling and middleware rather than a standalone consumer chain launch
Whitepaper: No current canonical standalone whitepaper or litepaper was found in the official materials reviewed during this pass. The most informative primary sources were the official site, CoFHE docs, roadmap pages, and active GitHub repositories; see ../whitepapers/fhenix-primary-sources-2026-04-27.md.