Project Name: IO.NET
Tag: $IO
Type: Decentralized Computing Network

Introduction

IO.NET is a decentralized GPU network designed specifically for machine learning (ML). It aggregates computing power from over one million GPUs sourced from independent cryptocurrency miners, Filecoin, Render, and other projects, providing low-cost, flexible computing resources for AI engineers.

Product Components

IO Cloud

Provides cloud computing services to users, enabling them to deploy and manage virtual machines, containers, and other cloud resources on demand. Seamlessly integrated with IO-SDK, it offers a comprehensive solution for scaling AI and Python applications. IO Cloud simplifies the process of managing cloud infrastructure, allowing users to focus on core tasks without worrying about the complexity of the underlying infrastructure.

IO Worker

A virtual leasing manager interface, allows users to manage GPU node operations through an intuitive web application. Users can lease their computing devices (such as GPUs and CPUs) to those in need of computing power. By leasing out their processing capabilities, users can earn rewards for tasks such as AI computation or rendering.

IO Explorer

Provides users with comprehensive statistics and visualizations of various aspects of the GPU cloud. Users can monitor compute jobs, access performance metrics, and explore available resources within the IO.NET network. IO Explorer also allows viewing the activities of others, offering a complete view of platform functionalities and user engagement.

IO.NET Technology

IO Network

The IO Network is an advanced network backend utilizing a secure mesh VPN to achieve low-latency communication between node workers. A mesh VPN network connects nodes in a non-hierarchical, decentralized manner. Unlike traditional hub-and-spoke VPN architectures that rely on central concentrators or gateways, a mesh VPN network allows each node to connect directly to every other node in the network. This structure ensures that data packets can travel along multiple paths, enhancing redundancy, fault tolerance, and better load distribution.

The mesh network architecture of IO.NET allows data to travel along the most efficient paths, minimizing latency. The decentralized nature of the mesh network ensures that the network continues to operate even if individual nodes fail. Additionally, the distributed network enables direct connections between nodes, facilitating efficient distributed computing and enabling resource sharing and collaborative processing across the entire network.

IO Tunnel

IO.NET utilizes reverse tunneling technology. A reverse tunnel establishes a secure connection from a client to a remote server by opening an inbound connection on the server side. This contrasts with traditional forward tunnels, where the client opens a connection to the server.

IO.NET uses reverse tunneling technology. A reverse tunnel is a method of establishing a secure connection from a client to a remote server by opening an inbound connection on the server side. This is the opposite of traditional forward tunnels, where the client opens a connection to the server. In the reverse tunnels adopted by the IO.NET network, engineers can securely access and manage IO Workers without complex network configurations or dealing with firewall and NAT restrictions, thereby simplifying engineers’ access to IO.NET miners.
The process includes:

1. IO Worker establishes a connection with the IO.NET server, creating a reverse tunnel.
2. The engineer’s machine connects to the IO.NET server as an intermediary.
3. The IO.NET server routes traffic between the engineer’s machine and the IO Worker through the reverse tunnel.

   Key Metrics

   

   Tokenomics

   Total token supply of 500,000,000:

• Seed Investors: 12.5%
• Series A Investors: 10.2%
• Core Contributors: 16%
• Community: 50%
  
  With the issuance of IO to incentivize network growth and adoption, the fixed maximum supply will grow to 800 million over 20 years. Rewards follow a deflationary model, starting at 8% in the first year, and decreasing by 1.02% monthly (approximately 12% annually) until reaching the 800 million IO cap. As rewards are issued, the share of early supporters and core contributors will gradually decrease, and the community’s share will grow to 50% after all reward distributions are completed.