Builders

Builders are one of the user classes of the Impossible Cloud Network (ICN) who require decentralised storage and computing resources. Builders access these resources by providing ICNT token requirements, which allows them to use the network’s distributed infrastructure.

Builders play a critical role in sustaining the ICN ecosystem, as their ICNT access requirements help reward Hardware Providers (HPs) and HyperNodes, ensuring the network continues to function efficiently. By submitting capacity requests, Builders initiate the flow of resources and incentives within the network.

Figure 1: Flow of Builders in the ICN

This flowchart illustrates the interaction between Builders and the Impossible Cloud Network (ICN). Builders submit Capacity Requests and provide ICNT for access. These ICNTs funds contribute to the Treasury.

---

Accessing Network Services

Builders in the Impossible Cloud Network (ICN) use ICNT tokens to access the network’s decentralised storage and compute resources. Builders submit storage capacity requests to the protocol, which then allocates the required resources from Hardware Providers (HPs) based on availability.

The Process of Accessing Network Resources

• Submit Capacity Request: Builders submit a request for storage capacity, specifying:

  • The amount of storage required (e.g., 1PB).

  • The location where the storage is needed (e.g., a particular cluster).

  • The duration for which the storage is required.

• Provide ICNT: To access the requested resources, Builders provide ICNT tokens based on factors like the cluster rate, storage capacity, scaling, and booking duration. Once validated by the network, Builders are allocated storage and can begin utilizing it. An example calculation might look like this

$$\text{Cost} = \text{ClusterRate} \times \text{Capacity} \times \text{ScalingFactor} \times \text{BookingDuration}$$

where:

• ClusterRate is the baseline rate for a given cluster.

• Capacity is the amount of storage requested.

• ScalingFactor accounts for specific node or usage scaling.

• BookingDuration is the length of time the capacity is needed.

Receive Network Resources: Once the request is processed and the ICNT access requirements are provided, Builders get access to ScalerNodes with the amount of storage requested.

For detailed information on how Access Requirements are calculated and distributed, visit the Access to Network Resources page.

---

Capacity Allocation

When an Builder submits a capacity request, the ICN protocol automatically assigns the request to the most suitable ScalerNode (SN) within the cluster where multiple HPs coexist. This process ensures that Builders are allocated storage efficiently and that HPs are compensated fairly for the resources they provide.

How Capacity is Allocated

• Pre-Assignment: The protocol pre-assigns the requested storage to a ScalerNode based on several key factors:

  • Reservation Price: HPs set a minimum price (Reservation_Price) for every ScalerNode they provide.

  • Cluster-Level Allocation: The protocol allocates ScalerNodes at the cluster level, meaning Builders do not select individual HPs. Instead, the network assigns a ScalerNode that meets the requirements requested.

---

Builders Responsibilities

As participants in the Impossible Cloud Network (ICN), Builders have certain responsibilities to ensure smooth operation and proper use of network resources.

Ensuring Sufficient ICNT for Services:

Builders must ensure they have enough ICNT tokens available for the capacity they request from Hardware Providers (HPs). Access to network resources requires an upfront provision of ICNT as access to network resources, calculated based on the amount of capacity requested and the Cluster_Price and the duration of the booking period.

Accurate Request Details:

Builders must provide accurate details regarding the amount, location, and duration of the storage capacity needed. Incorrect information may lead to failed capacity assignments or overcharges.