Install. Start. The card mines and proves.

One button starts the node, waits for sync, starts one miner per card and, on an NVIDIA card, the prover. Today's app, with the stock SP1 server: a 24 GB card proves the full shard (RTX 4090 5.6 s, RTX A5000 6.4 s) and a 32 GB card mines and proves (RTX 5090, 8.4 s); the stock server refuses 16 GB and under. Measured on 6 October 2026 on eleven rented cards, RTX 3060 to RTX 5090, with the patched server: every NVIDIA card from 8 GB proves, and 10 GB and up mine and prove; ships when the packaging row lands. AMD and Apple cards mine; a prover for them lands when a zkVM ships one. Quit stops them in order.

NVIDIA through the driver, AMD and Intel through OpenCL, Apple silicon through Metal. Real card names, one worker per card.

A payout key made on your machine and locked to your user, with a backup step before mining starts. Or paste an address you already hold.

Every block this machine finds pays one address in IGN. The Earnings page counts blocks this run and for life, IGN from proofs, and the electricity cost at your price. £ earned stays 0.00 on devnet and says why; a market price fills it in when one exists (coming). The wallet shows the balance.

An installer on Windows, a disk image on macOS, a package on Linux. No toolchain, no driver work: the GPU workers are prebuilt.

A custom miner for farms: the Linux miner, node and both GPU workers with the four Hive hooks. Hive itself is untested: report what breaks.

An Apple silicon laptop, no instructions beyond the five steps: 33 accepted blocks in 7 minutes, 0 rejected, 21.0 MH/s average.

An RTX 5090 on Windows from the installer: 117 to 119 MH/s, 34 accepted blocks in the first minute, CPU re-check OK on every share.

Proving is a switch. On, the client proves the shards the chain assigns to this machine's keys, submits the record to its own node and goes back to hashing. The Prove page shows one sentence per card on what it can prove and one line of counts: assigned, proven, paid, IGN.

Identities take turns on the card and each one votes and pays separately. 8 suits a big card, 2 a small one, 1 an integrated GPU.

The node announces the next seed early. The worker compiles the next program in the background and swaps at the boundary while the current one mines.

The manifest is signed with an Ed25519 key compiled into the app. The app verifies the bytes before it reads them, then checks the download's size and hash.

Node synced, no hourly boundary within 3 minutes, no worker starting. Machines take turns, each in its own minute of the hour, and never while the network lost over 30% of its identities in 10 minutes.

The download and the staging run while the card mines. The swap itself takes seconds. If the new version fails to start twice, the previous one comes back by itself.

At once when a consensus activation is within 1,800 blocks or the version is below the minimum supported, or when you click Install now.

At every hourly prepare the worker compiles the program in several shapes (unroll, load path, register budget, threads per group), times each for 2 seconds and keeps the fastest for the hour. Base keeps its place unless beaten.

On the M5 Max, 256-thread groups ran 17.3% and 21.2% faster than base on two programs, under load from other work. The NVIDIA race is built and has not yet run on a GPU.

Every race is one record in the app log. The fleet's best variant per card model goes back out inside the signed update manifest, so a card starts from the known best and keeps racing.

Tunes every card for hashes per watt: once after install, then every 7 days, and after a driver or program change. The app steps the power limit and the core clock on the live kernel, 60 seconds a step, and keeps the point with the best MH per watt within 1% of the card's top rate. The memory clock is never touched; a step with a rejected hash, a hot GPU or a dragged memory clock is reverted and marked. Every result feeds a fleet prior per card model that the next card of that model starts from. One goal for all cards: Efficiency, Balanced or Maximum, with about how many pounds a day at that goal.

Setting an NVIDIA power or clock limit needs administrator rights on Windows. The app asks once, when you turn Power control on, and registers a helper task; every cap after that is set through the task with no prompt. Off, NVIDIA cards are measured only. AMD cards are set through the app's own helper with no prompt at all.

A block built on a stale tip earns less. The miner is moving from polling to a template subscription and shorter jobs, so a new tip reaches the card in milliseconds. In progress, no number published yet.

Our own fleet only. A switch, "Allow remote jobs from Igneum (signed)", with the key's fingerprint beside it. Off aborts the running job and stops polling. Jobs run at most once each and only on the machines they name.

No status line for 90 seconds, or a hash rate of 0 for 60 seconds while synced: the miner is restarted once. If it recurs, that card is marked faulted with the reason and the other cards keep mining.

A node that answers nothing for 120 seconds is restarted by the app, with a growing delay when it repeats. Measured: silent node to mining again in 160.0 s.

Miners first, then the node, on quit and on update. What crashes comes back. A worker that restarts itself is left alone, so nothing is restarted twice.

A clock 60 seconds slow kept a node silently dead for 12 minutes. Now the app reads block times and an HTTPS Date header: over 5 seconds a warning, over 10 seconds Start is blocked and a Sync clock button appears.

Every benchmark and test the project has made, with the hardware and the commands. Newest at the bottom.

One row per card, generator version and miner version: best MH/s, MH per watt where measured, the date and the log entry behind each number.

The app uploads its status lines once a minute under a per-install id. Rows marked "reported by the fleet" come from machines we do not own.