When a signer gets a block validation response back from its node, it first checks if it has locally marked the block as GloballyAccepted or GloballyRejected. If this is the case, the signer doesn't broadcast a BlockResponse.
It would be better for the signer to still broadcast a block response, for a few reasons:
Even if this signer has seen enough responses to mark the block as accepted, the miner and/or other signers might not have
For monitoring purposes, it's better to know that a signer broadcasted a block response a little slower than others, than to not know if the signer was "alive" or not
With potential behavior around withholding of PoX rewards, we don't want to be penalizing just because a signer is in the >70%th latency percentile for a block
When a signer gets a block validation response back from its node, it first checks if it has locally marked the block as
GloballyAcceptedorGloballyRejected. If this is the case, the signer doesn't broadcast aBlockResponse.It would be better for the signer to still broadcast a block response, for a few reasons:
Relevant code:
https://github.com/stacks-network/stacks-core/blob/db35bfec877c368e1ccb8640dccc4bfc3430e914/stacks-signer/src/v0/signer.rs#L497-L509