Hub Tutorial

🌐 Exploring Hubs in FHE Validation

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

1. Hub Owner 👑

The Hub 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 Hub'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. Hub Manager 🤖

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

4. Openness to Other Consumers 🌱

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

---

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