Hi BNB Chain team,
We are following up on this report, as we have not yet seen a public response. Since our initial disclosure, we have completed further analysis and validated the issue on a controlled private testnet running BSC v1.6.6. Under the evaluated conditions, two conflicting branches can each finalize new blocks after activating different validator sets.
To facilitate technical discussion and issue tracking, we have opened a GitHub issue containing our updated analysis: Safety issue in Binance Consensus · Issue #3800 · bnb-chain/bsc · GitHub
We would appreciate confirmation that the report has reached the relevant team, as well as any initial assessment of whether later releases remain affected. We would be happy to provide additional technical details through an appropriate private channel and to collaborate on evaluating the proposed mitigation.
We hope this report will be useful to the BNB Chain team and community in improving the security and robustness of the system.