fix: make the received block metrics correct

[will-2012]

Description

Make the received block metrics correct to ensure the reth_chain_delay_block_recv metrics are accurate for more effective network latency troubleshooting.

Rationale

1. Make the ms-timestamp correct.
2. Do not update the received block metrics of the self-mined block.

Example

N/A.

Changes

Notable changes:

• Metrics*

Potential Impacts

N/A.

[hashdit-bot]

Pull Request Review

This PR refactors block delay metric handling in the Parlia consensus path to use full millisecond-precision block timestamps derived from the header (including Lorentz-era ms data), instead of second-only timestamps. It also separates metric behavior between network-received blocks and self-mined blocks by introducing register_self_mined_block, preventing locally produced blocks from contaminating the chain.delay.block_recv propagation metric. Call sites in block import service were updated to pass full headers and use the new self-mined registration path.

Sensitive Content

No sensitive content detected.

Security Issues

No serious security issues detected.

---

Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits.

[hashdit-bot]

Pull Request Review

This PR refactors chain-delay metric handling in a Rust blockchain client (Parlia/BSC context) to improve accuracy of reth_chain_delay_block_recv measurements. It changes block timestamp handling to use millisecond precision derived from the full header (calculate_millisecond_timestamp) and separates logic for network-received blocks vs self-mined blocks. It also updates call sites in block import flow accordingly and pins the CI udeps nightly toolchain to a specific date for reproducibility.

Sensitive Content

No sensitive content detected.

Security Issues

No serious security issues detected.

---

Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits.