diff --git a/site/404.html b/site/404.html index f01382b6f..24a8e1fc0 100644 --- a/site/404.html +++ b/site/404.html @@ -56,24 +56,24 @@ main{flex:1}
Your rate, what it costs a day, and the chain drawn live with your own blocks ringed. One window, four pages, every card one row.
One big number: your hash rate. Beside it, watts, hashes per watt, and what the electricity costs a day at your price. Then the chain itself, as it grows.
One row per card: rate, watts, hashes per watt, pounds a day, temperature, a Tune button and a switch. Ember Tune walks each card through its power steps and keeps the point with the most hashes per watt.
Ember run 6 on the three-card Windows rig. The pounds are arithmetic from the saved watts at 28p per kWh; the app uses your price. The log.
This is the live devnet, drawn by the same code the app ships. Every square is a real block; a lane per miner; a ring where a checkpoint locked. In the app, your own lane is marked.
120 s of blocks on screen. Hover or tap a block for its hash, miner and proof state. Ctrl or cmd and scroll, a pinch, or a click into the scene zooms the window.
What you made, where it goes. IGN from blocks and from proofs, the electricity at your price, and the address every block pays.
Every block is turned into a short proof, in pieces called shards. Your cards prove the shards the chain assigns to them and earn IGN for each one.
The same window on a narrow screen: the big button, the number, the chain, then the tabs.
Measured against a worker that misbehaves on command, 4 October 2026: recoveries in seconds. The log.
Download only from this domain. Nobody from Igneum will ask for your seed.
Your card: pending
Public testnet: not yet open; the devnet build is here for people who want to look.
Devnet. Coins have no value and the chain may be reset.
Install the miner, press Start, and the address it makes is the one the wallet imports with one click.
Every claim the homepage and the litepaper make, one row each, with one of five labels: designed (a decision, no code), implemented (code with passing test vectors), tested by the team (measured by the project on a named machine, in the engineering log), reproduced externally (a third party ran the published command and got the published result) and reviewed independently (a named outside reviewer published a finding on that version). Nothing on this chain has been reproduced externally or reviewed independently; every row says so. A label belongs to the exact version in the row, and an audit of one version never covers a newer one. The 12-node cloud network of 4 October 2026 is the project's own, so its rows are tested by the team, not reproduced externally.
docs/plans/funding.md
Statuses are honest as of 6 October 2026, the day this page was generated from docs/evidence.md, and change only through that file.
Statuses are honest as of 7 October 2026, the day this page was generated from docs/evidence.md, and change only through that file.