bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 31쪽 중 1쪽
# Overview
Source: https://io.net/docs/guides/announcements/announcements
Stay up to date with the latest updates, migrations, and important news from io.net.
This section provides key information on platform upgrades, new features, and essential changes that impact suppliers and users.
<Update label="Ocotober 1, 2025">
### Service Update: Bare Metal (Self Serve) Moving Forward
Bare Metal on Demand will no longer be available starting Wednesday, October 1, 2025.
* If you need Bare Metal, please contact our sales team at [business@io.net](mailto:business@io.net) for managed services.
* For self-service compute, check out our latest option: [Virtual Machines on Demand](/docs/guides/clouds/deploy-vm-on-demand).
</Update>
<Update label="May 2025">
### Important: Action Required for Expired Refresh Tokens
Some suppliers using older refresh tokens (generated before our switch to non-expiring tokens) may experience token expiration after 365 days — causing worker downtime and authentication errors.
For full details and steps to resolve the issue, please refer to the [Action Required for Expired Refresh Tokens](/docs/guides/announcements/important-action-required-for-expired-refresh-tokens)
</Update>
<Update label="April 2025" description>
### Supplier Migration to M4 Series – Upgrade Now!
Suppliers on io.net can now seamlessly upgrade their existing inventory of M2 Pro, M2 Max, and M2 Ultra devices to the cutting-edge M4 series. This transition offers enhanced performance, improved efficiency, and ensures continued eligibility for earnings on the io.net platform.
For full details on the migration process, please refer to the [Supplier Migration Guide: Upgrading to M4 Series Devices](/docs/guides/announcements/supplier-migration-guide-upgrading-to-m4-series-devices)
</Update>
# Action Required for Expired Refresh Tokens
Source: https://io.net/docs/guides/announcements/important-action-required-for-expired-refresh-tokens
May 2025
We’ve identified that some suppliers who generated their refresh tokens before we switched to non-expiring tokens may encounter token expiration after 365 days. This can lead to worker downtime and authentication errors such as:
<CodeGroup>
```json json theme={null}
{"error":"invalid_grant", "error_description":"Unknown or invalid refresh token."}
```
</CodeGroup>
**Error:** *Authentication failed. Your token might be invalid or expired. Please re-generate one and try again. Use `--no_cache=true` flag to re-authenticate.*
To resolve this, please follow these steps to generate a new **non-expiring** refresh token and restart your worker:
**Step 1:** Run the `io.net worker` CLI binary with the `--no_cache=true` flag to initiate token regeneration.
**Step 2:** Provide any required details to the CLI. Once successful, your worker will launch using the refreshed token.
<Info>
After completing the initial interactive authentication, you’ll see a new --token value. You can reuse this token to update other devices silently.
</Info>
Thank you for your continued support of io.net. The io.net Team
# Supplier Migration Guide: Upgrading to M4 Series Devices
Source: https://io.net/docs/guides/announcements/supplier-migration-guide-upgrading-to-m4-series-devices
April 2025
Suppliers on io.net can now seamlessly upgrade their existing inventory of **M2 Pro, M2 Max, and M2 Ultra** devices to the cutting-edge **M4 series.** This transition ensures enhanced performance, improved efficiency, and continued eligibility for earnings on the io.net platform.
<Warning>
**Important Pre-Migration Requirement**:
Before initiating the migration, ensure your current M2 worker has been actively earning Block Rewards for at least the last 3 continuous hours (i.e., passing PoW tests and contributing work).
If this condition is not met, the new M4 device will be automatically blocked during the migration process.
</Warning>
### Important Migration Dates:
* **Migration Start:** UTC 09:00 AM on April 3rd, 2025
* **End of Support for M2 Devices:** UTC 23:59:59 on April 21st, 2025
* **Migration Window Closes:** UTC 23:59:59 on April 21st, 2025
<Info>
Only currently connected devices with full stake are eligible for migration.
</Info>
### M4 Series Device Options
| Device | Earning Multiplier | Ray Cluster Pricing | Staking Requirement |
| - | - | - | - |
| M4 | 0.5x | \$0.10/hour | \$IO 200 |
| M4 Pro | 0.75x | \$0.13/hour | \$IO 200 |
| M4 Max | 1x | \$0.15/hour | \$IO 200 |
### Migration Process:
##### Step 1: Disconnect Your M2 Device
Before migrating, ensure your **M2 Pro, M2 Max, or M2 Ultra** device is **disconnected** from the io.net network.
##### Step 2: Execute the Migration Command
Once your M2 device is disconnected, run the following command on your new **M4, M4 Pro, or M4** Max device:
<CodeGroup>
```curl curl theme={null}
./io_net_launch_binary_mac --device_id={same device id} --user_id={same user_id}
--operating_system="macOS" --usegpus=false --device_name="{same device name}"
```
</CodeGroup>
##### Step 3: Ensure Proper Configuration
Your new **M4 series** device should be **correctly configured** with a **stable internet connection** to avoid loss of **Block Rewards** during migration.
### Benefits of Migration:
When migrating to the M4 series, your new device will:
* **Retain** **the same device\_id**
* **Retain the same \$IO staked** (M2 Pro/Max staking requirements match M4/M4 Pro/M4 Max)
* **For M2 Ultra migrations**: The excess 50 \$IO (beyond the minimum staking requirement) will be withdrawable without a cooldown period after approximately 24-48 hours post-migration./*/*
### Additional Update:
This migration ensures suppliers remain operational on io.net while benefiting from the **next-generation M4 series devices**. We appreciate your continued support as we drive decentralized computing forward.
**Thank you for your continued partnership and support as we move towards a more innovative future together.**
If you have any questions, please contact io.net support. The io.net Team
# Architectural Layers
Source: https://io.net/docs/guides/architecture/io-architecture
The IO Portal architecture is a multi-layered, cohesive structure that provides a seamless, secure, and efficient user experience. Each layer has a distinct role, working in tandem to ensure the system's optimal performance. The architecture is built upon modern technologies, ensuring scalability, reliability, and robustness.
<Frame>
<img alt="" />
</Frame>
### User Interface
This layer is the visual gateway for users. It comprises the ***Public website***, ***Customers area***, and ***GPU providers area (Workers)***. The design is intuitive and user-centric, ensuring easy navigation and interaction.
> Tech Stack: ReactJS, Tailwind, web3.js, zustand.
### Security Layer
A pivotal layer ensuring the system's integrity and safety. It encompasses a **Firewall** for network protection, an **Authentication Service** for user validation, and a **Logging Service** for tracking activities.
> Tech Stack: Firewall (pfSense, iptables), Authentication (OAuth, JWT), Logging Service (ELK Stack, Graylog).
### API Layer
Serving as the communication bridge, this layer has multiple facets: ******Public API for the website, Private APIs for Workers/GPU Providers and Customers, andInternal APIs****** for Cluster Management, Analytics, and Monitoring/Reporting.
> Tech Stack: FastAPI, Python, GraphQL, RESTful services, gunicorn, solana.
### Backend Layer
The powerhouse of the system. It manages Providers (Workers), Cluster/GPU operations, Customer interactions, Fault Monitoring, Analytics, Billing/Usage Monitoring, and Autoscaling.
> Tech Stack: FastAPI, Python, Node.js, Flask, solana, IO-SDK (a fork of Ray 2.3.0), Pandas.
### Database Layer
The data repository of the system. It uses **Main storage** for structured data and **Caching** for temporary and frequently accessed data.
> Tech Stack: Postgres (Main storage), Redis (Caching).
### Message Broker/Task Layer
This layer orchestrates asynchronous communications and task management, ensuring smooth data flow and efficient task execution.
> Tech Stack: RabbitMQ (Message Broker), Celery (Task Management).
### Infrastructure Layer
The foundational layer. It houses the **GPU Pool** with hardware from our verified partners. Orchestration tools manage deployments, while Execution/ML Tasks handle computations and machine learning operations. Additionally, it provides ***Data Storage solutions***. GPU performance is continuously monitored.
> Tech Stack:
>
> * GPU/CPU Pool
> * Orchestration: Kubernetes, Prefect, Apache Airflow
> * Execution/ML Tasks: Ray, Ludwig, Pytorch, Keras, TensorFlow, Pandas
> * Data Storage: Amazon S3, Hadoop HDFS
> * Containerization: Docker
### IO-SDK: The Powerhouse Behind io.net
IO-SDK is our specialized fork of Ray, a core technology driving io.net's capabilities. Embracing Ray's native parallelism, IO-SDK effortlessly parallelizes Python functions, enabling dynamic task execution. Its in-memory storage ensures rapid data sharing between tasks, eliminating serialization delays. The dynamic auto-scaling feature means IO-SDK can quickly adapt to computational demands. Moreover, it is not just limited to Python; the language versatility and integration capabilities with leading ML frameworks like PyTorch and TensorFlow make it a robust and flexible choice. Whether on a single machine or a vast cloud platform, IO-SDK ensures io.net's scalability and performance.
> Together, these layers, powered by the mentioned tech stacks, form a robust and scalable architecture for the io.net Portal, ensuring it meets the demands of modern users.
# IO Network
Source: https://io.net/docs/guides/architecture/io-network
This article explores the concepts of mesh VPN networks and how we leverage their benefits to improve performance and reliability in the io.net protocol.
**IO Network** is a cutting-edge networking backend that utilizes a secured mesh VPN to allow ultra-low latency communication between the antMiners nodes or 'workers'.
<Frame>
<img alt="" />
</Frame>
### Understanding Mesh VPN Networks
A *Mesh VPN network* is a type of virtual private network (VPN) that connects nodes in a non-hierarchical, decentralized manner. Unlike traditional hub-and-spoke VPN architectures, which rely on a central concentrator or gateway, mesh VPN networks allow each node to connect directly to every other node in the network. This structure ensures data packets can travel along multiple paths, increasing redundancy, fault tolerance, and better load distribution.
<Frame>
<img alt="" />
</Frame>
<Frame>
<img alt="" />
</Frame>
#### Advantages of *Mesh VPN networks*:
1. **Robust**: Mesh networks are resilient to individual node failures, as there are multiple paths for data to travel. This redundancy ensures that the network remains operational when one or more nodes experience issues.
2. **Scalability**: Adding new nodes to a mesh network does not significantly impact the overall network performance, making it easy to expand the network as needed.
3. **Low Latency**: By connecting nodes directly, mesh networks reduce the number of *hops* needed for data to travel between nodes. This reduction in latency enhances the performance of real-time applications and distributed computing.
4. **Optimized Load Distribution**: Mesh networks distribute traffic more evenly across nodes, preventing bottlenecks and ensuring optimal performance.
### Implementation of the *io.net Network*
We built an io.net network that creates an efficient, resilient, and scalable networking backend. By adopting mesh networking principles, io.net delivers the following benefits to its users:
1. **Enhanced Performance**: io.net's mesh network architecture minimizes latency by allowing data to travel along the most efficient paths, optimizing application performance and user experience.
2. **Improved Resilience**: The decentralized nature of io.net's mesh network ensures that it remains operational even when individual nodes fail. This resilience translates to increased reliability and uptime for users.
3. **Seamless Scalability**: io.net's mesh network can easily grow to accommodate more nodes as the user base expands, ensuring consistent performance and adaptability.
4. **Distributed Computing**: By allowing direct connections between nodes, io.net's mesh network facilitates efficient distributed computing, which enables resource sharing and collaborative processing across the network.
### Decentralized Architecture and Privacy
The decentralized nature of mesh VPN networks contributes to their security and privacy. Some notable aspects include:
1. **No Single Points of Failure**: The absence of a central concentrator or gateway in mesh VPN networks eliminates the risk of a single point of failure, ensuring that the network remains operational even if individual nodes are compromised or experience issues.
2. **Anonymity**: Since data travels along multiple paths within the mesh network, it becomes more difficult for an attacker to trace the origin or destination of the data, enhancing privacy for users.
3. **Traffic Obfuscation**: Mesh VPN networks can employ techniques like packet padding and timing obfuscation to make it harder for eavesdroppers to analyze traffic patterns and identify specific users or data streams.
### Network Access Control and Monitoring
Next for io.net Network includes:
1. **Access Control Lists (ACLs)**: Nodes must define and enforce ACLs to restrict communication between specific nodes or groups of nodes, ensuring that sensitive data is only accessible to authorized parties and only available during the time they are hired for a specific cluster.
2. **Regular Auditing and Logging**: To maintain security and compliance, the io.net mesh VPN must be configured to allow us to perform regular audits and maintain logs of network activities, enabling administrators to identify and address potential vulnerabilities or breaches.
# IO Tunnels
Source: https://io.net/docs/guides/architecture/io-tunnels
Reverse tunnels technology provides a way to bypass firewall and NAT restrictions, enabling secure access to remote resources. This article discusses the concept of reverse tunnels, how they work, and how io.net uses them to simplify engineer access to AntMiners Clusters.
<Frame>
<img alt="" />
</Frame>
### Understanding Reverse Tunnels
A *Reverse tunnel* is a method to establish a secure connection from a client to a remote server by opening an inbound connection on the server side. This is the opposite of a conventional forward tunnel, where a client opens a connection to the server. By using reverse tunnels, engineers can access remote resources behind NAT routers and firewalls without the need for complex network configurations.
### How Reverse Tunnels Work
1. The remote server (IO Worker) initiates a connection to the client (engineer's machine) through an intermediate server (io.net server).
2. The io.net server listens for incoming connections from both the client and the remote server. Once the connection is established, data can be exchanged between the client and the remote server through the tunnel as if they were directly connected.
The io.net network employs reverse tunnels to simplify access to io.net miners for engineers.
The process involves:
1. The IO Worker establishes a connection to 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. Engineers can securely access and manage IO Workers without the need for complex network configurations or dealing with firewalls and NAT restrictions.
### Benefits of Reverse Tunnels
1. **Simplified Access**: Engineers can easily access IO Workers without worrying about network restrictions, port forwarding, or VPNs.
2. **Enhanced Security**: Reverse tunnels provide a secure communication channel, ensuring data privacy and integrity.
3. **Scalability**: io.net can manage multiple IO Workers simultaneously, allowing engineers to work efficiently.
4. **Flexibility**: Reverse tunnels work across various platforms, ensuring compatibility with different operating systems and environments.
# Overview
Source: https://io.net/docs/guides/block-rewards/block-rewards
## Table of Contents
* [What Are Block Rewards](/docs/guides/block-rewards/block-rewards#what-are-block-rewards%3F)
* [Block Rewards Allocation](/docs/guides/block-rewards/block-rewards#block-rewards-allocation)
* [Block Reward Nomination Requirements](/docs/guides/block-rewards/block-rewards#block-reward-nomination-requirements)
* [Block Rewards Nomination Checklist](/docs/guides/block-rewards/block-rewards#block-rewards-nomination-checklist)
* [Wallets](/docs/guides/block-rewards/block-rewards#wallets)
### What Are Block Rewards?
Block rewards are payments made to suppliers who provide their GPUs or CPUs to our network. This incentivizes supply-side network growth. These rewards are accrued hourly in ***\$IO***, following a predefined emission schedule. Rewards are potentially subject to slashing before distribution.
### Block Rewards Allocation
Block Rewards are credited to Suppliers on an hourly basis for making their GPU or CPU available on the *IOG Network*, thereby incentivizing supply-side network growth. This payout is in **IO Coin** and follows a predetermined emission schedule. The current allocation of block rewards from each hourly emission is:
* 95% to GPUs
* 5% to CPUs
The ratio of rewards may be adjusted in the future to manage network growth.
To learn more, see [IO Coin](/docs/guides/coin/io-coin).
### Initial Block Reward
**The first Block Reward was created on June 25th 2024 12:00 UTC.**
We will calculate and publish the initial block rewards, and block rewards use a claim mechanism that is similar to the *Ignition Program*. The first 7 days of block rewards were claimable together with *Ignition Reward Season 3*. Block Rewards for June 25th - June 30th will also be claimable.
<Info>
IO Device Level staking/Minimum staking is now required for Block Rewards. To learn more about staking, see [IO Staking](/docs/guides/staking/io-staking).
</Info>
*IOG Foundation* provides emission rewards to incentivize the correct growth of the IO ecosystem. To better align with *Ignition Reward Season 3*, the *IOG Foundation* has not requested io.net to cap the amount of devices eligible for block rewards. In the future, the *IOG Foundation* will monitor the reward distribution and may potentially cap the amount of devices eligible for the top percentage of nodes. A device cap is used to increase the alignment of the network's structure.
### Block Reward Nomination Requirements
The requirements below must be met to be nominated for a Block Reward:
* Device *Uptime* must be green for the past **5 hours**.
* The minimum stake for the device must be met. To learn more about staking, see [IO Staking](/docs/guides/staking/io-staking).
* The account holder for the device must have a valid Solana wallet.
* The device’s status is **NOT** terminated or unsupported.
* The device’s hardware multiplier is greater than **0**.
* The device’s connectivity tier is greater than **0**.
<Info>
When a block is about to close, we test your device for *Uptime* and *PoW* again.
</Info>
### Block Rewards Nomination Checklist
Click the caret on the right side of the status row (**Eligible** in the example) to open the **Block Rewards Nomination Checklist**. Each step of the verification status is displayed, with a green or red check that indicates success or failure. The checklist displays the **current status** of the device's eligibility for a block reward. In the example case below, if a new block was opening, this device would be eligible.
프로젝트로 돌아가기