igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

Ledger close: the bounty correction recorded as applied on ca2-coord (6141e01, 8c5b02f)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 15:46:23 +00:00
parent 2b615f169f
commit c6b0bad13b
2 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/plans/ledger-close-status.md
View file

@ -58,3 +58,7 @@ Round 3 merged (ledger-pc2 564acab: M16 answered on PC 2's 5090, inline at 64 Mi
the project lead's decisions of 17:25 UTC on items 1 to 13 are written into the ledger as dated Decided lines and into `docs/plans/ledger-decisions.md` (outcomes section); item 1 corrected at 17:35 UTC: no device bounty, the claim is backed by paid cryptanalysis and the benchmark, an optional USD 50,000 cryptanalysis prize escrowed before it is named. Every public bounty mention is struck (litepaper four sentences, evidence page row 17, spec 06 O-1.17, the funding plan). The Counter ASIC document's issuance trigger lives on `ca2-coord` and was sent to its owner to re-point at the audit and benchmark.
Counts (167 entries): Fixed, rolled out, rule written or designed 54 (53 plus X17). Conceded and stated or terminal 52. Decided or closed by rule 27. Answered by design or with evidence 25. Open with counsel engaged 4 (L1 L2 L4 L5). Open, blocked on a later phase with the blocker and date named 3 (P3 X15 P22). Conceded, scheduled 1 (D5). C4 another agent's. No entry is open without a named owner, blocker or date.
## 17:55 UTC, 6 October 2026: the bounty correction is complete on both branches
`ca2-coord` 6141e01 and 8c5b02f (the Counter ASIC coordinator): every bounty sentence struck on that branch's litepaper, counter-asic-2-public.md, counter-asic-3.md (the issuance trigger now brings forward the paid cryptanalysis and the benchmark's next round), evidence row 17 and the bench-log paragraph. `fud-close` 72d1ec2 carries the same on its copies. The live site keeps 0.3.11's merged sentences until a cut takes either branch.

2
docs/plans/ledger-decisions.md
View file

@ -60,7 +60,7 @@ Question: adopt, at gate 3, the three values the ledger-tails round wrote into `
| Item | Decision | Ledger lines written |
|---|---|---|
| 1 (M1, M22) | CORRECTED at 17:35 UTC: NO device bounty (the 17:25 tiers of USD 250,000 and USD 100,000 are withdrawn: a team with a real 2x chip earns more mining than any bounty, so those tiers attract nobody). The claim "under 2x" is backed by the paid independent cryptanalysis (the Monero route: four paid reviews, no bounty) and the public benchmark with M22's metrics. Optional, the project lead's call later: a single cryptanalysis prize of USD 50,000 for a published 2x+ shortcut in the mixer, the chained cache or the acceptance rule, escrowed before it is named. Every public mention of a bounty is struck from the litepaper, the evidence page, spec 06 O-1.17 and the funding plan (this commit); the Counter ASIC 2.0 document's USD 20,000-a-day issuance trigger lives on the `ca2-coord` branch and must point at the audit and the benchmark, not a bounty (sent to that branch's owner) | M1, M22
| 1 (M1, M22) | CORRECTED at 17:35 UTC: NO device bounty (the 17:25 tiers of USD 250,000 and USD 100,000 are withdrawn: a team with a real 2x chip earns more mining than any bounty, so those tiers attract nobody). The claim "under 2x" is backed by the paid independent cryptanalysis (the Monero route: four paid reviews, no bounty) and the public benchmark with M22's metrics. Optional, the project lead's call later: a single cryptanalysis prize of USD 50,000 for a published 2x+ shortcut in the mixer, the chained cache or the acceptance rule, escrowed before it is named. Every public mention of a bounty is struck from the litepaper, the evidence page, spec 06 O-1.17 and the funding plan (this commit); the Counter ASIC 2.0 document's USD 20,000-a-day issuance trigger on the `ca2-coord` branch now points at the paid cryptanalysis and the benchmark's next round (applied there in commits 6141e01 and 8c5b02f, 6 October 2026, with every other bounty sentence on that branch struck) | M1, M22
| 2 (F16) | YES, option B | F16 |
| 3 (X5, X14) | YES as written, with the silent-fleet addition | X5, X14 |
| 4 (E14) | YES: internal table, one public unfunded-lines sentence | E14 |