pub const REPORT_LAG: Duration;Expand description
How long a counterparty’s SURB level report is assumed to have been on its way: the production of this long before a report arrives is added to the level it carries.
A report says what the counterparty held when it was written, before the SURBs that were in
flight to it reached it, so taken as it stands it pulls the believed level below the truth by
that much. One second covers the one-way latency of a multi-hop return path with mixing; a lag
taken too long errs on the high side, which the counterparty’s distress signal corrects within a
packet, where a lag taken too short errs low and is corrected only by the next report. (The much
larger lag measured after a bump, a whole notify period, was the keep-alive stream sampling the
level when the rate limiter pulled the item rather than when it released it; that is fixed at the
source in spawn_keep_alive_stream and no longer something this constant has to cover.)