BNB Chain has renewed its promotion of the Red Alarm security tool while urging BSC-Reth node operators to install a hotfix addressing a blockchain state calculation bug. BNB Chain has renewed attention on Red Alarm, a security scanner originally introduced in 2022. The DappBay service lists risky applications and lets users inspect smart contracts before making transactions. BSC-Reth operators on mainnet and testnet are urged to install v0.1.4-hotfix and restart their nodes.
The hotfix addresses incorrect state-root calculations and requires neither database migration nor another hard fork. BNB Chain said opBNB does not use op-reth and described the BSC-Reth exposure as limited. In a November 7 post, BNB Chain directed users to its DappBay Red Alarm list, where decentralized applications and smart contracts are flagged when they meet potentially risky conditions.
The reminder followed a separate November 6 security update for node operators, who were told to upgrade to v0.1.4-hotfix and restart their software. The two notices cover different parts of the network. Red Alarm gives wallet users information about applications before they interact with them, while the Reth update fixes software used by some of the machines that process and check blockchain data.
BNB Chain did not link the two notices
BNB Chain did not link the two notices to a single security incident. Red Alarm Lists Risky Apps Before Users Connect Wallets The DappBay page gives visitors a list of high-risk projects and contracts, together with a scanner for checking a smart contract or wallet address. Users can browse entries by application category, blockchain, risk driver and listing date, allowing them to examine the warning attached to a particular project.
One common warning concerns inaccessible project websites. A listing may indicate that an application website no longer works, although the tool notes that this can happen for several reasons, including a project shutting down. Other entries identify suspected Ponzi-style arrangements or contract features that could expose users to loss. In its latest reminder, BNB Chain said, “Keeping users safe takes ongoing work across crypto.” It described Red Alarm as a way of flagging potentially high-risk decentralized applications and contracts so users have more information before making decisions.
https://twitter.com/BNBCHAIN/status/2119037188947972151 The service is not new. BNB Chain introduced Red Alarm through DappBay in July 2022, and an August 2022 update said the system had scanned more than 3,300 contracts in its first weeks. At the time, the network directed visitors to over 50 projects flagged as presenting risks. The warning system is informational, not a guarantee that any unlisted application is safe.
DappBay says its risk assessments draw on automated
DappBay says its risk assessments draw on automated scans, models and available contract information, and warns that ratings should not be treated as endorsements or a substitute for users checking projects themselves. BSC-Reth Operators Told to Install November 6 Hotfix While BNB Chain was drawing attention to suspicious applications, its infrastructure developers had issued a more immediate instruction to operators running the BSC-Reth execution client.
The November 6 GitHub release recommends installing v0.1.4-hotfix as soon as possible and restarting the node afterward. The instruction covers BSC-Reth on both mainnet and testnet. Its stated audience includes validators, block builders involved in maximal extractable value activities, full-node operators and sentry operators, rather than ordinary wallet users. According to the release notes, the fix addresses an error that could make Reth calculate the wrong state root under specific conditions.
A state root records a cryptographic representation of blockchain account balances, smart contract storage and other network state; nodes rely on it when checking that they agree on valid data. The release incorporates a correction from the upstream Reth project concerning a legacy calculation path. BNB Chain said operators need neither a database migration nor a separate hard fork to apply this particular fix, making the required action an installation followed by a restart.
BNB Chain Says opBNB Is Not Affected
BNB Chain Says opBNB Is Not Affected by Reth Issue Before releasing the patch, BNB Chain acknowledged the risk in a November 6 notice and said the effect on BSC-Reth was limited. It clarified that opBNB does not use op-reth, the related client involved in the security discussion. The warning concerned execution software, not the Red Alarm contracts list. In its earlier coverage, crypto.news described the Reth bug and the response from Base, whose developers said they patched their block-building nodes and verified that users had not been affected.
BSC-Reth’s latest release follows a November 3 update that scheduled the Jenner hard fork for December 8, 2026, at 02:30 UTC. That previously announced upgrade introduces separate network changes and carries its own compatibility deadline for mainnet node operators. The Jenner changes include a Payment Lane proposal that reserves a default 5% of each block’s gas capacity for eligible payments.
The feature is intended to preserve space for approved transfers when other transactions compete for block capacity, according to the network’s published upgrade details.
