FHE Consensus Network
Last updated
Last updated
FCN: FHE Consensus Network
Do FHE consensus on fhe encrypted input. It waits for the other Hub's request, takes fhe encrypted input and do FHE computation to reach the consensus over the ciphertext. Each FCN Node uses the FHE compute key and has no way to decrypt the ciphertext and know the plaintext behind the ciphertext to prevent potential collusion risk. FCN is a foundational subnet to provide FHE Consensus for all subnets.
FCN waits for FHE consensus onchain request and is governed by HubController contract. Take RandGen as an example, FCN will start to work when RandGen finishes the voting round and requests to do FHE consensus.
FHE Consensus starts when other Hub generated requests onchain. FCN is served by a group of FHE nodes. Each node takes the FHE compute key and the request, does requested FHE computation, and generates a ciphertext result that is still encrypted by FHE.
FCN uses Byzantine Fault Tolerance (BFT) algorithm to determine the consensus threshold. The current setting is to require 2/3 FCN nodes to attest to the same FHE Request. FCN requires 32 nodes minimal.
FCN nodes can earn rewards for their efforts in FHE decryption. These rewards will be sent directly to each participating FCN node.
