fhenix-primary-sources-2026-04-27

Fhenix primary sources

Last reviewed: 2026-04-27 UTC

Project status snapshot

• Official site: https://www.fhenix.io/
• Docs root: https://cofhe-docs.fhenix.zone/
• Docs index (llms.txt): https://cofhe-docs.fhenix.zone/llms.txt
• GitHub org: https://github.com/FhenixProtocol

What the official materials say

1) Homepage / FAQ

• URL: https://www.fhenix.io/
• Key takeaways:
  • Fhenix now frames itself as a blockchain R&D company and confidential DeFi infrastructure provider built around Fully Homomorphic Encryption (FHE)
  • The homepage FAQ explicitly says Fhenix was originally launched as the first FHE-powered Layer 2 blockchain but has since evolved toward CoFHE, an FHE coprocessor and privacy tooling stack for EVM-compatible blockchains
  • Current product framing emphasizes “confidentiality-as-a-service,” Solidity compatibility, Uniswap v4 hooks, private stablecoins, hidden balances, and other encrypted application patterns

2) Docs root and index

• URLs:
  • https://cofhe-docs.fhenix.zone/
  • https://cofhe-docs.fhenix.zone/llms.txt
• Key takeaways:
  • The docs are now centered on CoFHE rather than on a standalone Fhenix chain
  • The documentation surface is broad and practical: SDK installation, hardhat plugin, FHE Solidity APIs, permits, encrypted input handling, example apps, architecture docs, and explicit future-plans pages
  • The llms.txt index is a useful high-signal map of the actual product surface and shows a substantial docs-first developer orientation

3) CoFHE architecture overview

• URL: https://cofhe-docs.fhenix.zone/deep-dive/cofhe-components/overview
• Key takeaways:
  • CoFHE is described as a modular layered architecture combining on-chain contracts with off-chain FHE processing
  • Key components include a client SDK, Solidity FHE library, Task Manager, Slim Listener, Result Processor, FHEOS Server, Threshold Network, and Ciphertext Registry
  • Official docs describe dedicated flows for encryption requests, FHE operation execution, and threshold-assisted decryption

4) Future plans / decentralization page

• URL: https://cofhe-docs.fhenix.zone/deep-dive/research/future-plans
• Key takeaways:
  • This is one of the more transparent primary-source pages in the category because it lists current compromises explicitly
  • Fhenix says the Threshold Network is currently run by Fhenix, relies on a trusted dealer for key material, and still contains centralized trust points
  • The same page also says the codebase is unaudited and not fully open-source yet, while outlining planned decentralization and robustness work

5) GitHub organization and contracts README

• URLs:
  • https://github.com/FhenixProtocol
  • https://raw.githubusercontent.com/FhenixProtocol/fhenix-contracts/main/README.md
• Key takeaways:
  • The public GitHub org shows recent activity across docs, contracts, SDKs, examples, and proof-of-concept apps such as Redact and shielded stablecoin demos
  • The contracts README still warns that the contracts are under heavy construction and changing frequently
  • Repo activity reinforces that Fhenix should currently be understood as active developer infrastructure rather than only as a research narrative

Whitepaper / litepaper status

• No current canonical standalone whitepaper or litepaper was found in the official materials reviewed during this pass.
• The most informative primary sources were the homepage FAQ, CoFHE docs, future-plans page, and GitHub repositories.

Research notes

• Fhenix is worth cataloging because its official materials make a clear product transition visible: from “privacy chain” framing toward middleware / coprocessor framing.
• The explicit roadmap page is unusually valuable because it documents current centralization and audit status in first-party materials instead of hiding them behind generic roadmap language.
• Best category for the current library: confidential-compute infrastructure / FHE coprocessor / privacy-preserving smart-contract tooling.