Runtime-567 preserved-ledger terminal retirement — 2026-09-07

This is an immutable, dated diagnostic record for a preserved owned-loopback ledger. It is not evidence for the final selected runtime or a fresh campaign. The resumed validator used the checked runtime below without reset, warp, account injection, or fixture reload.

Runtime and source provenance

The profile-owner repair derives Registry and Rent ArtifactRelease raw and staging PDAs from the decoded selected V2 Core infrastructure profile and checks the fetched raw bytes hash to the selected digest. It therefore does not select those accounts from stale plan records.

Terminal predecessor stages

All six prerequisite journals are finalized. The journal SHA-256 covers every recorded exact poststate; signatures, slots, fees, compute, and packet hashes are reproduced here for audit.

The one-shot aggregate stage made no submission. Its profile-authenticated preflight found a seated failure escrow and refused by name, directing the market to its four-packet checkpointed route. That route is the required retirement shape because its prepare packet burns the failure column.

Separated non-successes

The historical ResolutionCloseFund packet 4GqfLnXZCR6GCtRhMLjwjYhgzah1UKfmB4YUcgWBEWuaeXv89aNWL4zB6yJ4dUVZ2n3kCQrJiKeDZsurNuLGa36d was superseded only after the recorded block height 18716 exceeded its last valid block height 17223. The supersession report has SHA-256 91bc9796e0197be270064530e707e9f3891c32b72a982f9e7b5faf14c8dc136d; the immutable superseded journal has SHA-256 dfe1a35bf07ea136088fd822ea8062b75b1ade92f1a4d2763cb0118384f15878. It has no finalized poststate, so the later fresh GfqK…rtcS packet above is the sole accepted close-fund mutation.

resumed-tail-profilefix-evidence.json is a preserved empty failed first attempt to render the new evidence: SHA-256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855. Its renderer rejected an undefined jq variable before producing evidence; it was not replaced. This document cites the valid v2 output instead.

The submitted close-vault and close-replay packets were polled before their next finalized observation. They were not re-signed: each journal retained one frozen packet and later recorded its finalized status. The successful signatures below distinguish this observation delay from an expiry or timeout.

Accepted checkpointed retirement and conservation

The producer froze routing table AYUpgvHgiACNSMNkHsJ671PppsF77h8AchTminQ1Mx3D over 37 derived addresses. Its evidence is retirement-lookup-table.json, SHA-256 f10877fedd2681d9f9462c31f7d166522045702c658949a7a2b3ddac86aa542b. The four accepted checkpoint journals are:

retirement-completion.json SHA-256 is d6cbf8ef6b5a538f54577ea41d73edaa06749ffd3e1e498afa5dee6414115c97. It classifies Market 3,452,160; RentCredit 17,873,283; claims refund 13,765,041; custody replay 2,895,360; and hoard vault 2,039,280 lamports, with expected refund delta 40,025,124, terminal refund-wallet balance 60,327,450, and exact transaction fees 300,000 lamports.

The final finalized reread at slot 45466 is retirement-poststate-finalized.json SHA-256 c6754087d6fd9397ffbdf9299d04d49ac81191741f0a851ce845a839f81b7e55. It found Market, hoard vault, custody replay, RentCredit, and checkpoint all absent. Thus the market has completed the terminal checkpointed route and the hoard has no remaining account or balance.

The additive summary resumed-tail-profilefix-evidence-v2.json has SHA-256 a46f2702c33b3d1ac5a554f067d5261a8ef9819e4c52438a98ca28187edc8137.