Marcin Pawlowski a16284ebc5
The uncle cap rule survives the anchor change; the window floor does not
Second half of the re-measurement. Sizing U is unaffected: the smallest cap
reaching the 0.98 bar is identical under both anchors at every load tested --
U=1 at rho 0.27 and 0.47, U=2 at 0.87, and neither clears at rho=1.27, which is
past the operating point the recipe permits. U = ceil(rho)+1 carries over
verbatim. At that cap the residual cost stays inside the design regime: -0.003
at rho 0.47 and 0.87, growing to -0.009 only at 1.27.

So the anchor's cost lives in the WINDOW, not the cap, which is what the
mechanism predicts -- the parent gap lengthens the queue's deadline without
changing how fast it drains.

Net effect on the recipe: U unchanged, W floor up one to two block-intervals,
W = 10 still clearing at the deployed point and W = 12 restoring today's margin
at heavier delay. Both sweeps are committed configs and their data archived, so
the re-baselining is reproducible rather than a one-off.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-07 18:34:16 +02:00
2026-07-30 11:43:55 +02:00
2026-07-30 11:44:33 +02:00

Logos Blockchain Research

Description
Logos Blockchain Research
Readme MIT
Languages
Python 90.8%
C 3.2%
Shell 3%
Rust 1.9%
Makefile 0.9%
Other 0.2%