Fhenix / CoFHE - Decryption Trust & Tokenomics | Project Research Dossier

Project Research Dossier - Fhenix / CoFHE Research cutoff: 1 October 2026. Prepared by kimchi_swap with Codex for a Republic quest.

Question: Can confidential EVM computation support a defensible technology thesis while token economics remain undisclosed?

CoFHE lets contracts operate on encrypted handles while an offchain coprocessor performs FHE. The official site lists Sepolia testnets; this is not proof of production adoption. [1,2]

The key diligence issue is the decryption trust model. The homepage says no trusted hardware, but Teecryptor documentation describes Intel TDX and 3-of-6 key-share reconstruction inside one enclave. Distributed shares at rest are different from multiparty decryption at runtime; the latter is a planned replacement. Clarify deployment/version before drawing conclusions. [1-3]

No public sale or active TGE was identified in the reviewed official pages/blog index. This is a bounded finding, not proof of absence. Token price, supply, allocation, vesting and emissions were not established, so actual FDV and dated dilution cannot be calculated. Private financing is not token market cap. [1,4]

Conclusion: a technical research candidate, not an established token valuation. Require deployment-linked audits, a reconciled trust model, actual adoption data and official token terms.

Disclosure: No Fhenix holdings, investment rights, testnet/airdrop participation or project compensation. AI-assisted research; Republic quest rewards may apply. No independent audit performed.

Full research text and sources follow below. Please challenge a specific assumption or identify missing evidence. [1] https://www.fhenix.io/ [2] https://cofhe-docs.fhenix.zone/get-started/introduction/what-is-cofhe [3] https://cofhe-docs.fhenix.zone/deep-dive/cofhe-components/teecryptor [4] https://www.fhenix.io/blog

[Full research 1/4] PROJECT RESEARCH DOSSIER - FHENIX Prepared for kimchi_swap. AI-assisted research for a Republic quest.

Research question Can Fhenix make confidential EVM applications practical, and what must be verified before its technology can support an investment thesis? This dossier separates the currently documented product from promotional claims and undisclosed token economics.

Product and evidence The official site describes a shift from an FHE Layer 2 to confidential DeFi infrastructure. CoFHE moves encrypted computation offchain while Solidity contracts use ciphertext handles. Client-side encryption, input proofs, access controls and controlled decryption are documented components. The homepage lists Ethereum, Arbitrum and Base Sepolia testnets and says mainnet is forthcoming [1,2]. These are project disclosures, not an independently executed deployment test.

Material finding: clarify the decryption trust model The homepage says the coprocessor operates without trusted hardware [1]. The detailed documentation instead describes Teecryptor running in an Intel TDX trusted execution environment. It verifies access permissions and ciphertext commitments, then decrypts within the enclave. A 3-of-6 key-share arrangement reconstructs the key inside that enclave; it is not the same as a live multiparty decryption network [3].

[Full research 2/4] Interpretation and technical risk FHE computation over ciphertext and TEE-based authorized decryption are different stages. The sources may describe different versions or scopes; this is a documentation inconsistency to resolve, not evidence of an exploit. The documented runtime concentrates the reconstructed key in one attested machine. Review hardware/attestation assumptions, approved image control, custodian independence, access-control correctness and service availability. The docs describe threshold multiparty decryption as a future replacement, not a completed safeguard [3].

Team and delivery verification The site identifies Guy Zyskind as founder, Guy Itzhaki as CEO and Ravital Solomon as head of research, and links developer tools and documentation [1]. Named people and inspectable technical materials are useful verification leads. Their biographies, current production deployments, audit scope, deployed versions and commercial adoption were not independently validated in this review. Neither funding nor a named team proves execution or safety.

Tokenomics and eligibility: unresolved The official pages reviewed do not provide an investable token price, circulating supply, diluted supply denominator, allocation table, vesting calendar, emissions policy or tokenholder rights. FDV, circulating market cap and project-specific unlock amounts therefore remain unquantifiable. Private financing mentioned on the homepage is not evidence of a public token sale [1]. No public raise or active TGE was identified on these reviewed pages; that limited search does not establish their absence. The official blog index was also checked; no Fhenix public-sale or TGE announcement was identified. This is a bounded eligibility finding as of 1 October 2026, not proof of absence [4].

[Full research 3/4] Dilution model: explicitly hypothetical Let C be current circulating supply and U an additional unlock. Supply growth is U/C. If C=10 million and U=5 million, tradable supply grows 50%. At an assumed unchanged $1 price, circulating market cap rises from $10 million to $15 million; with an assumed 100 million diluted denominator, FDV is $100 million. These numbers are teaching assumptions, not Fhenix data or a price forecast. Selling pressure depends on recipients, demand, liquidity and market behavior. A real model needs dated unlocks, recipient categories, transfer restrictions and emissions.

Decision criteria and conclusion The useful research lead is confidential application infrastructure with a concrete documented workflow. A token valuation is not supported by the reviewed evidence. Before upgrading that conclusion, obtain official token terms and sale status; reconcile the homepage with the current Teecryptor architecture; verify relevant audits against deployed code; and request production performance, availability and adoption measurements. Research benchmark speed should not be presented as end-to-end application performance.

Proposed discussion question Which deployed network and software version currently use Teecryptor, and what evidence demonstrates its approved image policy and custodian independence? Separately, when will allocation and unlock schedules be published? Those answers would make this analysis project-specific rather than a generic dilution framework.

[Full research 4/4] Disclosures The submitter, kimchi_swap, confirms no Fhenix holdings, investment rights, testnet or airdrop participation, or project compensation. Prepared with Codex for a Republic quest; quest rewards may apply. No independent code audit or production deployment test was performed. This document does not claim teammate review or verifier approval.

PRIMARY SOURCES

1. Fhenix official website and FAQ: https://www.fhenix.io/
2. What is CoFHE?: https://cofhe-docs.fhenix.zone/get-started/introduction/what-is-cofhe
3. Teecryptor: https://cofhe-docs.fhenix.zone/deep-dive/cofhe-components/teecryptor
4. Official blog index: https://www.fhenix.io/blog