BNB Chain this week pushed two separate security notices aimed at different parts of its ecosystem: a renewed public reminder to use the DappBay “Red Alarm” scanner, and an urgent technical hotfix for operators running the BSC‑Reth execution client. What happened - Nov. 7: BNB Chain promoted DappBay’s Red Alarm list — a public scanner and database that flags decentralized apps and smart contracts that meet potentially risky conditions. The network reposted its message, saying “Keeping users safe takes ongoing work across crypto,” and pointing users to the Red Alarm entries and contract scanner. - Nov. 6: BNB Chain published a GitHub release asking operators of BSC‑Reth nodes (mainnet and testnet) to install v0.1.4‑hotfix and restart their software immediately. The patch corrects a rare bug that could cause Reth to compute an incorrect state root under certain conditions. Two notices, different audiences - Red Alarm targets end users and wallet holders: it surfaces warnings about projects (e.g., dead or inaccessible websites, suspected Ponzi-like mechanics, or risky contract features) so people can make more informed decisions before interacting with dApps. - The Reth hotfix targets infrastructure operators — validators, block builders (including MEV actors), full nodes and sentry nodes — and fixes execution software used to process and validate chain data. Why the Reth fix matters The bug addressed in v0.1.4‑hotfix affected a legacy calculation path that, in edge cases, could lead to an incorrect state root. The state root is a cryptographic summary of account balances, contract storage and other network state; nodes rely on it to confirm they agree on the same valid data. According to BNB Chain, the patch is an upstream correction from the Reth project, and operators do not need a database migration or a hard fork — just install the hotfix and restart. Scope and clarifications - BNB Chain said the impact on BSC‑Reth was limited and emphasized this release is separate from the Red Alarm advisory; it did not tie the two notices to a single incident. - BNB Chain noted opBNB does not use op‑reth, clarifying that other execution clients or Layer‑2 components are unaffected by this particular issue. - The Reth advisory follows similar activity in the space: Base developers earlier patched block‑building nodes after a related Reth bug and reported users were not affected. About Red Alarm Launched in July 2022, Red Alarm (via DappBay) is an informational risk scanner — not a definitive safety endorsement. Early updates said it scanned more than 3,300 contracts in its first weeks and flagged 50+ projects as risky. DappBay combines automated scans, models and contract data to produce risk flags, and encourages users to treat the ratings as guidance rather than a substitute for their own due diligence. Other network news BSC‑Reth’s hotfix release comes after a Nov. 3 update that set the Jenner hard fork for Dec. 8, 2026 at 02:30 UTC. Jenner includes several changes — notably a Payment Lane proposal that reserves a default 5% of each block’s gas capacity for eligible payments — and carries its own compatibility deadlines for node operators. What to do - Wallet users: consult DappBay’s Red Alarm list and use the contract scanner before interacting with unfamiliar dApps. - Node operators (BSC‑Reth): install v0.1.4‑hotfix and restart your node as soon as possible; no DB migration or hard fork is required for this fix. BNB Chain’s dual messaging reinforces two ongoing needs for blockchain security: user-facing tooling to highlight risky apps, and prompt operator action to keep node software correct and in consensus. Read more AI-generated news on: https://app.chaingpt.org/news