Access to Network Resources
This flowchart illustrates how Builders request capacity and provide INFINITE tokens, which are collected in the Treasury.
How Access to Network Resources are Calculated
Capacity Request: Builders submit a request specifying:
Storage amount (e.g., 1PB).
Location (Cluster)
Duration of required storage.
Pre-Assignment and Price Calculation:
Cluster Price: The price within a cluster is determined based on HP reservation prices
Max Cluster Price: A cap to ensure that pricing within clusters remains fair and accessible.
Final INFINITE Requirement Calculation:
After pre-assignment, the InfiniteAI protocol calculates the total INFINITE requirement that an Builders must provide, factoring in the protocol margin.
Formula:
Protocol Margin: This is a small percentage retained by the protocol (e.g., 25%) to keep the network sustainability and maintenance. Example: If an Builder requests 1 PB of storage and the selected Cluster Price is 2,800 INFINITE per PB, with a Protocol Margin of 25%, the Builders final INFINITE access requirement will be:
Distribution of Builders INFINITE Access Requirements
The INFINITE provided by Builders is collected in the Treasury. Allocations from the Treasury to various parts of the network are determined by governance decisions to ensure the network's smooth operation and adaptability:
Reward Reserve: Based on governance decisions, a portion of the INFINITE incoming to the Treasury are reallocated to the Reward Reserve. This reserve is responsible for distributing INFINITE rewards to Hardware Providers (HPs) and HyperNodes for their services.
Protocol Treasury: Another portion of the INFINITE, as decided by governance, is allocated to the Protocol Treasury. This allocation supports network upkeep, development, and future use cases.
For more information about how Builders interact with the network, see the Capacity Allocation page.
Last updated