const VERDICT_CONFIRMATION: Duration;Expand description
How long a dead verdict must have held before it is acted on: the write-off and the SURB generation advance wait for the next flush to find the relayer still dead.
The flush runs once a second (surb_flush_interval). A verdict reaches the graph at once, so the
planner steers around the relayer from the same flush; but a relayer that is merely the slowest in
its session’s first seconds — judged against a bar borrowed from the fastest, with no history of its
own — is revived by its own late replies a fraction of a second later, and a bump on that verdict
wipes the counterparty’s whole stock for nothing. Measured: one such wipe per ~7 scenario runs, always
at cold start, always the same relayer. Waiting one flush costs a dead relayer one more second of
replies into the void and costs a slow one nothing.
A relayer that still delivers over its other hop is not even judged at the first of the two flushes,
only suspected: see RelayerHealth::has_stood.