[DOCS] tutorials/migrating-from-fhe-decrypt: Teecryptor, not the Threshold Network

[haimbj1]

DOC-68

The migration tutorial named the Threshold Network as the component that decrypts and signs. Teecryptor does that today, inside a hardware-attested TEE. The Threshold Network is a future plan.

Changes:

• All 6 Threshold Network mentions now say Teecryptor, with the same wording the Deep Dive pages use.
• Teecryptor is introduced once, with a link to its Deep Dive page.
• One line after the flow steps points at Future Plans and labels the Threshold Network as planned.

While in the page:

• Overview states that FHE.decrypt no longer exists in FHE.sol, so a contract that still calls it does not compile.
• The verifyDecryptResult sample used require() around a function that reverts on a bad signature, so the message was unreachable. It now uses verifyDecryptResultSafe, and the text says how the two differ.
• The unshield client sample passed result.ctHash to a bytes32 parameter; it now passes the handle it already read.
• transferToPublic took no recipient parameter but used one.
• Style fixes: sentence case headings, onchain/offchain as one word, no em dashes in code comments, no 'simple' or 'just'.

Verified against source: FHE.sol (allowPublic, publishDecryptResult, verifyDecryptResult, verifyDecryptResultSafe, no decrypt), TaskManager.verifyDecryptResult reverting behavior, and @cofhe/sdk@0.7.1 (DecryptForTxResult fields, withACP/withoutACP).

lint-docs, vale, and check-versions are clean.

[mintlify]

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

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