CoinWorld News reports that on February 4th, Base released a post-mortem report regarding the network outage on January 31st. On that day, Base experienced transaction loss and inclusion delays caused by a change in transaction propagation configuration, which led block builders to repeatedly fetch transactions that could not be executed due to rapid increases in base fees. Base stated that the issue has been mitigated through rollback of the changes, and network stability has been restored. The team is taking measures to prevent a recurrence, including optimizing the transaction pipeline, removing unnecessary P2P overhead, and adjusting the mempool queue, with an estimated timeline of about one month. Additionally, Base is working on improving the alert system and change monitoring mechanisms.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
CoinWorld News reports that on February 4th, Base released a post-mortem report regarding the network outage on January 31st. On that day, Base experienced transaction loss and inclusion delays caused by a change in transaction propagation configuration, which led block builders to repeatedly fetch transactions that could not be executed due to rapid increases in base fees. Base stated that the issue has been mitigated through rollback of the changes, and network stability has been restored. The team is taking measures to prevent a recurrence, including optimizing the transaction pipeline, removing unnecessary P2P overhead, and adjusting the mempool queue, with an estimated timeline of about one month. Additionally, Base is working on improving the alert system and change monitoring mechanisms.