henyey mainnet daily — 2026-04-30 #2141
tomerweller
announced in
Announcements
Replies: 1 comment
Go ahead. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Validator
96998244(uptime 17m on this binary; ~15 deploys in last 24h, ~96m avg between deploys under the new 60m cool-down)Deploys (~15)
Major themes today — heavy security-audit follow-ups (AUDIT-200..217, ~12 fixes), correctness refactors (FeeMode/FeeStrategy enums, InvariantManager subsystem, PreparedTransactionSet newtype, hostname/peer-address validation), parity hardening (XDR-byte sort, sealed-box without crypto_box, low-order Curve25519 reject), and 2 monitor-side skill commits.
bb1d8bb62ee49eb6604f58945221918506010c8c3d903a97002c4e7f260f84d7724abcd2d0ea81cae08cd6e2e7d57f4d969982442abfffec3a0b9834Plus ~30 commits landed but rolled into bundles by the cool-down (only HEAD-of-bundle deploys actually happen).
Incidents (1)
~/data/74535976/wiped externally between 11:27Z and 11:47Z UTC~/data/74535976/(logs, binary, last_ledger, cargo-target) all deleted;~/data/mainnet/mainnet.dbreduced from ~25 GB to a 1.7 GB partial — clearly external action, not validator self-shutdowne7d57f4d(5m 55s), wiped the 1.7 GB partial state, fresh-sync from network archive (catchup completed in ~12 min — much faster than the 4 h fresh-start budget thanks to recent network position)Issues activity
Filed today (~58 — heavy audit batch + plan-do-review follow-ups):
Closed today (~50): #2098 + #2110 (urgent), #2083..#2106 audit batch (most), and ~30 follow-ups #2087..#2140
Still open (sample, ~10): #2106 [audit-info] AUDIT-217 watcher-mode catchup, #2134 (FeeRate newtype), #2135 (closing-gate replay variant test), #2136 (peer_port != 0 validation), #2137 (RPC port collision), #2138 (top-level VALIDATORS/HISTORY parsing), #2139 (RPC getEvents filter), #2140 (overlay PeerAddress conversion). Plus #2041 [not-ready] Quickstart
build/complete exit 1flake (CI hygiene).Watch items
pdr-2126, etc.) appear to be eating into root. The/home/tomer/datapartition has plenty of room (5%). Worth running a cleanup ofpdr-*/debug/build caches.validator_status: 🔴 OFFLINE (~40 min) → 🟢 Validating after fresh-sync recovery. Resolved.cool-down floor: raised from 30m to 60m on 2026-04-30. First full day under new rule produced ~15 deploys vs ~23-25 yesterday under 30m — closer to the desired settling cadence.Tick aggregates (last 24h)
75315f0c(every 20m, schedule3,23,43 * * * *). Pre-wipe ticks lost (tick-history.jsonl was inside the wiped session dir).b8d88be0"monitor-tick: auto-wipe corrupt persisted state after repeated FATAL" (yesterday's evening, included)3a0b9834"monitor-tick: raise deploy cool-down from 30m to 60m"2abfffec"monitor-{tick,loop}: align cadence wording with 20m cron"Open questions for the operator
/home/tomer/data/pdr-*/debug/look like they're driving the pressure. Want me to clean stalepdr-*/debug/directories that no longer have a running cargo process? It's destructive (~tens of GB recoverable) but harmless to those agents — they'll rebuild on next run.~/data/74535976/was deleted externally today; recovery worked (40-min downtime), but it'd be cheap to add a periodic snapshot oflast_ledger+ the lightweight metric files outside the session dir so post-wipe restoration doesn't lose progress tracking. Worth doing?Auto-posted by
/daily-summary(session 74535976). Today's 13:00 UTC cron likely fired during the build window and missed the REPL-idle slot — this is a manual fire from the operator's/daily-summaryinvocation.All reactions