Getting Started with AIOZ DePIN CLI v1.2.5: A practical, first-time operator guide

With the release of AIOZ DePIN CLI v1.2.5, running an AIOZ DePIN CLI is more streamlined, resilient, and flexible, especially for operators contributing storage and delivery resources.

This article is a hands-on walkthrough for first-time operators. It guides you through your first successful run, from installation to reward withdrawal.

By the end, you will have:

• Installed the AIOZ DePIN CLI
• Generated a key and backed it up safely
• Started a live AIOZ DePIN CLI process
• Confirmed resource contribution
• Checked and withdrawn potential rewards

Before You Begin

1. Choose the right machine

The AIOZ DePIN CLI works best on machines that are stable and consistently online. Ideal setups include:

• An always-on desktop, home lab machine, or server
• A reliable wired or high-quality network connection
• A system not constantly overloaded by heavy workloads

For v1.2.5 specifically:

• Any supported machine can run the CLI
• Windows systems with compatible GPUs can additionally benefit from GPU transcoding support introduced in this release

2. Supported operating systems

AIOZ DePIN CLI currently supports:

• Windows: Windows 10 (22H2), 64-bit or later
• Linux: Ubuntu 14.04+, 64-bit
• MacOS: macOS Catalina (10.15) or later

Ensure your system has:

• Sufficient free disk space for cached data
• Enough CPU/RAM headroom
• Stable upload bandwidth for sustained delivery traffic

3. Network and wallet layout rules

Two principles help avoid common issues:

• Multiple devices behind one public IP: this setup is supported, but tasks will be shared. Each CLI instance will naturally receive fewer assignments.
• One wallet key per CLI instance: reusing the same private key across machines is unsafe and may cause signing or withdrawal errors. Treat each key as bound to one machine.

4. Basic safety awareness

You should be comfortable with:

• Using a terminal or shell
• Copying and storing files securely
• Understanding that mnemonics and private keys directly control funds

Always treat your AIOZ DePIN CLI key material as sensitive.

Install the AIOZ DePIN CLI

Download the correct binary for your OS from the official source, extract it, and confirm that it runs correctly.

• Windows:

1. Download and extract the latest Windows archive from the official README.
2. Rename the executable to aioz-depin.exe if needed.
3. From the folder containing the binary, run: .\aioz-depin.exe version

If the installation succeeded, the command prints the CLI version (for example, 1.2.5).

• MacOS or Linux:

1. Download the corresponding .tar.gz archive.
2. Extract and rename the binary to aioz-depin.
3. In the same directory, run: ./aioz-depin version

The output should show the current AIOZ DePIN CLI version.

If the version command fails or the shell reports “permission denied,” fix the executable bit: chmod +x ./aioz-depin.

Generate a CLI key (and back it up)

Each AIOZ DePIN CLI uses a unique key that includes:

• An AIOZ address (aioz1…),
• An EVM address (0x…),
• A public key + private key
• A mnemonic phrase for recovery.

From the directory containing the binary:

1. Create a new key

• Windows: .\aioz-depin.exe keytool new--save-priv-key privkey.json
• MacOS or Linux: ./aioz-depin keytool new --save-priv-key privkey.json

This command generates a new keypair, prints the addresses and keys, and writes the private key to privkey.json.

2. Back up securely (critical)

Immediately after generation:

• Store the mnemonic phrase offline or in an encrypted password manager
• Back up privkey.json, but never share it
• Never send keys or mnemonics to anyone

Important: If the mnemonic is compromised, the funds are compromised.

Check device status and contribution

Once the AIOZ DePIN CLI is running, verify storage and delivery activity:

• Windows: .\aioz-depin.exe stats
• MacOS or Linux: ./aioz-depin stats

You’ll see:

• Storage metrics, such as total items and total size.
• Delivery metrics, including upstream_speed, which reflects how fast the AIOZ DePIN CLI instance can send data.

If activity is slow:

• The device may not have received tasks yet
• Bandwidth may be limited
• Multiple devices may be sharing the same public IP address

You need to ensure that:

• The machine stays online.
• The connection is stable and not capped.
• Firewall rules are not blocking relevant traffic.

AIOZ DePIN CLI instances behind a shared public IP will see fewer assignments each, so it can take longer to see activity in the stats.

View rewards

After contributing resources, check reward balance:

• Windows: .\aioz-depin.exe reward balance
• MacOS or Linux: ./aioz-depin reward balance

The output includes:

• balance: current total rewards in attoaioz.
• storage_earned: rewards from storage work.
• delivery_earned: rewards from delivery or bandwidth work.
• withdraw: the amount already withdrawn.
• delivery_counter: number of delivery events

Note: On AIOZ Network, attoaioz is the smallest unit of AIOZ, where 1 AIOZ equal 10¹⁸ attoaioz.

Withdraw rewards safely

Once the minimum withdrawal amount is reached (1 AIOZ), use the withdraw command to send rewards to a wallet address on AIOZ Chain.

Example pattern: ./aioz-depin reward withdraw\

Key points:

• -address: is the destination address on AIOZ Chain.
• -amount accepts either aioz or attoaioz units.
• -priv-key-file must match the key used by the running CLI. Without it, the CLI will ask for the key via standard input.

After a successful withdrawal, the CLI returns a txid that can be checked on an AIOZ blockchain explorer.

To avoid exceeding the withdrawal rate limits introduced in version 1.2.5, group withdrawals into reasonable batches instead of triggering them repeatedly in quick succession.

Recover a key from mnemonic (if needed)

If the machine is replaced or privkey.json is lost but the mnemonic was backed up, the key can be restored using the keytool recover command.

• Windows: .\aioz-depin.exe keytool recover"your mnemonic phrase"--save-priv-key privkey.json
• MacOS or Linux: ./aioz-depin keytool recover"your mnemonic phrase" --save-priv-key privkey.json

This recreates the private key file and prints the associated addresses. Run recovery only on trusted machines.

After recovery:

• Restart the CLI using the restored privkey.json
• Confirm the reward balance is correct

Troubleshooting and next steps

If the CLI does not behave as expected, a few checks cover most first-run issues:

• CLI will not start: Verify the OS version, file permissions, and that the -priv-key-file path is correct and readable.
• No stats or rewards after a long time: Check uptime, no firewall or router rules block outbound traffic, and ensure the machine has enough upload bandwidth.
• Withdraw fails repeatedly: Confirm that the amount is at least the minimum, the address is valid, and that withdrawal attempts are not exceeding the rate limit.

For advanced configuration:

• Refer to the complete AIOZ DePIN CLI documentation for advanced flags and operational details.
• Reach out through community channels with logs and environment details.

Final thoughts

Running AIOZ DePIN CLI v1.2.5 is straightforward once the fundamentals are in place. With a stable machine, a securely backed-up key, and consistent uptime, operators can reliably contribute resources to the AIOZ DePIN network while tracking their potential rewards with clarity.

This guide covers the complete first-run path—from installation and key generation to operation, verification, and withdrawal—so you can get started smoothly and build from a solid foundation.

With these steps completed, a new operator has:

• Installed the current AIOZ DePIN CLI.
• Generated and backed up a key.
• Started an AIOZ DePIN CLI process that can auto-update and survive restarts.
• Confirmed stats and rewards.
• Executed a withdrawal in a controlled way.

Download the AIOZ DePIN CLI today to explore what v1.2.5 brings, including GPU transcoding support on Windows alongside ongoing storage and delivery contributions.