Nesa Miner Rewards CLI

A one-command CLI for eligible Nesa miners to check their rewards allocation and submit a claim to an EVM address.

The CLI is intended to be run on the same machine that performed mining, because it reads the miner's local private key file, derives the miner identity, and signs a claim request locally. The private key is never intentionally sent to the rewards server.

Claim window

The claim process is scheduled to open on:

June 24, 2026 at 8:00 PM Singapore time (SGT / UTC+8)

The claim window will remain open for one month.

That is equivalent to:

• June 24, 2026 at 12:00 PM UTC
• June 24, 2026 at 7:00 AM US Central Daylight Time

One-line usage

bash <(curl -fsSL https://raw.githubusercontent.com/nesaorg/miner-rewards-cli/main/claim-rewards.sh)

For non-interactive usage:

bash <(curl -fsSL https://raw.githubusercontent.com/nesaorg/miner-rewards-cli/main/claim-rewards.sh) -y \
  --evm-address 0x1111111111111111111111111111111111111111

Recommended safer usage

Because this script reads a local private key file to sign the claim request, we recommend inspecting the script before running it:

curl -fsSL https://raw.githubusercontent.com/nesaorg/miner-rewards-cli/main/claim-rewards.sh -o claim-rewards.sh
less claim-rewards.sh
bash claim-rewards.sh

What the CLI does

The CLI performs the following steps:

1. Reads the miner private key from a local .env file.
2. Derives the miner's Cosmos address.
3. Derives the miner/node ID.
4. Shows the detected identity and asks the user to confirm.
5. Calls the rewards server allocation endpoint.
6. Shows the allocation in both aNES and NES.
7. Shows Terms of Use and privacy guidance.
8. Prompts for the EVM address to receive the claim.
9. Signs a claim payload locally.
10. Sends the signed payload to the rewards server.
11. Prints the transaction explorer URL so the user can check status.

Default private key file

By default, the CLI reads:

~/.nesa/env/orchestrator.env

The file must contain:

NODE_PRIV_KEY="<64-character-private-key-hex>"

The key must not be 0x prefixed.

Example:

NODE_PRIV_KEY="0000000000000000000000000000000000000000000000000000000000000001"

Do not use the example private key for anything real.

Custom private key path

bash claim-rewards.sh --private-key-path /path/to/orchestrator.env

Or with the one-liner:

bash <(curl -fsSL https://raw.githubusercontent.com/nesaorg/miner-rewards-cli/main/claim-rewards.sh) \
  --private-key-path /path/to/orchestrator.env

Non-interactive mode

Use -y to skip prompts. This requires --evm-address.

bash claim-rewards.sh -y \
  --evm-address 0x1111111111111111111111111111111111111111

Using -y means you accept the Terms of Use and want to submit the claim automatically if eligible.

CLI arguments

Argument	Default	Description
-y, --yes	disabled	Skip interactive prompts. Requires --evm-address.
--evm-address	none	EVM address that will receive the claimed rewards.
--private-key-path	~/.nesa/env/orchestrator.env	Path to .env file containing NODE_PRIV_KEY.
--bech32-prefix	nesa	Cosmos Bech32 prefix used to derive the wallet address.
--allocation-endpoint	production rewards server URL	Rewards server allocation endpoint.
--claim-endpoint	production rewards server URL	Rewards server claim endpoint.
--bridge-url	Nesa bridge URL	Bridge URL shown after claim.
--explorer-base-url	https://explorer-evm.nesa.ai	Explorer base URL used to display the transaction link.

Privacy recommendation

For privacy, claim to a fresh EVM wallet address that has not been publicly linked to your validator, miner, personal wallet, exchange account, or other on-chain activity.

Transaction status

The CLI reports when your claim transaction has been submitted. Submission does not guarantee that the transaction has finalized successfully. Always check the transaction status on the explorer URL printed by the CLI.

Explorer:

https://explorer-evm.nesa.ai

Bridging reminder

If you bridge funds to a separate chain with a different gas token, deposit directly to a destination address that already has gas, or to an address that is strictly a deposit address. On the bridge page, you may be able to adjust the destination address by clicking the destination address field before submitting the bridge transaction.

Security notes

• The private key is read locally and used to sign the claim payload.
• The private key is not intentionally sent to the rewards server.
• The rewards server verifies the submitted signatures before processing a claim.
• The CLI should be downloaded from the official repository only.
• Users are encouraged to inspect the script before running it.

Support

If the CLI reports an error, copy the final Summary section and share it with the support team on Discord. Do not share your private key or mnemonic.