
Igneum Miner
Mined by GPUs. Proven by fire. This app runs a node on this machine and mines Igneum with your graphics card.
Nobody from Igneum will ever ask for your seed.
Your GPU
Asking the graphics cards to report in.
Igneum caps each NVIDIA card's power at 80% of its default limit to keep it stable. This needs administrator rights once, when mining starts; the limit goes back to what it was on quit. Settings has a slider per card.
Each card you switch on gets its own worker. An integrated GPU is off by default: it is slow and shares the machine's memory.
Where should rewards go?
Every block this machine finds pays one EVM address. Pick one way. One block in 100 pays the miner software's dev fee; Settings turns it off.
Your GPUs
Your blocks
Activity
Prove shards on this machine
Every block on Igneum is turned into a short mathematical proof, in pieces called shards. The chain assigns shards to your keys; this machine proves them and is paid for each one. On by default on an NVIDIA card with 24 GB or more (a full shard needs 20.4 GB of GPU memory, measured); off on a Mac, whose CPU prover is slow.
Off. Switch it on and this machine proves the shards the chain assigns to its keys.
Verifier
Before a proof counts, the node checks it. A node without a verifier passes proofs along and never includes them.
Program
Every proof names the program that made it. Other nodes accept a proof only from these two ids.
Rewards address
Every block this machine finds pays this address.
Save your key
The key for this address was made on this machine and is stored in the app folder, readable by your user only. Keep a copy somewhere safe: anyone with the key can spend what the address holds.
Use another address
Paste an EVM address you control. The miner restarts and pays the new address from the next block.
Chain
Headers arrive before blocks. The DAA score counts blocks the whole network made; the difficulty is how hard the next one is to find.
Consensus
The fingerprint of the rules this node runs. Every node on the network shows the same one; a peer with another is refused.
A switch is a planned rule change. The node applies it by itself when the chain reaches that height.
Finality
A lock is a point the miners have agreed can never be undone. This machine votes on one every 30 s.
Sync
Igneum Miner
Not checked yet.
Downloads in the background and installs at a quiet moment, never mid-program. Off: it downloads, then waits for Install now.
Remote jobs
Igneum publishes signed jobs (a benchmark, a script, logs to collect) next to the update manifest. This machine runs each one once and reports back. Only jobs signed by Igneum's key run.
Graphics cards
Once after install, then weekly and after a driver or program change: the power limit steps from 100% down to 50%, then the core clock from its maximum down to 60%, 75 s a step on the live program; the memory clock is never touched. The card keeps the point with the most hashes per watt within 1% of its top rate. A step with a rejected hash, a hot GPU or a dragged memory clock is reverted. A card whose model the fleet already knows starts at that point and confirms it in two steps. Every result goes back to the fleet without anything that identifies you. A cap you set by hand is left alone.
Windows asks for administrator rights once; the NVIDIA cap and the tune need them. Off, the app never asks and NVIDIA cards measure only. AMD cards need no rights.
This machine
The miner opens when you sign in and keeps mining in the background.
Signed jobs from Igneum run on this machine and report back. Updates shows what ran.
Your miner signs a checkpoint every 30 s. Votes are what lock the chain; leave it on.
A label for you only. Keys come from the machine id , never from the name.
Dev fee
One block in 100 is mined for the miner software's author, the same way every GPU miner takes a fee. The protocol itself takes nothing. This switch turns it off.
Logs
Copies the last lines the node and the miner wrote, for a support message. Show the log opens the drawer with every line.
Advanced
devnet tools
Devnet only. When no verifier is found next to the engine, the node includes proof records it never checked. A found verifier always wins. Changing this restarts the node.