Commit graph

661 commits

Author SHA1 Message Date
igneum-josh
cc89e3fbd8 Hero shortened on Josh's word (6 October 2026, 16:4x UTC): the same claims in 70 words; the reddit post saved as docs/posts/reddit-2026-10-06.md
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 17:20:01 +01:00
igneum-josh
0cf63749ce Review round 4 (reddit): the post finalised against the pages deployed at 16:12 UTC (399 words), the sections 5 and 6 notes updated
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:14:35 +00:00
igneum-josh
03357540cc Site truth, 6 October 2026: the ledger's stated sentences merged, the bounty struck, draft (a) on the chip line, the measured prover tiers, the ledger page, the evidence page generated from its source, the live scene reading the live state
Branch site-truth-2026-10-06 = master 2cf8851 + merge of ledger-text (the 45 conceded sentences of the 5 October close) + cherry-picks 6141e01, 8c5b02f (the bounty strikes) and 45d135e (review round 4 reddit) + this commit. The hero chip line follows the owner's pick of 16:25 UTC (draft (a) of docs/plans/counter-asic-3-status.md section 6 with the owner's last sentence). Every number carries its source beside it. No em dashes. Site build, identity-check.sh (0 hits over 224 files) and the private-string sweep of the built pages pass.

Changed sentences, before and after (lines are master's where the sentence existed):

site/index.html:343 hero
  before: A custom chip gains under 2x, and the model is public.
  after:  The strongest recompute chip we can price, holding the whole 256 MiB cache on-die, reaches under 1x per chip against an RTX 5090. A memory-controller chip that stores the whole dataset reaches 1.2x per chip and, in our model, 5x to 9x per joule; the Ethash chips of this class reached 2.1x to 4.8x. The lever against it, program work in the latency shadow, is measured and in its gates: it brings the chip to about 2x. The model is public: the numbers.
  before: An NVIDIA card with 24 GB or more proves every block and gets paid for it; AMD and Apple cards mine.
  after:  Every NVIDIA card from 8 GB proves and is paid for it; 12 GB and up mine and prove; 24 GB on the stock server (eleven rented cards, RTX 3060 to RTX 5090, 6 October 2026, docs/analysis/prover-tiers-real-cards.md). AMD and Apple cards mine.
site/index.html:372  before: miners active  after: vote keys active in 10 min (a card runs several)
site/index.html:400 and the chain scene script  before: the "proven" and "locked" counters counted the simulation while the scene carried the live label  after: in live mode the counters read the observer (proven = blocks in the window every shard of which is verified, "not active" while the proving layer is off; locked = locked checkpoints in the window) and the simulated shard sparks stop
site/index.html:484  before: One click. The card mines; an NVIDIA card with 24 GB proves too.  after: One click. The card mines; every NVIDIA card from 8 GB proves, 12 GB and up mine and prove.
site/index.html:492 and site/miner.html:266  before: (the app is still labelled Igneum Miner until 0.3.6)  after: (the app window still says Igneum Miner at 0.3.13)
site/litepaper.html:301 abstract  before: A custom chip gains under 2x, and the model is public; the claim is tested by paid independent cryptanalysis and the public benchmark.  after: draft (a) as on the hero, then the sources (chip-model-v3.md section 5; the Ethash rows of asic-resistance-history.md; Counter ASIC 3.0 item 8), then "The model is public; the claim is tested by paid independent cryptanalysis and the public benchmark."
site/litepaper.html:396  before: About one a second  after: About one a second with the full fleet; 0.65 a second over the hour to 16:00 UTC on 6 Oct 2026 with one PC off (the live page's hour count, 2,325 blocks)
site/litepaper.html:400  before: version 0.3.5; 0.3.6 staged  after: version 0.3.13 (6 Oct 2026); the app window still says Igneum Miner
site/litepaper.html:412  added after "not on maths or bandwidth.": Measured: an RTX 5090 hashes at 95 GB/s of useful 4-byte loads against 1,638 GB/s of sequential writes (engineering log, the RTX 5090 entries).
site/litepaper.html:424  before: It claims the gain is small, the response takes a week, and both are measured.  after: It states the gain its own model finds, the response takes a week, and both are measured.
site/litepaper.html:440 (vs RandomX, Useful work)  before: NVIDIA cards with 24 GB or more prove every block and sell proofs to other chains; AMD and Apple cards mine, ...  after: Every NVIDIA card from 8 GB proves; 12 GB and up mine and prove; 24 GB on the stock server (eleven rented cards, RTX 3060 to RTX 5090, 6 October 2026, docs/analysis/prover-tiers-real-cards.md); they sell proofs to other chains. AMD and Apple cards mine, ...
site/litepaper.html:452  before: Proving needs an NVIDIA card with 24 GB or more (32 GB until the fee switch of 6 October 2026; ...). AMD and Apple cards mine. A prover for them lands when a zkVM ships one.  after: Proving: every NVIDIA card from 8 GB proves; 12 GB and up mine and prove; 24 GB on the stock server. Measured on eleven rented cards ...: the RTX 3060 (12 GB) mines at 23.78 MH/s and proves the v1 shard beside its miner at an 8.9 GB peak in 37.5 s; the RTX 4060 (8 GB) proves it alone at 7.4 GB in 18.4 s; the RTX 4090 (24 GB) proves it on the stock SP1 server in 5.6 s at 17.4 GB. The patched server that fits the smaller cards is not yet in the shipped app. AMD and Apple cards mine. A prover for them lands when a zkVM ships one.
site/litepaper.html:454  before: The old 12 GB gate on the roadmap is withdrawn until a prover build with a smaller floor is measured.  after: ... was withdrawn on 5 October until a prover build with a smaller floor was measured; on 6 October a patched server proved the same shard at 7.4 to 8.0 GB alone on eleven rented cards from the RTX 3060 to the RTX 5090 (the real-card table), so the gate returns as measured and the patched server is not yet in the shipped app.
site/litepaper.html:562 (Hardware)  before: 24 GB proves full shards (measured on a 32 GB card's allocation; a 24 GB card has not run it yet) and 32 GB mines and proves on one card, measured 5 October 2026 on this prover build (a 12 GB card does not prove on it: the GPU prover's floor is 13.9 GB).  after: Every NVIDIA card from 8 GB proves; 12 GB and up mine and prove; 24 GB on the stock server (eleven rented cards, RTX 3060 to RTX 5090, 6 October 2026, docs/analysis/prover-tiers-real-cards.md).
site/litepaper.html:645 (Governance, admin keys)  appended: On the devnet the activation heights and one execution-state restart (6 October 2026) reach every node through the signed update manifest, so on the devnet the release key acts as the operator; the sentence above holds for mainnet consensus only once that path is closed, and the public testnet terms will say which parameters still travel that way.
site/litepaper.html, Questions miners ask  added: the entry "Don't ASICs make a chain safer?" (three parts and a five-row table; the rental row cites the fleet's bench entry that lands tonight and the 50-miner wave row reads "measurement tonight")
site/litepaper.html:733 (What Igneum does not claim, the chip item)  before: ... approximate; the claim is under 2x, the margin is stated on the numbers page, and the next lever is named there. No hash has stayed free of chips forever; Igneum does not claim to. Monero's seven years without a public chip are precedent, not proof.  after: ... approximate. The same model, drawn out to the chip that stores the dataset (6 October 2026): draft (a) with its sources. No hash has stayed free of chips forever; Igneum does not claim to. Monero's seven years without a public chip are precedent, not proof, and a small prize: they say nothing about the price of a chip with the 256 MB cache on its die, and that price is a cost model, not a measurement.
site/litepaper.html, the four bounty sentences (301, 424, 684, 686): struck as on ca2-coord 6141e01 and 8c5b02f
site/litepaper.html, the 45 sentences of the 5 October close: as on ledger-text d49eebb (merged)
site/miner.html:7, 13, 21 (meta)  before: and an NVIDIA card with 24 GB proves.  after: and every NVIDIA card from 8 GB proves.
site/miner.html:252  before: Install. Start. The card mines. An NVIDIA card with 24 GB proves too.  after: Install. Start. The card mines. Every NVIDIA card from 8 GB proves; 12 GB and up mine and prove.
site/miner.html:308  before: ... and, on an NVIDIA card with 24 GB or more, the prover. AMD and Apple cards mine;  after: ... and, on an NVIDIA card, the prover: every NVIDIA card from 8 GB proves; 12 GB and up mine and prove; 24 GB on the stock server (eleven rented cards, ...); the patched server for the smaller cards is not yet in the shipped app. AMD and Apple cards mine;
site/evidence.html  before: hand-kept, "30 claims · 4 Oct 2026", row 21 "unwritten"  after: generated by site/build.mjs from docs/evidence.md (31 rows, the counts, the date), scrubbed as /bench is
docs/evidence.md row 17  before: The chip resistance target: a chip gains under 2x over a GPU  after: The chip resistance claim: the strongest recompute chip under 1x per chip against an RTX 5090; the stored-dataset chip 1.2x per chip and 5x to 9x per joule in the model (2.1x to 4.8x by the Ethash precedent); the latency-shadow lever, measured and in its gates, brings it to about 2x
docs/evidence.md  the card-lifetime row numbered 22 under "What moved on 5 October" becomes row 31 of the table; "Hetzner VMs" becomes "cloud VMs", "recommended to Josh" becomes "recommended to the owner"
docs/fud-ledger.md, docs/fud-fixes.md  taken from fud-close dc12d76 (167 entries); two lines reworded for the identity check (the log key, the log intake)
site/ledger.html  new: every ledger entry with the critic's words, what was done, the status and the date, the count table on top (53 conceded, 54 fixed or built, 27 closed by rule or decided, 13 answered with evidence, 13 by design, 7 open); generated by tools/ledger-page.mjs
site/vercel.json  the /ledger redirect removed
site/partials/footer.html  "Ledger: every criticism" added under Read (so every page's footer changed)

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:12:30 +00:00
igneum-josh
131b2c5cf3 Review round 4 (reddit, 6 October 2026): eight personas, 2 fatal, 11 serious, 9 minor; the believe-list; site/ledger.html drafted from the ledger (167 entries) with its generator; six public-text fixes
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:06:42 +00:00
igneum-josh
b7776c81ba Counter ASIC 2.0: the last three bounty sentences struck (public levels, the litepaper's Kaspa answer, CA 3.0 item 4)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:06:41 +00:00
igneum-josh
4dfc5ed9cb Counter ASIC 2.0: no device bounty (Josh, 6 October, ledger M1); the claim backed by paid cryptanalysis and the public benchmark on every ca2 document and the litepaper
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:06:41 +00:00
igneum-josh
6916145453 Merge branch 'ledger-text' into site-truth-2026-10-06
# Conflicts:
#	site/downloads.json
#	site/index.html
#	site/journey.json
#	site/litepaper.html
#	site/miner.html
2026-10-06 16:05:58 +00:00
igneum-josh
39838206db release 0.3.13: the exec checks red at the close, the cause, the four rules, 0.3.14 named
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:52:54 +01:00
igneum-josh
373c288ea8 release 0.3.13: the incident after publish 2 (the activation inside the window, the deep reorg, the moved pruning point) and node 1's own eth port in restart-hand-nodes.sh
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:52:30 +01:00
igneum-josh
b988f3c364 release 0.3.13: PC 1's switch, the sweep, the proving agent's answers (the chain height reading; the exporter failures real until 0.3.14)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:46:26 +01:00
igneum-josh
d0cb5efd2f release 0.3.13: the rollout (both publishes, the exec checks, PC 2's exporter finding, PC 1 held for Ember)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:40:33 +01:00
igneum-josh
5ca4913bf5 release 0.3.13: merge master b79f2cb (docs)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:19:57 +01:00
igneum-josh
30974c1d75 release 0.3.13: CI green on be344ff, the installer and zip hashes; PC 1 first in publish 1, its switch after Ember
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:19:39 +01:00
igneum-josh
13fda758fd release 0.3.13: the third round's DMG and HiveOS rows
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:14:00 +01:00
igneum-josh
7c678bfe8d release 0.3.13: the fresh-joiner fix (node bb43e9a8), the third round of builds, the fresh-install check in the order
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:13:30 +01:00
igneum-josh
b79f2cb22a day record: afternoon (0.3.13 approved with the state reset, fleet phase 1, Ember, PC 1 three cards)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:12:04 +01:00
igneum-josh
744ba55961 release 0.3.13: the trust-window fix (node 544fc30f), the Ember merge (dry run 3 passed), the second round of builds
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:08:07 +01:00
igneum-josh
4deea567c5 release 0.3.13: merge ember-tune 32b2688 (master merged into the branch, the dry-run-3 bench entry, the playbook-quit gate's allow entry)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:05:00 +01:00
igneum-josh
fd1917c363 Merge master 494c9c7 into ember-tune (0.3.12's version files and the proving-v1 app merge; my own 7f6c4e6 came back as ebea8b6) 2026-10-06 16:03:37 +01:00
igneum-josh
71f08d5b9c release 0.3.13: merge ember-tune 07d5a72 (the Power Helper: one approval registers a per-user elevated scheduled task, no prompt after; the folder-lock ACL; the verbatim settings copy; the watchdog; no firewall prompt for a sweep engine; the jobrun follow_file)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:03:27 +01:00
igneum-josh
a3479af1ee bench log: dry run 3 passed (the first measurement engine on PC 1 that mined: 5090 127.31 MH/s at 316.5 W, 4070 28.68 MH/s at 102.7 W), the folder-lock finding measured on PC 1 and its consequence
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:03:18 +01:00
igneum-josh
2f58824eca release 0.3.13: the node suites on a9dfe78e (one new igneum-exec failure after 05e93f0e, the proving agent's)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 16:01:23 +01:00
igneum-josh
0cd24c2e9d release 0.3.13: the DMG and HiveOS rows
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 15:59:53 +01:00
igneum-josh
e483d13066 release 0.3.13: the state reset's figures (the proving agent's), the build rows, the digests (7bd98cc4 unchanged, b18ed271 with the thirteen-field object)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 15:59:16 +01:00
igneum-josh
0db091edd5 release 0.3.13: the state reset stated plainly (empty EVM state at chain block 27,276, what is gone and what re-derives), the line for Josh
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 15:54:22 +01:00
igneum-josh
b57ff27b86 release 0.3.13: the plan to the two-publish shape (the three exec-restart digest fields, protocol 16), the exec-sync merge a9dfe78e
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 15:53:04 +01:00
igneum-josh
e6c939ed10 release 0.3.13: merge fin-route (the bench-log entry on the finality route echo)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 14:21:35 +01:00
igneum-josh
05d0944d25 bench-log: the finality route, the certificate echo below the window (fork fin-route-0313 5a339733), before and after rates
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 14:21:19 +01:00
igneum-josh
e2c84e4701 release 0.3.13: the plan skeleton (node-only: the exec follower fix and the finality route fix; the hand-node swap first, one publish carried over)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 14:16:26 +01:00
igneum-josh
19edae08fc morning summary: since noon (0.3.12 out, the 4070, the fleet, Apple, the two fleet-found node bugs)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 14:01:28 +01:00
igneum-josh
53b50e81ba One administrator approval, ever (Josh, 6 October 2026 11:50 UTC): the first Power control approval also registers the per-user scheduled task 'Igneum Power Helper' (RunLevel Highest, no trigger, action = the app's own exe --power-helper); every later cap and every tune's helper starts the task and writes the command file, no prompt, across restarts, updates and reboots; Power control off sends remove and the task unregisters itself; the helper runs only fixed verbs with digit-only nvidia-smi arguments (threat note in ember-tune.md 7a); 4 tests
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 12:50:49 +01:00
igneum-josh
24fcf6d702 release 0.3.12: the plan's sections deduplicated and in order
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 12:47:55 +01:00
igneum-josh
6cb8653663 release 0.3.12: PC 1's minute at 0 MH/s after the switch (the C43 class); sections in order
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 12:47:32 +01:00
igneum-josh
f3328532d4 release 0.3.12: the rollout (the re-pin to 198,000, the two publishes, per-machine times, the sweep, the Mac pause on Josh's order)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 12:46:55 +01:00
igneum-josh
cf1ad2b350 release 0.3.12: merge master f11b02e (the morning summary, docs only)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 12:28:27 +01:00
igneum-josh
f11b02eddd morning summary: 12 GB mine-and-prove measured as a core-only prover
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 10:15:27 +01:00
igneum-josh
4d4da4e4ea release 0.3.12: the PC 2 job's place in the queue (one second before floor-build-6)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 10:14:21 +01:00
igneum-josh
92ea135218 release 0.3.12: the CI verdict (37440559793 on 88df58e), the gate stands
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 10:08:42 +01:00
igneum-josh
88df58e00d release 0.3.12: merge master d3b64cb (the morning summary, docs only)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 10:05:27 +01:00
igneum-josh
37b6a7ff74 pc2-agg-cost.ps1: pkill -f sp1-gpu-server at the end (the CI root-socket check); release 0.3.12: the PC 2 job, the Windows artefacts, the CI rows
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 10:04:33 +01:00
igneum-josh
0a71f315c9 release 0.3.12: the Windows exes, the second inputs push, the consensus-core fast-time finding
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:50:13 +01:00
igneum-josh
d3b64cbb5e morning summary: Counter ASIC 3.0 closed, the class v4 candidate and its gate decision
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:49:04 +01:00
igneum-josh
44b4d85539 release 0.3.12: the Mac node suites with the igneum-pow feature (the M20 era test known on 89dfcb95 too, the finality ban test flaky)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:46:49 +01:00
igneum-josh
ff6e624cd0 release 0.3.12: the plan's digests, the two-publish order, the line for Josh
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:45:23 +01:00
igneum-josh
4c63017031 release 0.3.12: the plan's node, prover, HiveOS and DMG rows for the widened cut
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:43:31 +01:00
igneum-josh
709413c143 release 0.3.12: the plan widens to the node change (the fresh-record rule switch, the segment-aligned prover)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:40:18 +01:00
igneum-josh
49e0e2c694 release 0.3.12: merge proving-v1 app aea2f6a (the segment-aligned prover, the held fresh record, the fresh-record rule harness)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:37:18 +01:00
igneum-josh
0f945f3c58 morning summary: the segment rule is a consensus switch; 0.3.12 carries the node
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:36:28 +01:00
igneum-josh
aea2f6a633 bench-log: the fast-time harness on the fresh-record rule, both cases
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:35:13 +01:00
igneum-josh
67e4945d51 release 0.3.12: the plan names the make-payload fix and the superseded first Windows run
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-06 09:34:25 +01:00