Subnet with FHE Validation

🌐 Exploring Subnets in FHE Validation Subnet serves as a virtual boundary, tailored to specific use cases within FHE validation. The subnet design aims to generalize FHE validation demands and provide flexibility to adapt to various AI and other projects. Each subnet comprises the following components:

1. Subnet Owner 👑

The Subnet Owner initiates the use case idea and oversees the registration and updates of FHE validation tasks. Utilizing existing templates (e.g., Task Definition), the owner designs the logic and credits initial funds to kickstart the subnet's operations.

2. Task Definition 📝

Task Definition stores all essential information for task execution. This includes details such as what needs validation, round logic, SIV opt-in criteria, slash criteria, rewards contract, and the fheActivationFunction. Moreover, the task specifies who will handle decryption. If Mind is chosen, it also outlines where decrypted results will be written.

3. Subnet Manager 🤖

The Subnet Manager acts as a contract for subnet owners to register the subnet and broadcast tasks to attract SIVs. It automates the management of subnet lifecycle, encompassing registration, publishing, and cancellation processes.

4. Openness to Other Consumers 🌱

Subnets can also extend their services to other consumers. Once a subnet gains mutual trust from the community, individual consumers seeking FHE validation-enabled services can directly engage with the subnet and make payments accordingly.

We will introduce a few examples of how to build subnet in next chapters.

Last updated