Founding-packet freshness runtime record — 2026-09-07

This dated record preserves one failed packet and one fresh, terminal local campaign. It does not identify a deterministic source-code latency defect: the preserved failure has only its final Dispatching row and no phase timing markers. The new markers bound the successful path. Consequently the measured conclusion is transient host/runtime contention or scheduling in the failed run, not a proven attribution to fee RPC, account rereads, hash generation, or filesystem sync.

No journal transition, validity rule, or recovery permission was weakened. In particular, no expired packet was re-signed. The fresh campaign created a new signed packet against a new genesis and finalized it before its recorded last-valid block height.

Exact sources, runtime, and command

The checked ELF SHA-256 values used by the chain were Core a08769a886cf03a061376dc5741c4141c545554830a3c9b79423477b94115c97, Resolution 87661a9764839945cce082feccb5095c8b7c6412fc7f65cd0114be222d84698a, and Claims 7656cade51da56014f0be94988330a50ba9ec75cdf8b1fb176c5d5881c48afe3.

This is a live checked-program local-validator result driven by the named working-tree clone. It is not a release cut from either source revision.

Failure boundary and fresh-packet measurement

The original preserved runtime-567 evidence is /tank/dregg-build/dclutch-capture-transition-40d880df4-run/runs/20260908T002200Z-capture/capture/campaign/founding-evidence.json, SHA-256 08b50da0a4c7edfff7bd5ea962eb69d0fffaed7654b9c7402255822d8c20c1b0. Its core-funding-accept-v1 row remained Dispatching, carried last-valid block height 8049, and had no signature. The contemporaneous height was 8112: the unsigned-to-send interval crossed 63 heights after expiry (and 213 heights after the prior relevant snapshot). The older driver had no named phase observations, so this record deliberately does not assign that interval to any individual RPC or fsync.

The driver now emits named observations before each freshness gate, including the failed boundary, and preserves the same exact message fee quote. In the fresh run, the accepted core-funding-accept-v1 packet measured:

Thus the measured driver path crossed one height and sent within 128 ms. It refutes a persistent 16-tick driver-side 200-height path; it does not prove which external activity caused the old run's stall. The retained instrumentation is the diagnostic/fix for a recurrence: it records the named blocking boundary before refusing, while the immutable journal remains the only authority for a future exact-signature recovery.

Accepted funding and poststates

core-funding-accept-v1 finalized at slot 7891 with last-valid block height 7961, fee 75,000 lamports, and 213,429 compute units. Its exact signature is 85u1kAuSc2Y75ZrSLrXuHviP171VoE8pboqq6vXXdTVuPUaRkxdtqDMYJ4gGzzRaBJr3Lj37iD3db8RViG9RP1G. The journal's finalized-poststates digest is f997a19e52e588e9a35bebf4a906e384abe9abd523bc328bf90a3dd1ce728e34.

The journal's accepted Core, Resolution, and Claims poststates are the following exact account evidence entries:

The complete founding evidence has SHA-256 038cee2cb156e9ebe0c9ab8d980df8f2cd6a1f5501a726ef0d4da86989d5aaf1.

Pyth capture and terminal poststate

The transcript SHA-256 is aa903f2db9b14614df1961b8806b9aee013037cf87d48f7bb4d6784daeb6d808. It records a Pyth publication at cluster unix time 1788831234, then a real Wormhole verification and Pyth receiver update. Resolution submitted the funded rung and produced certificate D69ojguLFwYcPfxKa3zfuzWSojDvxYk1sFNzqKtmzm9T; the capture readback is Resolved, route Recovery, attempt index 1, selector 0, terminal sequence

1. Core then admitted that certificate: the transcript's final stage records

Market phase Terminal, terminal sequence 1, and winner 0. The transcript finished at cluster unix time 1788832538.

The frame captures retained with this result are campaign/captures/provider-submit.capture.json SHA-256 0faad3ff91f9485501cf0e60478a3b0e53f5aa620af6a1a7c7d834090786f5cb and campaign/captures/provider-execute.capture.json SHA-256 4d9a68f78547b39cd7d3361b24a02adc659e647da4e9d9b394d291124d8733ee.

Separated 64-tick control

Commit 3f51d00f0c79ac9644f3dec254549d01ae5417ac also makes the explicit DCLUTCH_TICKS_PER_SLOT profile reach both validator spawn sites. A bounded 64-tick control verified the argv and was stopped before any founding packet was planned. Its retained scheduling-wall record is /tank/dregg-build/dclutch-founding-packet-3f51d00f0-run64/64tick-scheduling-wall.json, SHA-256 20913112d52992be6cd4cc7b21c0060e39d6d9b2f2a03e0da59cfef39750eddb.

That control published its immutable source window at 2026-09-08T01:23:45Z with a 1200-second primary deadline, while 5900 slots remained before Found. At 64 ticks per slot the conservative completion time was about 2360 seconds. It could not accept Capture under that authored window, so it is evidence of a campaign-scheduling wall only; it makes no accepted-capture claim and does not justify changing the source-window policy.