Services and Apps

Builders reserve network capacity in ScalerNode units where applications and services are deployed. When submitting capacity requests, this triggers the automatic allocation of necessary resources and rewards within the network.

Builders can submit capacity requests at the level of clusters where the ICN protocol then assigns to a specific ScalerNode. Then, a Builder booking specifies:

1. Builder address: Blockchain address of the Builder.

2. Cluster ID: Unique identifier of the cluster within a specific region.

3. Capacity Request: The amount of requested capacity units.

4. Duration Request: Requested duration of the booking period.

And based on the following ScalerNode’s parameters:

1. ScalerNode capacity: The total capacity of the ScalerNode for a certain hardware class*.

2. Minimum booking duration: Minimum booking duration of the ScalerNode set by ICN (currently 90 days).

3. Maximum booking duration: Maximum booking duration of the ScalerNode set by the HP (minimum 180 days).

4. Cluster Price: Minimum value between:

   1. Maximum price: max price for a cluster in ICNT for a hardware class*.

   2. Reservation price: price of the ScalerNode in ICNT set by the HP.

5. Collateral commitment duration: Duration of the lock period of the collateral (min. 36 months).

*Currently, only one storage class is available with unit of capacity in terabytes (TB).

The protocol assigns the requested capacity to any ScalerNode that fulfills the following requirements:

1. Capacity request is equal to the capacity of the ScalerNode.

2. Booking duration requested is within minimum and maximum booking duration periods of the ScalerNode.

3. Duration request is shorter than the collateral commitment period of the ScalerNode.

If more than one ScalerNode fulfills the request, the ICN protocol assigns the first available ScalerNode from the pool.