From 3fb3c6a07e0375639efc048176f74b186329038e Mon Sep 17 00:00:00 2001 From: thePR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com> Date: Mon, 22 Jun 2026 18:47:52 -0400 Subject: [PATCH] docs(todo): mark cold-start REQ-storm + from_hex fixes done Co-Authored-By: Claude Opus 4.8 --- todo/TODO_2026-06-20_pre-launch.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/todo/TODO_2026-06-20_pre-launch.md b/todo/TODO_2026-06-20_pre-launch.md index ce7d4949..55a3b4a1 100644 --- a/todo/TODO_2026-06-20_pre-launch.md +++ b/todo/TODO_2026-06-20_pre-launch.md @@ -131,8 +131,16 @@ tests → `npm run build` + `npm run test:unit` green → commit + push. surfacing the same control from the Storage settings pane. ### 9. Cap the cold-login relay-REQ storm further -- [ ] Investigate the ~117 REQ/s spike at login. Respect the `capReadRelays` invariant - everywhere fan-out happens; consider staggering subsystem subscriptions at login. +- [x] **Biggest source fixed** (`a8e9f520`): the community-blacklist load fired one + kind-30000 REQ *per curator* (~28-32 parallel) at cold start. Collapsed into a + single batched multi-author REQ (`js/adminListBatch.js`), routed through the + subscription manager. This was the dominant `kind 30000` storm. +- [x] **Relay `from_hex` REQ rejects fixed** (`733cb593`): one odd-length/non-hex + value in `ids/authors/#e/#p/#q` made strict relays reject a whole REQ; now + sanitized at the pool choke point (`normalizeFilterList`). +- [ ] Re-measure the login REQ/s spike after these. If still high, look at remaining + fan-out (profiles kind 0, reports kind 1984, mute lists kind 10000) and consider + staggering subsystem subscriptions at login. Respect `capReadRelays` everywhere. ## Open — lower priority / infra