Ledger · 26 entries · regenerated from the repository

Every criticism, answered
or conceded.

Every criticism Igneum 2.0 expects, in the critic's words, with the status today, what answers it and the pin of the 2.0 plan it answers. 26 entries, written fresh on 8 October 2026. A pin closes only with a landed document and its pass condition met, so anything not yet delivered says Open and names the pass condition. Where the critic is right the entry says Conceded. Entries are never deleted; a status that changes keeps its history. Help is welcome: pick an open row and write to hello@igneum.network with its id.

CountStatusMeaning
12Nothing has settled it yet. The entry names what will
5The critic is right. "Stated" means the public text says so; "not yet stated" means it does not yet
1A code, spec or text change answers it, with the commit or the page named
8A consensus rule or a decision by the owner answers it, dated
26Every entry. The sections: The objective and the four properties, The five deliverables, Pools, software and participation, Architecture and proving, The three boundaries, Comparisons and leadership

The objective and the four properties

R0

"Another zkEVM"

8 October 2026
This is another zkEVM chain with a mining story attached.
Decided 8 October 2026): the positioning line is served on every page, and "zkEVM" appears only under the architecture explanation.
Pin Architecture and product, sixth box (every served page carries the positioning line and the three boundaries); Site reset, fourth box.
The answer as first written

The line is "A GPU-secured network for Ethereum-compatible applications and verifiable computation." Igneum is a sovereign GPU-mined network that runs Ethereum-compatible applications and proves their execution; the proof architecture is explained beneath that line, with its three boundaries (B1 to B3), and never leads.

R1

A specialised miner will remove most of the cost

8 October 2026
GPU-friendly hashes always fall to chips. A specialist strips everything a GPU carries that the hash does not need.
Open 8 October 2026): pass when the best supported cost and energy advantage of a re-optimised, programmable adversary sits inside the chosen competitiveness envelope, with its uncertainty published (D3).
Pin The objective, property 1; D3 pass condition.
The answer as first written

The target is contestable mining, not chip destruction: a manufacturer with a profitable product is not the failure; an exclusive, durable advantage large enough to displace the accessible GPU fleet is. Two measured results already bound the design. The connected-state reorganisation was killed as a class because rearranging the same operations moves neither side (D2). The mixed FP32 branch was killed because deterministic FP32 costs the cards 15 to 26 percent energy per hash against a 10 percent budget and widens the chip's edge to 3.0x to 3.2x (measured cards, modelled chip). Both stay as regression controls.

R2

Ordinary operators will be priced out

8 October 2026
Competitive hardware ends up in a few warehouses. A home miner with a used card has no chance.
Open 8 October 2026): pass when the reference GPU population is published with both tests per class (existing owner and new entrant) and the cost per accepted unit of work is served for each class.
Pin The objective, property 2; D1, sixth to eighth boxes.
The answer as first written

The cohort is the discrete-GPU population, used cards included. Each class gets two tests: the existing owner (power, wear, fees, alternative use) and the new entrant (purchase, operating cost, resale). The central measure is cost per accepted unit of work: annualised hardware, power, hosting, failures and fees over annual accepted work. Nothing here is measured yet as a population.

R3

Mining and proving will not pay once issuance falls

8 October 2026
The subsidy carries everyone at launch. When issuance falls the miners and provers leave.
Open 8 October 2026): pass when the five-year coexistence model names credible conditions for sustained commodity participation and names where it fails; a result needing a small network, token appreciation or scheduled chip death has not passed.
Pin The objective, property 3; D4 pass condition.
The answer as first written

The model replaces the capex wall. It covers growing and shrinking networks, reduced issuance, cheap and dear electricity, replacement and resale on both sides, changing proving demand and miners who react. Its mandatory stress case assumes the opponent's development is already paid for.

R4

The defence is a rescue fork waiting to happen

8 October 2026
When a chip arrives you will change the algorithm in an emergency, like everyone else.
Decided 8 October 2026): no property assumes a future emergency algorithm change; rotation is optional to the security argument, and seed delay is evaluated only as seed-selection protection.
Pin The objective, property 4; D5 pass condition.
The answer as first written

The four properties must hold with no rescue upgrade assumed. The no-rescue network exercise (D5) is the test: epoch boundaries crossed, signing interrupted, the network partitioned, major operators removed, hostile proof submissions, independently written clients, with specified behaviour and no emergency algorithm change or privileged intervention. That exercise is Open.

The five deliverables

D1

The numbers cannot be reproduced

8 October 2026
Your measurements come from your own machines and your own scripts. Nobody can check them.
Open 8 October 2026): pass when an independent operator reproduces the baseline within declared tolerances from the served kit alone.
Pin D1 pass condition.
The answer as first written

One exact generator, verifier, dataset policy, compiler configuration and measurement harness, pinned by digest and served. Mining and proving are measured together on the final configuration, with wall power beside device telemetry, accepted and rejected work, compile time, memory use and sustained thermals. Nobody outside the project has reproduced anything yet.

D2

Reorganising the work will not stop a specialist

8 October 2026
A specialist separates storage, arithmetic and memory scheduling. Rearranging the same work does not change what an operation costs.
Conceded 8 October 2026): the connected-state variant, D2(a), is a KILL as a class; the memory-sharing attack, D2(b), is Open.
Pin D2, first box (a) and second box (b).
The answer as first written

The critic is right for D2(a). With the same operations reorganised so that live state feeds every load address, the 64-register window is necessary (63 of 64 registers live at every address, measured), but a chip answers with a clock-gated register file that pays per write, so only the window's width reaches it: +1.2 pJ per lane-op at N5 (synthesised), moving the chip's edge 1.10x node for node against a 1.25x gate (modelled). The generator variant and the liveness tool stay behind a flag. D2(b) prices memory sharing, recomputation and data-local execution against class v6; pass when a candidate improves against re-optimised adversaries across the declared population within the preset cost and verification limits, otherwise class v6 stands and the experiment is published as a failure.

D3

Chips do not expire on schedule

8 October 2026
Your economics assume every chip dies at the next family epoch. A programmable chip survives every family you publish.
Conceded 8 October 2026): "every chip dies within a family epoch" is out of the baseline economic model, and chip-arrival percentages are not published.
Pin D3, first to fourth boxes and the pass condition.
The answer as first written

The adversary is allowed to survive: whole-system cost minimised across every published family, free to change lane count, register implementation, instruction storage, memory technology, scheduling and support hardware, placed rather than synthesised, with a three-year stress life. Next-generation opponents are in the matrix. Pass when its best supported cost and energy advantage sits inside the chosen competitiveness envelope with uncertainty published; 1.5x energy is a research goal, not the pass criterion. That is Open.

D4

The capex wall is a fiction

8 October 2026
Your wall assumes the attacker pays for development. Somebody already has.
Open 8 October 2026): pass when the five-year coexistence model, whose mandatory stress case has development already paid for, names credible conditions for commodity participation and where they fail.
Pin D4, first, fifth to seventh boxes and the pass condition.
The answer as first written

The capex wall is replaced. Tariff advantage is shown apart from hardware advantage, and the economics page resolves the tip-share discrepancy with an explicit user-funded proving payment and congestion pricing, burn treated separately, the hard cap and no development tax kept. A profit-maximising operator simulation (mine, prove internally, prove externally, switch off) must show pricing and capacity rules restoring service without an administrator.

D5

Proofs are not a protocol guarantee yet

8 October 2026
Proof verification sits off the consensus path. A modified producer can include a matching statement without the valid proof and collect a payout it did not earn.
Fixed 8 October 2026, 17:0x UK): the Igneum 2.0 devnet's node enforces proof verification in consensus from block zero (verifier_in_consensus set, node 2.0.0 4cdcc488 on release-2.0.0-node, the node's own start line); the no-rescue exercise itself stays Open and is the pass condition. Was: Conceded, the rule off on the earlier devnet.
Pin D5, first box (the prerequisite).
The answer as first written

Every producer verifies proofs off the consensus path today, so the network demonstrates proving activity rather than enforcing a permissionless proving economy. The rule and its activation switch exist in the node fork and are off on the devnet. Enforcement in consensus is the prerequisite of the no-rescue exercise, and node 2.0.0 follows it.

Pools, software and participation

P1

A pool controls its miners' votes

8 October 2026
Whoever runs the pool votes with everyone's work. Finality by pool operator.
Open 8 October 2026): pass when the member's retained voting key is committed into its work at protocol level, payment aggregation is separate and verifiable, and pool identity substitution is resisted.
Pin Pools, first box.
The answer as first written

Vote keys stay with the miner at protocol level; the pool aggregates payment, not votes. Not built yet.

P2

Pools take custody and home miners lose to latency

8 October 2026
Pools hold the coins, minimum payouts strand small miners, and a home connection loses accepted work to a datacentre.
Open 8 October 2026): pass on non-custodial payouts with practical minimums, local work verification and low-bandwidth participation, and on a published measurement of the accepted-work penalty for home internet against datacentre connections.
Pin Pools, second and third boxes.
The answer as first written

P2Pool is the precedent, not the code. Neither the payout design nor the latency measurement exists yet.

P3

Firo's miner is the bar

8 October 2026
Firo's reference miner supports NVIDIA and AMD, charges no developer fee, and reports performance within about 1 percent of closed miners. Ember has to meet that.
Open 8 October 2026): pass when Ember reaches good operating points without third-party software and its optimisation work, compiler settings and safe tuning logic are published beside a comparison.
Pin Pools, fourth box; Leadership tests, first box (Firo).
The answer as first written

Agreed that this is the bar. The within-1-percent figure is Firo's own report (claimed, not measured here). Ember is measured against it, not against whitepapers.

Architecture and proving

A1

Why not an Ethereum L2

8 October 2026
If you run EVM contracts and ZK proofs, settle on Ethereum like everyone else.
Decided 8 October 2026): three separate decisions: EVM-compatible execution for developers (revm), SP1 as the one well-tested proving backend behind a versioned interface, and sovereign GPU-mined consensus. Not an Ethereum L2.
Pin Architecture and product, first box.
The answer as first written

An L2 would suit a project whose objective is Ethereum settlement. Igneum's objective is an independent network secured by accessible hardware. Sovereignty has a cost: the network must establish its own consensus security, data availability and credible cross-chain verification, and execution proofs do not remove those duties.

A2

Proof-system flexibility becomes arbitrary acceptance

8 October 2026
A replaceable proof system means the chain accepts whatever prover is fashionable.
Decided 8 October 2026): program identities, verifier versions and security parameters are pinned in the protocol; one backend first, a second only where justified, never interchangeable immature backends.
Pin Architecture and product, second box.
The answer as first written

The interface stays replaceable; what the chain accepts does not. Pinning in the protocol is designed and not yet shown on the devnet.

A3

Rotation is not the defence

8 October 2026
Your resistance is the rotation: when a chip shows up you will identify it and fork it out.
Decided 8 October 2026): no chip detection in consensus, no hardware whitelists, attestation, per-address quotas or self-reported GPU bonuses; rotation is optional to the security argument.
Pin Standing rules (no detection, rotation optional); D3 (the adversary that survives rotation).
The answer as first written

Igneum's mining design accepts that specialised hardware may be built; its security does not rely on identifying that hardware or retiring it through emergency changes. Class v6 adopts the 64-register window and retains it across every rotation. The window costs a GPU under 1 percent of rate at stock (measured on rented RTX 5090 and RTX 4090 cards, 8 October 2026). The long-program and select-tree proposals stay out as regression controls.

A4

A concentrated prover can stall the chain

8 October 2026
Separate roles on paper. In practice one big prover withholds proofs and useful operation stops.
Open 8 October 2026): pass when a withholding concentrated prover is exercised on the no-rescue network with replacement operators, usable inputs, reassignment and explicit behaviour during proof delays, and the network behaves as specified with no privileged intervention.
Pin D5, fourth box.
The answer as first written

Winning the mining lottery and producing proofs stay separate, and they must remain separable during a failure, not only on paper.

A5

Your miner promise covers hardware your prover does not

8 October 2026
The miner runs on AMD and Apple, but the proving income needs NVIDIA.
Conceded 8 October 2026): proving runs on NVIDIA; AMD and Apple mine. The product language states it plainly.
Pin Architecture and product, fourth box.
The answer as first written

The proving stack is judged on the full pipeline: inputs, proving, aggregation, verification, payment, memory footprint and mining income forgone. A fast shard result is not enough when aggregation or memory pressure makes ordinary operators uncompetitive.

A6

"Everything runs unchanged" is a claim, not a test

8 October 2026
EVM-compatible until the block context, the randomness or the fees differ.
Open 8 October 2026): pass when compatibility ships as a product deliverable: representative contracts, wallet fee estimation, indexing, failed transactions, receipts and application assumptions tested, with the documented set of differences (block context, randomness, two-dimensional fees).
Pin Architecture and product, third box.
The answer as first written

The differences are known and are listed; the test suite that makes compatibility a deliverable does not exist yet.

A7

The proving market is revenue you do not have

8 October 2026
Internal payouts on a valueless devnet show a mechanism, not demand.
Conceded 8 October 2026): the external proving market is not built and stays out of revenue assumptions until it is.
Pin Architecture and product, fifth box; Leadership tests, third box.
The answer as first written

The ladder: prove Igneum's own execution; then one external customer's exact workload with repeat paid jobs; then further workloads only where the fleet has a demonstrated edge. Pilots and announcements do not count; customers repeatedly paying for proofs at prices that carry reliable service and an operator margin do.

The three boundaries

B1

Proven execution means the block is final

8 October 2026
The block is proven, so it is final.
Decided 8 October 2026): the boundary is stated wherever the proof architecture is explained.
Pin The objective, the three boundaries; Architecture and product, sixth box.
The answer as first written

Proven execution is not finality. A proof shows a block's execution was computed correctly; finality is a property of the chain's own consensus and checkpoints.

B2

EVM-compatible means Ethereum's security

8 October 2026
It runs Ethereum contracts, so it inherits Ethereum's security.
Decided 8 October 2026): the boundary is stated wherever the proof architecture is explained.
Pin The objective, the three boundaries; Architecture and product, sixth box.
The answer as first written

EVM compatibility is not Ethereum security. Igneum is a sovereign network: its security is its own GPU-mined consensus, not Ethereum's validators.

B3

ZK means private

8 October 2026
Zero knowledge, so my transactions are private.
Decided 8 October 2026): the boundary is stated wherever the proof architecture is explained.
Pin The objective, the three boundaries; Architecture and product, sixth box.
The answer as first written

ZK is not privacy. The proofs here verify execution; transaction data is public, and privacy would need additional application or protocol design.

Comparisons and leadership

C1

Ravencoin already does this

8 October 2026
KAWPOW already keeps consumer GPUs competitive, allows for future chips and does not plan forks as the normal defence.
Open 8 October 2026): pass when benchmarks against Ravencoin's KAWPOW, an operating system with the same stated objective, are published and show a stronger result or a more valuable overall offering.
Pin Leadership tests, first box (Ravencoin).
The answer as first written

Restating the goal is not enough. Igneum is measured against the operating system, not its whitepaper.

C2

Ergo is an operating benchmark

8 October 2026
Ergo already runs a GPU memory-hard design with live pooling, emission and difficulty changes.
Open 8 October 2026): pass when the comparison with Ergo, on its live behaviour rather than its papers, is published.
Pin Leadership tests, first box (Ergo).
The answer as first written

Ergo is a reference point, not a whitepaper competitor; the comparison is owed.

C3

Number one is unsupported

8 October 2026
You claim to be the best GPU network before anyone outside has checked anything.
Conceded 8 October 2026): no "number one" claim before comparative results and adoption exist.
Pin Leadership tests, fifth box (served ranking language); second to fourth boxes.
The answer as first written

The ceiling of the served ranking language is serious contention for the top of the GPU-mining space on engineering and operator proposition. The tests that would earn more are miners staying through hard conditions, customers repeatedly paying for proofs, and the network running without the founding team (D5); none is met yet.

Source: the project's Igneum 2.0 criticism ledger, a file in the repository, rendered to this page at build time. A criticism that is not here, or that shows an entry is wrong, is added with credit if wanted: hello@igneum.network or an issue on the specification repository.