fix: v2.2 prefetcher warmup#359
Conversation
BscBlock::rlp_length was filtering out empty withdrawals (Some([])) by treating them as None, making the computed block size 1 byte smaller than geth/erigon for any block that carries an empty withdrawals list. (cherry picked from commit 12556dc)
* chore: add more for debug p2p * chore: add more logs * chore: avoid fetch newest block by newblock which result in failed fetch and p2p reset * chore: avoid fetch unnecessary newest block * chore: request_blocks_by_range only by v2 peer * chore: fetch block prefer announce peer * chore: make reth-bsc peer-manager similar to geth-bsc * chore: try some p2p config * chore: update peer config * fix: fix forward vote bug which too large msg * chore: restore reth deps * chore: remove temp peer dump * chore: remove useless codes * chore: add force prune vote when stage sync * chore: update some trivals (cherry picked from commit a133c6c)
(cherry picked from commit 648696f)
(cherry picked from commit 7cdb875)
Co-authored-by: joey <10592664+joey0612@users.noreply.github.com> Co-authored-by: cbh876 <3930922419@qq.com> Co-authored-by: cbh876 <30834644+constbh@users.noreply.github.com> (cherry picked from commit a1c132d)
* fix: make receive block metrics correct * ci: pin udeps job to nightly-2026-05-11 cargo-udeps 0.1.61 segfaults on nightly >= 2026-05-19 due to an incompatibility with rustc internals. Pin to the last known-good nightly to unblock CI. A follow-up should migrate to cargo-machete to remove the nightly fragility entirely. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com> (cherry picked from commit 32a07ee)
Pull Request ReviewThis PR introduces a broad set of networking, fork-recovery, and mining pipeline improvements for a Rust-based BSC full node, with emphasis on reliability and performance under mainnet conditions. Key updates include version-aware BSC peer registry behavior (bsc/1 vs bsc/2), announcer-aware failover for Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
4 participants
Description
add a description of your changes here...
Rationale
tell us why we need these changes...
Example
add an example CLI or API response...
Changes
Notable changes:
Potential Impacts