BNB Chain Addresses Node Synchronization Challenges

According to Foresight News, BNB Chain has reported that some node operators using the Erigon client are experiencing slower synchronization speeds and increased resource usage. The BSC development team is actively working on performance optimization and expanding client diversity to enhance network stability and support long-term scalability needs. The current situation indicates that while Erigon remains a stable and storage-efficient client on BSC, certain aspects require adjustments. Some operators are facing issues such as reduced synchronization speed, nodes lagging behind the latest blockchain blocks, higher system resource consumption, lack of parallel processing in Merkle root calculations, rapid database expansion during data migration delays, and slower historical data reading due to I/O performance and decompression limitations. Node operators can improve performance through three methods: upgrading hardware with NVMe SSDs (preferably local storage), over 200GB of memory, and high-performance CPU configurations; optimizing startup parameters by setting --bodies.cache = 4G, --sync.loop.block.limit = 5000, and --batchSize = 512M; and maintaining version updates. If chaindata exceeds 100GB during synchronization, operators are advised to delete chaindata and restart to prevent data overflow. The BSC development team is also preparing to launch a new client, Reth, developed in Rust. This client is designed for high performance and parallel processing, expected to significantly enhance network efficiency and lay the foundation for the next phase of BSC's expansion.