Getting Started with AIOZ DePIN CLI v1.2.6: Setup, Upgrade, and AI Compute Participation

Getting Started with AIOZ DePIN CLI v1.2.6: Setup, Upgrade, and AI Compute Participation

With the release of AIOZ DePIN CLI v1.2.6, AIOZ DePIN operators can now contribute not only storage and delivery, but also AI compute workloads within the same operational lifecycle.

This step-by-step guide explains how to set up v1.2.6, verify AI compute participation, monitor activity and rewards, and safely upgrade from a previous version.

This article focuses on operational flow and decision points. Detailed command syntax, flags, and low-level references are documented separately in the official documentation.

Step 1: Prepare the AIOZ DePIN Environment

Before starting, ensure your environment meets the required conditions.

  • OS Support: AIOZ DePIN CLI v1.2.6 supports Linux, macOS, and Windows
  • Connectivity: A stable internet connection
  • Permissions: Write access to directories used for configuration, cache, and runtime data

For testing, consider using a local home directory. Storing data in the current working directory makes it easier to reset the environment without affecting other setups.

Step 2: Create or Import a Private Key

A private key is required to identify your participation on the AIOZ Network.

You may:

  • Generate a new private key
  • Recover an existing key using a mnemonic phrase
  • Reuse an existing private key file

The same key is used consistently across storage, delivery, transcoding, and AI compute participation.

NOTE: Never share the private key file or mnemonic phrase. Treat these credentials as sensitive and store them securely, especially in shared or automated environments.

Step 3: Initialize the DePIN Home Directory

Initialization prepares the DePIN directory structure, generates baseline configuration files, and creates the required runtime context.

  • If you rely on a custom directory layout, set the DePIN home directory during initialization so future runs use the same location.
  • If you prefer the default behavior, the CLI automatically applies a default home directory.

NOTE: Initialization can be skipped in some setups if you start directly, but explicit initialization is recommended for predictable behavior and easier troubleshooting.

Step 4: Start the DePIN Runtime

Start the runtime using your private key file.

When the runtime starts, storage and AI compute services are launched within the same environment. Health monitoring begins immediately and checks all services at regular intervals. If a service fails, the runtime attempts automatic recovery using controlled backoff strategies.

The runtime also supports automatic update mode. When enabled, the CLI periodically checks for new versions and performs a controlled restart to apply updates without manual intervention. This helps long-running environments remain aligned with the latest stable release.

NOTE: At this stage, the AIOZ DePIN environment is actively participating in the network.

Step 5: Verify AI Compute Availability

After startup, verify that AI compute is available using the CLI's operational status commands.

AIOZ DePIN CLI v1.2.6 provides a consolidated view of DePIN services, including AI compute availability and supported AI task information. This allows participants to confirm AI readiness without relying solely on logs.

If AI compute is not reported as available, review runtime logs and perform basic system checks, including disk space, network connectivity, and directory permissions.

Step 6: Monitor Activity and Rewards

Use monitoring commands to inspect activity across storage, delivery, transcoding, and AI compute.

Statistics and rewards are aggregated using standardized outputs, allowing participants to review AI compute rewards independently while maintaining a unified operational view across all services.

Step 7: Configure and Validate Storage Limits

If explicit control over disk utilization is required, set a storage limit using the storage management commands introduced in v1.2.6.

After setting a limit, verify that the updated value is reflected in storage information outputs. Storage limits are enforced within valid bounds based on current usage and available free space, and allocation is managed consistently across IO and AI services.

NOTE: This step is strongly recommended for shared machines, constrained disks, and repeatable QC testing environments.

Step 8: Withdraw Rewards and Track On-Chain Settlement

Reward withdrawal behavior has been refined in v1.2.6.

Withdrawals now follow a simplified command syntax and return only transaction identifiers, allowing participants to track settlement directly on-chain without relying on amount fields in the response.

NOTE: If you maintain automated withdrawal workflows, update them to store and track transaction identifiers instead of parsing withdrawal amounts from responses.

Upgrade Guide: Migrating from CLI v1.2.5

If you are upgrading from v1.2.5, complete the following steps before deploying v1.2.6 in production:

  • Update withdrawal commands to use positional arguments instead of flags.
  • Review any JSON parsing logic that depends on older response formats.
  • Explicitly configure the DePIN home directory if your setup relies on custom paths.

Completing these steps before deployment helps avoid silent failures in automation and long-running operational workflows.

Conclusion

AIOZ DePIN CLI v1.2.6 provides a more structured and extensible foundation for DePIN participation within the AIOZ Network.

By integrating AI compute into the same lifecycle as storage and delivery, this release enables broader workload participation while maintaining predictable and manageable operations.

About the AIOZ Network

AIOZ Network is a DePIN for Web3 AI, Storage, and Streaming.

Powered by a global community of AIOZ DePINs, AIOZ rewards you for sharing your computational resources for storing, transcoding, and streaming digital media content and powering decentralized AI computation.

Find Us

AIOZ All Links | Website | X | Telegram