The public test
1. What this is
Igneum 2.0 runs on Devnet 4 (network id igneum-devnet-4, chain id 4465), software version 2.0.3. The public test is an open invitation to run that software on your own card, on your own machine, and report what happens. It is a test. Coins on this network have no value, cannot be bought or sold, and the chain may be reset; nothing here is a launch, a sale or an offer.
The test opens when the five gates in section 5 read green. From that morning a 30-day clock runs on one question: how many operators the project does not control keep a node and a miner on this chain, and what breaks for them. The project's own fleet is counted separately and is never mixed into that number. The monetary gates of the Token Value volume, counsel's review and the 90-day observation period are not part of this test and are not shortened by it.
What the test proves, if it passes: that a stranger can install the software on Windows, macOS, Linux or HiveOS, sync, mine, prove where the card allows it, and ride through the hourly program changes and the weekly epoch cuts without a hand from the project. What it does not prove: that the token has value, that the chain is final in the sense a mainnet needs, or any claim about chips beyond what the resistance page states in its own words. The one headline that page supports today, verbatim: "the only live GPU network whose GPUs earn income a chip cannot (LIVE on Devnet 4: one epoch, 928 shard and 86 aggregation records, 1,453.53 IGN to 15 prover keys, 51 percent of the pool's credit), with the chip-to-GPU edge of every live chain measured the same way on the same cards and published with its attacker"; the test is where an operator's own card, not the project's fleet, earns that income.
2. Join, per platform
Every download comes from this domain only (/download); check the sha256 the page shows. One install carries the node, the miner and, where the card allows it, the prover.
| Platform | What to install | What you need | Notes |
|---|---|---|---|
| Windows 10 or 11 | the installer from /download#windows | an NVIDIA, AMD or Intel card with 4 GB or more; 32 GB of memory for a fresh sync this cut | SmartScreen shows "Windows protected your PC" on an unsigned build: More info, Run anyway. The installer's one administrator prompt turns on the Windows Subsystem for Linux for the proof verifier; the app installs the rest itself. On a machine under 32 GB the app does not start a fresh sync and says so; the snapshot sync of 2.0.3.1 is that machine's route. |
| macOS, Apple silicon | the disk image from /download#mac | an M-series Mac; 16 GB works | On first open macOS says it cannot verify the app: System Settings, Privacy and Security, Open Anyway. A 16 GB Mac completes a fresh sync in about an hour on swap and feels slow until the node reads synced; this holds until 2.0.3.1. |
| Linux | the tarball from /download#linux | an NVIDIA or AMD card; 64 GB of memory for a fresh sync from genesis today | The flight sheet on the download page. The number falls when snapshot sync ships. |
| HiveOS | the package from /download#hive | a rig with NVIDIA cards | The package waits for the node to sync before it mines. HiveOS mines only in 2.0.3; its prover entry is being cut. |
The memory note, plainly: a fresh sync from genesis needs 64 GB of memory on Linux and Windows today, because the node holds the chain's execution state in memory as it replays it; a 16 GB Mac syncs on swap; the snapshot sync of 2.0.3.1 brings a 16 GB machine in without the replay, and this page says so when it ships. A 2.0.3 install dials five targets by default: the three hubs and the two public nodes on the build host; a node that cannot reach any of them says so in its log.
What your card does once it is in: any 4 GB card mines; an NVIDIA card of 24 GB or more proves the shard beside its miner by default; a 16 GB card holds no shard. The rates the project measured per card are on /miner#card and the bench table on /miners; your own rows are welcome (section 3).
3. What to report, and where
The Discord is the one place: discord.gg/igneum. Read #start-here and #rules first (three rules). Then:
| What happened | Where | What to include |
|---|---|---|
| The install or the app will not start, sync or mine on Windows | #support-windows | the app version (the window's About), the card and driver, the Windows version, the line the app shows, the log the Logs button opens |
| The same on a Mac | #support-mac | the app version, the Mac model, the macOS version, the line the app shows, the log |
| The same on Linux or HiveOS | #support-linux-hiveos | the package version, the card and driver, the flight sheet or command, the last 50 lines of the log |
| Your card's rate and watts | #benchmarks | one row: card, driver, OS, app version, MH/s, W, the command or the app's setting; the bench table is built from rows like these |
| Your first block | #first-block | the bot posts it; reply under it with your card if you like |
| Mining talk, settings, what your card is doing | #mining | say the card, the OS and the app version |
| A node you run without mining | #node-runners | the version, how it dials, what it sees |
| Proving on a 24 GB card | #proving | the card, what the app shows under proven, the shard times |
| Something that looks like a chain fault: a fork, a stall, a reset you did not expect | #devnet | the time (UTC), your node's height and tip, the lines around it; the project's incident posts are in #incidents |
| A criticism of the design or a claim on this site | #ledger | the claim as served, what you think is wrong, your source; it gets a ledger id and a dated answer on /ledger |
The hourly numbers from the public API post to #network-feed (height, hash rate, keys, the last lock). An incident is posted in #incidents when it opens and when it resolves, with the cause and the fix. Nothing you report is private; say nothing you would not say in public.
4. The rules of the test
- The software updates itself when you let it at install; a test on an old version is still a report, say the version.
- Every machine mines solo on its own keys; there is no pool during the test. Outside pools are listed on #pools only with a signed statement.
- The project's fleet, the hubs and the build host's nodes are the project's and are counted apart from independent operators.
- A fault with a software fix is fixed and shipped; it is not held for a word. The incident post names the fix and its version.
- The project does not touch your machine. There is no remote execution in the public build.
5. The five gates, with their state
The test opens the morning after all five read green. The state column is read from the project's record by the site lane; the time it was read is on the row.
| Gate | What green means | State at 14:0x UK, 9 October 2026 |
|---|---|---|
| 1. 2.0.3 on the hubs and the fleet | the three hubs and the project's fleet run node 27f54124 on one chain | in progress: the hub canary passed its sync; the hubs move one at a time on its pass; the fleet rolls after |
| 2. A 16 GB machine joins by snapshot sync | a fresh install on a 16 GB machine reaches the tip without the full replay | not yet: the snapshot-sync branch (2.0.3.1) is green on six test suites; the first served snapshot and the 16 GB canary are due this afternoon |
| 3. Mac, Windows and HiveOS 2.0.3 entries on their canaries | each package installs, syncs, mines and updates itself on a machine the project does not hand-hold | Mac: canary passed (the reboot leg not run, held by the founder); HiveOS: canary in its last blocks; Windows: being cut; the entries publish on the hubs' line |
| 4. One tip held through two epoch cuts after the roll | every public node on one chain across two weekly cuts with no restart by hand | not yet: counted after gate 1. Finality is locking again since 13:52 UK (the first lock after the pause, checkpoint 2224 of 2225, 84.5 percent of active weight, locks at cadence since) |
| 5. The served claims in the approved wording, both conventions | /resistance serves the approved wording verbatim, the measured card rows, both conventions, the coexistence table and the two phases with their labels | green: landed on the repository's master at 13:29 UK on 9 October (commit bba8a927) and served |
When all five read green the state column changes here, the announcement goes to #announcements and the 30-day clock starts; the start date is written on this row when it happens.