Verify

Everything here is yours to check.

A mining tool asks you to run a program and give it a wallet. That is a lot to ask. So every claim on this site is built to be checked by you, with public tools, in a few minutes. Here is exactly how.

Three things to check

A row of linked blocks receding into the dark — the chain that carries the contracts.

01

The contracts

Read the code that is actually running

Start with the live release manifest and official contract addresses. Inspect each contract on the Robinhood Chain explorer, including its source, roles and privileged functions. A published address alone does not establish source verification or a security audit.

How you check it — Compare the full address with the release manifest, then check its deployed code, source-verification status and transactions.

A single computer glowing in a dark room — the miner running on your own machine.

02

The miner

Confirm the program matches the open source

The public CLI includes source code, release checksums and GitHub build attestations. Verify the downloaded package against the exact release and source commit, or build it yourself. These checks establish provenance; they do not prove the software is bug-free.

How you check it — Follow the release verification guide to check both the checksum and build provenance before running a downloaded package.

One ornate key alone on a dark surface — the key that stays yours.

03

Your wallet

Use a separate mining wallet

The browser app connects to MetaMask for entry, funding and HUNTER locks. Proof submissions use a separate mining wallet created or restored on your device. It holds the ETH you fund and the NFTs you mine. Keep its encrypted backup and passphrase safe; losing access can mean losing those assets.

How you check it — Save the encrypted mining-wallet backup before mining. Never share a private key or passphrase with support or a social account.

Wallet handling

Four facts about how it handles money

It signs locally

Your key is used to sign on your own computer. Only the finished, signed transaction leaves the machine — never the key, never the passphrase.

It is encrypted at rest

Downloaded mining-wallet backups are encrypted. Use a strong, unique passphrase and store the backup safely.

It has a spending limit

The browser has a run budget. The CLI max-fee setting limits each transaction, not the total session. Review these limits before starting.

Review evidence has limits

Source verification, automated tests and security review are different checks. Read the published evidence for the exact release; none guarantees that bugs or losses are impossible.

One honest note

Check what each tool actually verifies

A scanner may not support every chain or contract. An unsupported result is not a security assessment. Use the official addresses and release manifest, inspect onchain activity and source-verification status, and read the release evidence.

Checked it? Start mining.

Use a separate mining wallet, save its encrypted backup and fund only the ETH you intend to spend on network fees.