BNB Pasteur hardfork Aug 25 needs no migration, only transfer timing

On August 25, 2026 at 02:30 UTC, BNB Smart Chain activates the Pasteur hardfork, a planned upgrade that hardens bridge verification and validator-key handling without creating new coins or requiring any user migration.

"Binance will handle all technical requirements for BNB Chain (BEP20) holders," the exchange said in its maintenance notice, while the BNB Chain Foundation detailed the upgrade in a blog post dated Aug 21.

The fork bundles two improvement proposals. BEP-682 closes a weakness in the CometBFT light client that could have allowed a validator to sign two contradictory bridge messages; BEP-695 tightens rules for rotating validator signing keys, blocking replay of compromised keys. Node operators must run client version 1.7.7 before activation.

For most holders the practical effect is timing. Binance suspends BEP20 deposits and withdrawals for all tokens from roughly 02:25 UTC, with order-book trading continuing. Delegators should confirm their validator runs the new client, since a lagging node risks penalties or removal from the active set under BEP-695.

What changes for holders, traders, and delegators

Activation is tied to a block height, not the clock, so the 02:30 UTC time is an estimate that can shift by minutes. Anyone planning a BEP20 transfer should move it before 02:00 UTC or wait several hours after activation. Binance typically reopens the deposit and withdrawal flow one to two hours after confirmed activation.

Self-custodied wallets on MetaMask, Trust Wallet, Ledger, or Trezor need no action on the coins themselves. Users running a self-operated node or a less common RPC endpoint should confirm it carries the Pasteur version, or the wallet may not see the new chain for a few hours. Hardware wallet firmware updates with Pasteur compatibility typically arrive within 48 hours of the fork.

Delegators staking BNB through a validator should check the operator's status page. Major operators including Everstake, Figment, Kraken, Coinbase Cloud, and Binance's own nodes publish client status; smaller validators should be asked directly. Switching validators on BSC carries no undelegation lock-up, and rewards transfer from the next epoch.

DeFi positions on PancakeSwap, Venus, or yield aggregators stay in their contracts and are not moved. The main risk is a brief front-end mismatch in the first hour after activation, so avoid entering new positions or moving large amounts in that window. BEP20 stablecoins such as USDT and USDC on BSC, and wrapped tokens like WBTC and WETH, are unaffected beyond the exchange pause.

Why the fork matters, and what it does not do

Pasteur follows five prior BSC hardforks in the past 24 months — Feynman, Haber, Haber-Fix, Bohr, and Lorentz — none of which caused a chain split or required users to claim balances. The upgrade does not alter BNB supply, the quarterly burn, or staking reward structure, so it carries no direct price effect. Its value is defensive: it closes a bridge-verification gap that could theoretically have been exploited for an attack on assets.

The fork also opens a known phishing vector. No wallet provider, exchange, or node operator will ask for a seed phrase, private key, or signature to "migrate" to the new chain. Any such request is a scam.

This article is for informational purposes only and does not constitute investment advice.