[DOCS] fhe-library: Teecryptor decrypts and signs today, not the Threshold Network

[haimbj1]

DOC-67

The FHE library pages named the Threshold Network as the component that decrypts CoFHE ciphertexts and signs decrypt results. That is wrong.

Teecryptor does that work today, inside a hardware-attested TEE. The Threshold Network is a future plan. The Deep Dive tab was already corrected in #43; this aligns the FHE library tab to the same wording.

Changes:

• access-control.mdx: the security argument now names Teecryptor. It states what the TaskManager actually checks: it recovers the signer from the ECDSA signature over (result, encType, chainId, ctHash) and accepts only the registered decryptResultSigner. The reason an attacker cannot get a signature is that Teecryptor's signing key never leaves the enclave, and Teecryptor only signs after an ACL-gated request.
• decryption-operations.mdx: signer renamed, and the Tip no longer sells MPC decryption as current. It now links to the Teecryptor page, and points at Future Plans for the planned Threshold Network. The old link to /deep-dive/cofhe-components/threshold-network is gone; that page was retired in Deep Dive rewrite: align every page to the current architecture #43 and only resolved through a redirect. Also dropped "Dispatcher", which is not a current component name.
• fhe-sol/decryption.mdx, auction-example.mdx, conditions.mdx: "Threshold Network signature" and "threshold signature" become "Teecryptor signature".

17 mentions across 5 files. lint-docs, vale, and check-versions are clean on every file touched.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
fhenix	🟢 Ready	View Preview	Sep 3, 2026, 4:59 PM