Audited 1671 blocks (h0-1670); emission 22534878.69 XEQM matches the scheduled curve to the atomic unit with no inflation (0 violations).

HF22 activated cleanly at block 250 (v21->v22); 56 blocks across the boundary serialize and link with no orphan spike; 1 node(s) agree on the post-fork chain.

20/20 stall/recovery cycles passed on a fresh 5-host cross-platform fleet (fernando/lemon/surf Linux x86_64 + dexter macOS arm64 + macmini macOS x86_64), 20 operators / 40 service nodes on the rebased release-code binary. On each forced Pulse stall the chain stayed live via GOV_SIGNED fallback and Pulse re-formed within 2-9 blocks with 9-11 validator signatures (>= the 7-signature safety floor); worst block gap 83s — the chain never halted.

Data dir populated to h1714 on the prior build reopened by the release build with no resync from zero (came up at h1714), DB intact (hash@1709 unchanged), reached tip h1714.

Node SIGKILLed at h600 restarted on the same data dir at h601 (no resync from zero), DB intact (hash@597 unchanged), and recovered to tip h1674.

Data dir populated to h1702 on the prior build reopened by the release build with no resync from zero (came up at h1702), DB intact (hash@1697 unchanged), reached tip h1702.

29 integrator-critical RPC fields across 4 methods verified present with unchanged types; 0 removed, 0 retyped (additive changes allowed).

An existing op3 wallet (prior build) opened on the release wallet-rpc, scanned, and reported its address and balance; skipped (no unlocked funds or no dest) — open+scan verified.

4/4 flag-parsing checks passed: unknown flags and the renamed --fallback-miner-key fail loudly (no silent misbind); current flags parse.

On a genuine pre-fork snapshot (blocks 0..249, hash@249 identical to canonical), a fork-unaware node came up holding the canonical chain but could not advance past HF22 (block 250): the post-fork seed was dropped at the handshake as forked, so it adopted zero post-fork blocks and stayed at h250. A fork-aware node fed the same seed passed the fork to h1786. The canonical chain (h1785) was unaffected: no surviving minority, no split.

Voluntary stake-unlock scheduling verified on 3 operators (dry-run, no SN removed): each request scheduled the service node's deactivation exactly 6 blocks out (current_height + BLOCKS_IN(UNLOCK_DURATION), UNLOCK_DURATION=30s at 5s blocks), reported the correct locked stake and target service node, and confirmed can_unlock.

Audited 154 quorums over heights 1371-1671 (1714 validator slots, 100.0% mapped to operators); no operator address occupied more than one slot in any quorum (0 violations).

891 of 1140 GOV_SIGNED fallback blocks (h1-1671) carry the authorized fallback-signer signature (voter_index 65535); the network only accepts fallback blocks signed by an authorized key (testnet fc3f4e92…), so every fallback block on the canonical chain was authorized.

6/6 transaction-validity cases behaved correctly against the live daemon: the valid transfer was accepted; a genuine double-spend (two txs on one key image) was rejected with 'double_spend'; and in-pool replay, a truncated blob, a bit-flipped proof and a tampered version were all rejected — no invalid tx reached the mempool.

Over 9 blocks the batch accounting held to the atomic unit: every block, Δ(total accrued) + coinbase paid == BLOCK_REWARD_HF19 (20.65 XEQ); the governance address accrued exactly 12.4 XEQ/block and was paid every 5 blocks; the SN portion is 8.25 XEQ/block. Rewards accrue and pay to the right addresses on cadence — no inflation, no mispayment.

A fresh node synced from genesis to the seed tip h1669 across hard forks [11, 19, 21, 22] and matched the seed's tip block hash.

Finality is bounded and live: immutable_height trailed the tip by 8 (<= the 11-block reorg window), advanced 1672->1680 as the chain grew, and recent checkpoints were SN-signed with >= 13 votes at 4-block spacing. Finalized block hashes below immutable_height were unchanged after the chain advanced, and an isolated node force-popped below its immutable height re-synced to the identical finalized blocks — finalized history cannot be rewritten.

The v1.1.0 binary runs on all 5 target hosts across 3 platform/arch combos (linux/x86_64, macos/arm64, macos/x86_64), including a non-AVX2-class Intel Mac and Apple Silicon.

All 5 release build jobs succeeded for the release candidate (core-v1.1.0-rc4): Linux x86_64, Linux arm64, Windows x64, macOS arm64, macOS x86_64. Linux and macOS artifacts are confirmed to start on target hosts.