FHE Operation Request Flow

This page follows a single FHE operation from the contract call that requests it to the commitment that anchors its result onchain. The request itself is synchronous: the contract gets a handle for the result immediately, while the coprocessor computes the actual ciphertext in the background.

Key components

Component	Description
Your contract	Requests FHE operations through the FHE.sol library
FHE.sol	The Solidity library providing FHE operation functions
TaskManager	Validates requests, checks the ACL, and emits task events
FHE Engine	Picks up task events, validates and orders the work, executes it, and commits the result
CommitmentRegistry	Records a hash commitment for every result ciphertext

Flow diagram

Step-by-step flow

Encrypt the input with the Client SDK

The application encrypts its input client-side and proves it valid, producing an encrypted-input handle plus a batch proof the contract can accept. The Encryption Request Flow covers this step.

This step happens on the client side, before any blockchain interaction.

Request an FHE operation

Import the FHE library in Solidity:

import "@fhenixprotocol/cofhe-contracts/FHE.sol";

Call the appropriate FHE function from the imported library:

// Using trivial encrypt or the handle and proof from the previous step.
function addExample(externalEuint32 input, bytes calldata proof) public {
    euint32 lhs = FHE.asEuint32(input, proof);
    euint32 rhs = FHE.asEuint32(10);

    // Request an operation (addition in this example)
    euint32 result = FHE.add(lhs, rhs);
}

FHE.sol forwards the request to the TaskManager contract.

TaskManager processing

The TaskManager is the gateway for all FHE operation requests. It:

Validates the request structure, so all inputs are properly formatted.
Verifies access permissions: the caller must have ACL access to every encrypted input.
Generates a unique handle that will reference the future ciphertext result.
Returns the handle to the calling contract, synchronously. Subsequent operations can chain on it right away.
Emits a TaskCreated event with the operation details for the offchain services.

FHE Engine pickup

The FHE Engine subscribes to TaskManager events on every host chain and picks up the TaskCreated event. It checks that the operation is well formed and that the inputs it references exist. An operation that arrives before its inputs finish computing is deferred and released once they land.

Execution

The engine then:

Executes the requested operation on the encrypted data.
Stores the result ciphertext in the ciphertext database, keyed by the handle.
Releases any dependent operations that were deferred while waiting for this result.

Commitment posting

The engine produces a commitment for the result, the hash of the stored ciphertext bytes, and posts it in a batch to the CommitmentRegistry on the registry chain. The commitment anchors the result. Teecryptor will only decrypt ciphertext bytes that hash to a registered commitment.At this point the operation cycle is complete, and the confidentiality of every encrypted value is preserved.

CoFHE Components

Data Flows

Research

Key components

Flow diagram

Step-by-step flow

​Key components

​Flow diagram

​Step-by-step flow

Key components

Flow diagram

Step-by-step flow