Constant BLOCK_COUNT_VOTE_DELAY 

pub const BLOCK_COUNT_VOTE_DELAY: u64 = _; // 7u64

How many blocks a peer’s block count vote trails its bitcoin backend: the finality delay, plus one block of slack. Processing a new consensus block count waits for the local backend to report the consensus count plus the finality delay, and without the slack that is exactly the block the voter saw, so a backend a little behind, or a backend status that is stale (it is polled once a minute), stalled item processing on every new block.

Lives here rather than in the server so that the client can tell how deep a peg-in has to be before the federation claims it.