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

Merge master b73a33b8a into ca3-coord-record under the master-landing lock

Browse source
This commit is contained in:
igneum-labs 2026-10-09 03:26:53 +00:00
commit ea2bb20d15
4 changed files with 114 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/plans/igneum-2.0-f0-manifest.md
View file

@ -54,7 +54,7 @@ The fixture every case of the Test and Acceptance Standard (docs/plans/igneum-2.
| The acceptance rule on the candidate (6.13) | PASS under both era inputs in circulation; the edc4fa84 program (the candidate) clean at widths 4 and 1 under the full rule and the crate's own predicate; attack-f8 subset PASS | master 17dee5bc (lane D, 22:40 UK); batch family-gate-20261008c | lane D |
| The live class v5 object (context 03) | 81fbfa3aa413173f at epoch 2 (epoch seed 3c3fab43…, day 20734), the live node's own program-id line as the witness; the same-work test's live-chain half, references about 00:25 UK, CUDA after them; labelled on an island, not a network | the hand's context 03 (build-1, sha256 53837a96…) | same-work hand |
| 2.0.2 pair gate | Kit 2 (the roll): node release-2.0.2-node 5d53a591 (kit2b-line: fix 2 + the wedge fix on kit 1's tree) and the cut tip release-2.0.2 1176efb9 (the pin and the manifest's node block at 5d53a591, release-manifest-check green; no crate move since 77b5acc5): on build-4 from the key-succession parent with the class v5 freeze (fingerprint cbc5bd0a) the kaspad check with igneum-pow GREEN (rule 19), core 185/0, exec 95/0, miner 33/0, p2p-flows 40/0, consensus 143/0; the miner tip pow 113/0, app 389/0 on 77b5acc5. Batch 202-5d53a591-1176efb9. Kit 1 re-cut (490ebcfe, 5db25637; batch 202-490ebcfe-5db25637, master ff1da144) is the clean fallback. cf32be79 (the record-store fold) read red on the fresh-sync read at 00:55 UK (the store's IBD pre-fetch reads its own store as held while the body rule reads the pool) and rides 2.0.3. Earlier shas stand as records: 94e4c6ba (six cells GREEN, the mac canary FAIL, the wedge at DAA 9,821; master 9b040ab0), d657e490 (the 4,379 stall; master 76041234), a284380b (the pair RED on chain, a fix-2 lock fault; master 26203e35). | the shipper's 01:2x line; build-1:/srv/artefacts/tas/202-5d53a591-1176efb9/ | CI steward, shipper, node lane, HEAL lane |
| Rule 33 canary for 2.0.2 | Kit 2 (1176efb9, node 5d53a591): the record tools/ci/canary/1176efb9.json landed on master fa8139bd at 02:29 UK with its mac block PASS (the project's macOS machine, Apple M6: synced from empty in 2,016 s on hub-1's chain, 18 blocks in five minutes at 12.65 MH/s, 0 refusals, shard n/a on Apple silicon, the tip inside ten of the age-adjusted feed, quit in 4 s; build-1:/srv/canary/1176efb9/mini/); the Mac entry published on it at 02:20 UK through publish-manifest's guard (Igneum-Miner-2.0.2-5d53a591-1176efb9.dmg 66137cd8…, the public alias on it); Windows and HiveOS stay 2.0.1 until their own blocks read PASS; the fleet, hive and windows blocks join from their boxes. INT-07 reads NOT RUN in progress on one of four blocks. Kit 1 as 94e4c6ba (870c0344): the mac block FAIL on its sync line (the wedge at DAA 9,821) stands as that sha's record; kit 1 re-cut (5db25637) has its own PASS mac block staged as the fallback's evidence. | the shipper's 02:3x line; the coordinator's ruling | shipper, fleet lane, relay lane, HEAL lane |
| Rule 33 canary for 2.0.2 | Kit 2 (1176efb9, node 5d53a591), the record tools/ci/canary/1176efb9.json: the mac block PASS (the project's macOS machine, Apple M6: synced from empty in 2,016 s on hub-1's chain, 18 blocks in five minutes at 12.65 MH/s, 0 refusals, shard n/a on Apple silicon, the tip inside ten of the age-adjusted feed, quit in 4 s; the Mac entry published on it at 02:20 UK through publish-manifest's guard, Igneum-Miner-2.0.2-5d53a591-1176efb9.dmg 66137cd8…); the fleet block FAIL at sync (lp-4090-11, 04:04 UK: a fresh 2.0.2 node walls at the reference chain's fifth cut under fix 2's walk bound, 'passed 7200 blocks (2 x epoch_blocks) without meeting a block this executor holds a record of'; the kit ran clean); the hive block about 05:30 UK, the windows block on the relay lane's clock. No fleet, hive or windows entry publishes on this record; Windows and HiveOS stay 2.0.1. INT-07 reads FAIL on the fleet block. Kit 1 as 94e4c6ba (870c0344): the mac block FAIL on its sync line (the wedge at DAA 9,821) stands as that sha's record; kit 1 re-cut (5db25637) has its own PASS mac block as the fallback's evidence. | the shipper's 02:3x and 04:19 lines | shipper, fleet lane, relay lane, HEAL lane |
| Network label | devnet-4 has been islands since the epoch-3 cut: every measurement recorded on the 2.0 devnet after 20:00 UK reads "on an island, not a network" until the fleet is one chain (the 2.0.2 roll as the convergence test, else the operator reset onto hub-1's chain at 04:00) | main's word through the coordinator, 22:2x UK; the recorder's --label-islands | CI steward |
The block is the steward's read-back of the lanes' own landed lines; the three roles in the signatures table sign by a landing of their own.

31
docs/plans/igneum-2.0-test-registry.json
View file

@ -15444,20 +15444,20 @@
"owner": "CI steward with the hash lane (a690540514aa453d7) and the worker lane (a9e87343f008e0edd)",
"manual_page": null,
"owner_lane": "CI steward with the hash lane (a690540514aa453d7) and the worker lane (a9e87343f008e0edd)",
"run_status": "NOT RUN",
"run_status": "FAIL",
"master_status": "PROPOSED / NOT RUN",
"run_id": "canary-202-20261009-01",
"evidence_path": "tools/ci/canary/1176efb9.json; build-1:/srv/canary/1176efb9/mini/00-verdict.txt",
"updated": "2026-10-09T01:39:15.241Z",
"evidence_path": "tools/ci/canary/1176efb9.json; build-1:/srv/canary/1176efb9/mini/00-verdict.txt; build-1:/srv/canary/1176efb9/lp-4090-11/fleet-block.json",
"updated": "2026-10-09T03:25:13.107Z",
"evidence_record": {
"requirement_id": "INT-07",
"decision": "NOT RUN",
"decision": "FAIL",
"method": "team-reported",
"cell": "canary:fresh-install",
"manifest_sha": "5d53a591",
"run_id": "canary-202-20261009-01",
"evidence": "tools/ci/canary/1176efb9.json; build-1:/srv/canary/1176efb9/mini/00-verdict.txt",
"in_progress": true,
"evidence": "tools/ci/canary/1176efb9.json; build-1:/srv/canary/1176efb9/mini/00-verdict.txt; build-1:/srv/canary/1176efb9/lp-4090-11/fleet-block.json",
"in_progress": false,
"coverage": "partial: V6-12's clean-install half (one published object installed fresh, synced, mined, proved and paid on one host per artefact); the cross-host agreement half (node, pool, CPU verifier, each GPU host across activation) is harness:same-work's",
"release_identity": {
"commit": "1176efb9 (release-2.0.2 kit 2 tip; node 5d53a591)",
@ -15467,22 +15467,22 @@
"activation": "",
"profile_hashes": ""
},
"claim_impact": "INT-07's clean-install half: kit 2's rule-33 record reads PASS on its mac block (one of four); the row reads NOT RUN in progress until the fleet, hive and windows blocks join, PASS then; the Mac entry published on it at 02:20 UK through publish-manifest's guard",
"claim_impact": "INT-07's clean-install half on kit 2 reads FAIL on the fleet canary (the walk bound at the fifth cut); the mac block PASS stands as the Mac entry's evidence; no fleet, hive or windows entry publishes until a record reads PASS on its own block",
"reviewer": "",
"at": "2026-10-09T01:39:15.241Z",
"note": "one PASS block (mac) of four on kit 2's record; the row turns PASS when the fleet, hive and windows blocks read PASS | Kit 2 (tip 1176efb9, node 5d53a591): the mac block PASS under tools/ci/canary-check.sh on master (synced from empty in 2,016 s on hub-1's chain, 18 blocks in five minutes at 12.65 MH/s, 0 refusals, shard n/a on Apple silicon, tip 16731 against the feed's 16722 at 1 s, quit in 4 s); the record landed as fa8139bd at 02:29 UK; the fleet, hive and windows blocks join from their boxes when their canaries read. Kit 1's 94e4c6ba FAIL (the wedge) stands as that sha's record.",
"at": "2026-10-09T03:25:13.107Z",
"note": "mac PASS, fleet FAIL at sync (the walk bound at the reference chain's fifth cut under fix 2), hive and windows pending | Kit 2 (tip 1176efb9, node 5d53a591): the mac block PASS under tools/ci/canary-check.sh (the project's macOS machine: synced from empty in 2,016 s, 18 blocks in five minutes at 12.65 MH/s, 0 refusals, shard n/a on Apple silicon, the tip inside ten of the age-adjusted feed, quit in 4 s); the fleet block FAIL at sync (lp-4090-11, 04:04 UK: a fresh 2.0.2 node walls at the reference chain's fifth cut under fix 2's walk bound, 'passed 7200 blocks (2 x epoch_blocks) without meeting a block this executor holds a record of'; the kit ran clean; build-1:/srv/canary/1176efb9/lp-4090-11/fleet-block.json); the hive block reads about 05:30 UK, the windows block on the relay lane's clock. No fleet, hive or windows entry publishes on this record; the Mac entry published on its PASS block at 02:20 UK. Kit 1's 94e4c6ba FAIL (the wedge) stands as that sha's record. The recorder's rule: a measured FAIL on one block is a FAIL on the case.",
"network_label": "on an island, not a network"
},
"evidence_records": {
"canary:fresh-install": {
"requirement_id": "INT-07",
"decision": "NOT RUN",
"decision": "FAIL",
"method": "team-reported",
"cell": "canary:fresh-install",
"manifest_sha": "5d53a591",
"run_id": "canary-202-20261009-01",
"evidence": "tools/ci/canary/1176efb9.json; build-1:/srv/canary/1176efb9/mini/00-verdict.txt",
"in_progress": true,
"evidence": "tools/ci/canary/1176efb9.json; build-1:/srv/canary/1176efb9/mini/00-verdict.txt; build-1:/srv/canary/1176efb9/lp-4090-11/fleet-block.json",
"in_progress": false,
"coverage": "partial: V6-12's clean-install half (one published object installed fresh, synced, mined, proved and paid on one host per artefact); the cross-host agreement half (node, pool, CPU verifier, each GPU host across activation) is harness:same-work's",
"release_identity": {
"commit": "1176efb9 (release-2.0.2 kit 2 tip; node 5d53a591)",
@ -15492,14 +15492,13 @@
"activation": "",
"profile_hashes": ""
},
"claim_impact": "INT-07's clean-install half: kit 2's rule-33 record reads PASS on its mac block (one of four); the row reads NOT RUN in progress until the fleet, hive and windows blocks join, PASS then; the Mac entry published on it at 02:20 UK through publish-manifest's guard",
"claim_impact": "INT-07's clean-install half on kit 2 reads FAIL on the fleet canary (the walk bound at the fifth cut); the mac block PASS stands as the Mac entry's evidence; no fleet, hive or windows entry publishes until a record reads PASS on its own block",
"reviewer": "",
"at": "2026-10-09T01:39:15.241Z",
"note": "one PASS block (mac) of four on kit 2's record; the row turns PASS when the fleet, hive and windows blocks read PASS | Kit 2 (tip 1176efb9, node 5d53a591): the mac block PASS under tools/ci/canary-check.sh on master (synced from empty in 2,016 s on hub-1's chain, 18 blocks in five minutes at 12.65 MH/s, 0 refusals, shard n/a on Apple silicon, tip 16731 against the feed's 16722 at 1 s, quit in 4 s); the record landed as fa8139bd at 02:29 UK; the fleet, hive and windows blocks join from their boxes when their canaries read. Kit 1's 94e4c6ba FAIL (the wedge) stands as that sha's record.",
"at": "2026-10-09T03:25:13.107Z",
"note": "mac PASS, fleet FAIL at sync (the walk bound at the reference chain's fifth cut under fix 2), hive and windows pending | Kit 2 (tip 1176efb9, node 5d53a591): the mac block PASS under tools/ci/canary-check.sh (the project's macOS machine: synced from empty in 2,016 s, 18 blocks in five minutes at 12.65 MH/s, 0 refusals, shard n/a on Apple silicon, the tip inside ten of the age-adjusted feed, quit in 4 s); the fleet block FAIL at sync (lp-4090-11, 04:04 UK: a fresh 2.0.2 node walls at the reference chain's fifth cut under fix 2's walk bound, 'passed 7200 blocks (2 x epoch_blocks) without meeting a block this executor holds a record of'; the kit ran clean; build-1:/srv/canary/1176efb9/lp-4090-11/fleet-block.json); the hive block reads about 05:30 UK, the windows block on the relay lane's clock. No fleet, hive or windows entry publishes on this record; the Mac entry published on its PASS block at 02:20 UK. Kit 1's 94e4c6ba FAIL (the wedge) stands as that sha's record. The recorder's rule: a measured FAIL on one block is a FAIL on the case.",
"network_label": "on an island, not a network"
}
},
"in_progress_since": "2026-10-09T01:39:15.241Z",
"approvals": {
"scope_approved": null,
"implementation_complete": null,

12
tools/ci/batches/canary-202-20261009-01.json
View file

@ -14,19 +14,19 @@
"activation": "",
"profile_hashes": ""
},
"claim_impact": "INT-07's clean-install half: kit 2's rule-33 record reads PASS on its mac block (one of four); the row reads NOT RUN in progress until the fleet, hive and windows blocks join, PASS then; the Mac entry published on it at 02:20 UK through publish-manifest's guard",
"note": "Kit 2 (tip 1176efb9, node 5d53a591): the mac block PASS under tools/ci/canary-check.sh on master (synced from empty in 2,016 s on hub-1's chain, 18 blocks in five minutes at 12.65 MH/s, 0 refusals, shard n/a on Apple silicon, tip 16731 against the feed's 16722 at 1 s, quit in 4 s); the record landed as fa8139bd at 02:29 UK; the fleet, hive and windows blocks join from their boxes when their canaries read. Kit 1's 94e4c6ba FAIL (the wedge) stands as that sha's record.",
"claim_impact": "INT-07's clean-install half on kit 2 reads FAIL on the fleet canary (the walk bound at the fifth cut); the mac block PASS stands as the Mac entry's evidence; no fleet, hive or windows entry publishes until a record reads PASS on its own block",
"note": "Kit 2 (tip 1176efb9, node 5d53a591): the mac block PASS under tools/ci/canary-check.sh (the project's macOS machine: synced from empty in 2,016 s, 18 blocks in five minutes at 12.65 MH/s, 0 refusals, shard n/a on Apple silicon, the tip inside ten of the age-adjusted feed, quit in 4 s); the fleet block FAIL at sync (lp-4090-11, 04:04 UK: a fresh 2.0.2 node walls at the reference chain's fifth cut under fix 2's walk bound, 'passed 7200 blocks (2 x epoch_blocks) without meeting a block this executor holds a record of'; the kit ran clean; build-1:/srv/canary/1176efb9/lp-4090-11/fleet-block.json); the hive block reads about 05:30 UK, the windows block on the relay lane's clock. No fleet, hive or windows entry publishes on this record; the Mac entry published on its PASS block at 02:20 UK. Kit 1's 94e4c6ba FAIL (the wedge) stands as that sha's record. The recorder's rule: a measured FAIL on one block is a FAIL on the case.",
"cells": [
{
"cell": "canary:fresh-install",
"cases": [
"INT-07"
],
"status": "NOT RUN",
"in_progress": true,
"evidence": "tools/ci/canary/1176efb9.json; build-1:/srv/canary/1176efb9/mini/00-verdict.txt",
"status": "FAIL",
"method": "team-reported",
"evidence": "tools/ci/canary/1176efb9.json; build-1:/srv/canary/1176efb9/mini/00-verdict.txt; build-1:/srv/canary/1176efb9/lp-4090-11/fleet-block.json",
"network_label": "on an island, not a network",
"note": "one PASS block (mac) of four on kit 2's record; the row turns PASS when the fleet, hive and windows blocks read PASS"
"note": "mac PASS, fleet FAIL at sync (the walk bound at the reference chain's fifth cut under fix 2), hive and windows pending"
}
]
}

93
tools/ci/canary/1176efb9.json
View file

@ -85,9 +85,100 @@
"verdict": "PASS",
"recorded_at": "2026-10-09T00:11:54Z",
"recorded_by": "shipper"
},
{
"artefact": {
"url": "build-1:/srv/workers/fleet/kit-5d53a591.tgz",
"sha256": "8fb8c8f52c27670fef988ff15ffd11c47b9024d62e0dab0bb4e0412974ed1012",
"kind": "fleet",
"note": "the tarball installed at 03:29 UK (8fb8c8f5\u2026) was re-tarred by the cutter at 03:32 UK to de47da86da056d6c1b96483cf214de96ea23d7e762e7b3f7b1edb48788ba13c5 with byte-identical binaries (igneumd fbf1d6e53021febd, igneum-miner 66fded0f5ce15bde, fingerprint cbc5bd0aa10585c8): the gzip stamp only; the binaries are the identity"
},
"box": {
"host": "lp-4090-11 (RTX 4090, Ubuntu 24.04, EPYC)",
"isa_line": "cpu flags: no avx512 (avx512f_count=0)"
},
"datadir": {
"path": "~/fleet/dn4 (igneum-devnet-4)",
"empty_at_start": true,
"read_back": "build-1:/srv/canary/1176efb9/lp-4090-11/01-datadir.txt"
},
"sync": {
"genesis_height": 0,
"tip_height": 16492,
"seconds": 0,
"feed": {
"height": 0,
"age_s": 0,
"blocks_per_min": 0.0
},
"read_back": "build-1:/srv/canary/1176efb9/lp-4090-11/02-sync.txt"
},
"mining": {
"minutes": 5,
"refusals": 0,
"accepted_blocks": 0,
"read_back": "build-1:/srv/canary/1176efb9/lp-4090-11/03-mining.txt"
},
"shard": {
"claimed": false,
"proved": false,
"paid_or_queued": "none",
"read_back": "build-1:/srv/canary/1176efb9/lp-4090-11/04-shard.txt"
},
"quit": {
"bounded": false,
"seconds": 999,
"read_back": "build-1:/srv/canary/1176efb9/lp-4090-11/05-quit.txt"
},
"lines_read_back": [
{
"line": "install",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/00-install.txt"
},
{
"line": "box",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/00-box.txt"
},
{
"line": "datadir",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/01-datadir.txt"
},
{
"line": "sync",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/02-sync.txt"
},
{
"line": "mining",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/03-mining.txt"
},
{
"line": "shard",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/04-shard.txt"
},
{
"line": "quit",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/05-quit.txt"
},
{
"line": "version",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/00-version.txt"
},
{
"line": "tip",
"evidence": "build-1:/srv/canary/1176efb9/lp-4090-11/09-tip.txt"
}
],
"tip": {
"within_ten_of_hub1": false,
"line": "",
"read_back": "build-1:/srv/canary/1176efb9/lp-4090-11/09-tip.txt"
},
"verdict": "FAIL",
"kind": "fleet"
}
],
"verdict": "PASS",
"recorded_at": "2026-10-09T01:15:45Z",
"recorded_by": "shipper (the mini's rule-33 canary)"
"recorded_by": "shipper (the mini's rule-33 canary)",
"note": "the fleet block reads FAIL at sync (lp-4090-11, 04:04 UK, 9 October 2026): a fresh 2.0.2 node walls at the reference chain's fifth cut under fix 2's walk bound; the kit ran clean; no fleet, hive or windows entry publishes on this record; the mac block stands for the Mac entry published 02:20 UK"
}