August 25, 2026 BNB Pasteur Hard Fork: A Checklist for Holders, Traders and Principal

On August 25, 2026, BNB Smart Chain will usher in an important upgrade. At 02:30 Coordinated Universal Time (UTC) that day, the network will activate the Pasteur hard fork. If you hold a BNB or make a commission or transfer money through the BEP20 chain a few hours before the fork, then this is a day worth paying attention to. For the vast majority of investors, the core message is that your currency itself does not require any manipulation. The chain will automatically switch to the new software, your wallet balance will remain the same, and your address will remain the same. This soothing message is barely visible in German reports, as almost all reports revolve around possible price impacts. This is precisely the reason why this article emphasizes it in the first place.

What you need to proactively plan is: If you plan to recharge or withdraw BNB on a centralized exchange, or initiate a BEP20 transfer on the BNB smart chain, please schedule the operation before approximately 02:20 UTC, or several hours after the fork activation. Binance has announced that it will suspend BEP20 recharge and withdrawal of all tokens during the fork period, but trading functions will remain normal. Delegates who pledge their balance through a validator should check whether their validator is running a new client version. For DeFi users, there is still one uncertainty, which is the core issue of every chain fork: In rare cases, a hard fork can cause individual protocols to be interrupted for hours.

The rest of this article is a short version of two official announcements from the BNB Chain Foundation and the Binance Maintenance Notice, translated into questions you really care about. I will attach a link to the original source so that you can verify it yourself if needed.

What is a hard fork and why Pasteur counts as a hard fork

A hard fork is a change to the rule of blockchain that produces effective blocks. Every node in the network must run new software or lose its connection to the chain. The opposite is a soft fork: it only tightens the rules, so old nodes will still treat new blocks as valid. Hard forks cannot do this. In a controversial hard fork, the chain splits into two branches, and each holder's single token becomes two. The most recent observable example was the separation of eCash (ECX) from Bitcoin on October 31, 2026, for which we wrote a special guide.

This was not the case for Pasteur. It is a planned network upgrade, supported by the entire collection of validators, and rolled out in a coordinated client version. There are no snapshots, no new coins, no 1:1 mapping. Your BNB address remains unchanged and your balance remains unchanged. The fork only changes the rule for the chain to continue writing from block X. That's why no one is asking you to move coins elsewhere before August 25-and the current wave of phishing is trying to take advantage of this, using so-called "migration" as bait to trick you into filling in mnemonic words. Pasteur did not migrate. Anyone who asks you to type in mnemonic words wants your money.

Exact time: Block height is more reliable than clock

The 02:30 UTC given in the announcement is an estimate and is not a guarantee. Like all Ethereum virtual machine forks, activation is highly pegged to blocks, that is, specific blocks on the chain. Since the blocks of the BNB intelligent chain are generated at a pace of seconds, but cannot be accurate to milliseconds, the actual activation time may deviate by a few minutes. If you want to see the actual moment, please pay attention to the Block Browser: Starting from the announced block, the verifier's node client will switch to the new version.

In practice, this means that if you want to be safe, don't schedule the operation for 02:30 UTC, but schedule it for a time window that ends at least 30 minutes earlier or starts at least 30 minutes later. The BNB Chain Foundation is also accustomed to posting final status updates for deployments on blogs and dedicated announcement channels; anyone who is anxious about unfinished transactions can find real-time status there. Need to know the background: The BNB smart chain has experienced more than five hard forks in the past 24 months without major interruptions, including Feynman, Haber, Haber-Fix, Bohr and Lorentz. This is no reason for complacency, but it is a solid record.

What bifurcations have changed technically and why it still affects you

Pasteur bundled two improvement proposals, known in BNB Chain's language as BEP-682 and BEP-695, respectively. Both sound technical, but the core can be summed up in one sentence: The two proposals make the bridge between the old Beacon Chain and the smart chain more secure and plug a loophole that could theoretically be used to attack network assets. As a BNB holder, this means that the chain in which your balance is located becomes more robust against certain types of bridging attacks. The last time such a pattern incident appeared publicly at the L1 level was two years ago, but lasting forward protection requires a coordinated fork.

BEP-682 fixes a vulnerability in the so-called CometBFT light client, which is in part responsible for verifying that blocks on the smart chain from the beacon chain are valid. Without this amendment, a verifier could theoretically sign two contradictory bridging messages without the other party automatically noticing it. After the fork, such attempts will be rejected at the protocol level. BEP-695 tightens the rules for verifiers to rotate signature keys, making it impossible to replay old, leaked keys. Both are so-called hardened changes: invisible to users in daily use until one day attacks occur on the network and are defused by them.

If you want to know how secure such chains are in international comparisons, our overview of BaFin regulated cryptocurrency exchanges lists institutions that use BNB as a tradable asset; due diligence of these providers will consider fork history.

The time window around 02:30 UTC determines whether the transfer will be blocked. Time is passing faster than the announcement suggests.

BNB holders on centralized exchanges: Binance and other alternatives

If your BNB is deposited on a centralized exchange, you don't need to do anything to the coin itself at all. Provide client-side software that adjusts its wallet infrastructure, and your account remains unchanged. Binance clearly stated in the linked announcement: Binance will handle all technical requirements for BNB Chain (BEP20) holders. The translation is: We are responsible, you don't have to do anything.

What Binance clearly opens is that starting from approximately 02:25 UTC on August 25, the recharge and withdrawal of all BEP20 tokens will be temporarily suspended. This applies to BNB, as well as to all other tokens running on the BNB smart chain, from large stablecoins to small project tokens. Orderbook trading remains open during this period, so you can continue buying and selling; only the flow of tokens into and out of the exchange is suspended. The time for Binance to reopen this flow is only generally stated in the announcement, usually one to two hours after confirmation of activation.

If you plan to conduct real on-chain operations during this period, such as withdrawing BNB into your wallet or recharging from your wallet to an exchange, you have three practical options. First: Complete the transfer before the time window, in fact before August 24 or August 25 02:00 UTC at the latest. Second: postpone the operation until the afternoon or evening of August 25. Third: If you have to transfer money and your provider has suspended the BEP20 channel, please check whether the same exchange provides the same token on other chains. For example, many stablecoins also exist on Ethereum, wavefield or Solana, and these chains are not affected by BSC forking. Keep in mind that Ethereum's network costs may be several times higher than BSC, so you should make cost comparisons for alternative chains.

If you want to take the opportunity to switch or diversify your investments, our comparison of the best cryptocurrency exchanges in the German market lists institutions that are solidly regulated, and our comparison of hardware wallets covers devices that allow you to withdraw your balance from provider custody. Both decisions go far beyond any fork, and the fork is one of the times worth making these decisions.

BNB in your own wallet: MetaMask, Trust Wallet, Ledger and Trezor

If your BNB is stored in a self-managed wallet, the same core principles apply: the token remains in place, the address remains the same, and the mnemonic remains the same. What you may need to adjust is the RPC endpoint for wallet-to-chain communication. People using Binance or Ankr's public standard endpoints don't need to do anything because those providers update their nodes in a timely manner. If you are running your own node or using less common RPC, you should check that node has a Pasteur version installed hours before fork. Otherwise, your wallet will not be able to see the new chain for several hours, but your balance will not be affected and will display correctly after switching to the updated RPC.

For Ledger and Trezor's hardware wallets, the situation is as follows: The device itself is not affected by the fork and can still sign transactions at your address. What you need to update is the BNB Intelligent Chain application in the accompanying application, or update the firmware through Suite for Trezor, provided that the manufacturer has released Pasteur compatible updates. These updates are typically rolled out within 48 hours of the fork; before that, the actual signature of the device is independent of the chain rules, so there will be no problems.

The warning is emphasized again, because every fork opens the same attack vector: No wallet provider, exchange, or node operator will ask you to enter mnemonic, private key, or signature via email, message, or pop-up window to "migrate to a new chain." All such requests are phishing without exception. Forking occurs at the protocol level and requires no action from you; even if your wallet software needs to be updated, it will be done through your operating system's regular app store or the manufacturer's official website, and never through links in unsolicited messages.

What should committers and active pledgers do now

Anyone who entrusts BNB on the smart chain, that is, those who bind balances to verifiers to earn pledge rewards, has a checkpoint before August 25. The question is: Is my validator running the Pasteur client version? If so, everything is ready. If not, it may no longer be able to participate in the new chain; according to BEP-695 rules, if there is a delay, its slot will be penalized or temporarily removed from the active set. The BNB Chain Foundation clearly warned in its announcement that validators who fail to adapt to its settings may face penalties or be excluded from active collections. As a trustor, this exclusion will lead to short-term reward losses, but your tokens themselves will not be lost.

Where to check? The vast majority of professional verifier operators on BSC, including Everstake, Figment, Kraken, Coinbase Cloud and nodes operated by Binance itself, publish client status on their status pages or on Channel X. If you delegate to a smaller, unknown validator, you should proactively ask Pasteur about it; there is approximately eleven days window from announcement to activation, which is enough for you to switch validators before fork if the answer does not arrive or is not trustworthy. Switching on BSC does not require unblocking the delegation lock, and new verifiers will take over the rewards from the next era.

If you want to take the opportunity to comprehensively review your pledge strategy, our best pledge platform compares providers that support BNB and other proof-of-stake networks, as well as lists yields, lock-up periods and fees. This is a decision that, once made, will last for years and far exceed the timing of any single fork, bringing more rewards.

BEP20 tokens other than DeFi users and BNB

If your assets are deposited in the DeFi protocol on the BSC, such as the PancakeSwap pool, Venus loan contracts, or as LP tokens in the revenue aggregator, the situation is as follows: Your position remains in the contract, and the smart contract itself will not be moved. In rare cases, the front end of the protocol may briefly display an error because it gets old data from an RPC that has not yet been updated in the first few minutes after the fork. Avoid opening new positions or moving large amounts in the first hour after 02:30 UTC, as the window of time where the front end does not match the actual balance is a window where the risk of slippage increases.

For non-BNB BP20 tokens, namely stablecoins on BSC such as USDT and USDC, packaging tokens such as WBTC or WETH, and thousands of smaller project tokens, the same technical principle applies: contracts exist on the chain, are not affected by rule changes, and the address of your balance remains the same. The only practical impact is the suspension of recharge and withdrawal on the above-mentioned centralized exchanges. If someone holds project tokens in the vesting contract and their payment is due on August 25, in rare cases there may be a delay of several hours. This is annoying, but not a loss.

Safety and control are balanced. This is a measure of the success of a network upgrade.

Pasteur's influence on BNB prices and why the German media got it wrong

German reports mainly focus on price forecasts before the hard fork. Since August 17, almost all five articles on Wallstreet Online, multiple analyses on FinanzNachrichten, and articles by Boerse Express and The Coin Republic have asked the same question: How much will BNB rise or fall around August 25? The honest answer is that no one knows that anyone who gives a number is selling you opinions as facts.

What has been observed historically is that event-driven hard forks, those that do not change supply but improve security or efficiency, have mostly no lasting impact on token prices. Short-term fluctuations of a few percentage points are common and can often be attributed to expectations being factored into the price before activation. People who have held BNB for a long time cannot see the impact of the bifurcation from the chart five years later. Short-term traders should give price fluctuations in these events a weight commensurate with their value: noise, not signals.

Pasteur's economic impact on chains is another matter. Changes to validator rules and bridge security will not change the supply of BNB, the amount of destruction under quarterly repurchase, or the structure of pledge rewards. Anyone who expects Pasteur to create scarcity or increase yields will be disappointed. But anyone who accurately interprets bifurcations as visible evidence that the chain continues to be maintained and reinforced has reason to view them positively from a medium-to long-term perspective. This view is clearly an assessment, not a prediction.

Historical comparison: Smooth running BSC hard forks

A review helps understand the background. The BNB smart chain has experienced many hard forks in its history, but most users are unaware of it. The Feynman fork in the summer of 2024 shortened the block time to three seconds and introduced a new governance structure; Hubble and subsequent Hubble fixes updates strengthened block hashing calculations and their handling in consensus; the Bohr fork in late 2024 removed the outdated Byzantine fault-tolerant path and strengthened verifier rotation; the Lorentz fork in the spring of 2026 significantly shortened the final confirmation time (i.e., finality) of the block, making it the most significant change in user perspective. Pasteur follows the same series in rhythm and scope.

None of these forks caused long network outages, caused chain splits, or caused users to have to claim their balances. The only actually relevant side effects-trading delays during the activation window and hours of waiting on the centralized exchange-have the same probability of occurring in the Pasteur fork as in previous forks. Therefore, the advice of this article for most readers is: Do nothing, just avoid making transfers within the time window. For those who operate the chain or serve as verifiers, the situation is different; for passive holders, Pasteur is an administrative process that does not involve them.

BNB Pasteur Hard Fork: Points You Should Remember

Check the transfers and payments you plan to make around 02:30 UTC on August 25, 2026. On Binance and most large exchanges, BEP20 deposits and withdrawals will be suspended for approximately two hours. Please schedule the operation late before the fork or late August 25. If you want to take this opportunity to withdraw your balance from third-party hosting, you can find tested devices in the Hardware Wallet Comparison.

The entrusting party should proactively ask his verifier whether the Pasteur version has been run? If not, please switch before August 25. If you use fork as an opportunity to rethink the overall pledge structure, please compare providers, yields and lock-in periods. See our overview of the best pledge platforms for the German market for more details.

Ignore all requests for "migration" that require you to enter mnemonic words or private keys. For a coordinated hard fork like Pasteur's, there is no migration; switching occurs at the protocol level and requires no action from you. If you want to take this opportunity to structure your trading venue, you can find BaFin authorized institutions in our comparison of the best cryptocurrency exchanges for the German market.

(As of August 20, 2026. This article does not constitute investment advice. Price and fee structures are subject to change; please check terms with your provider before purchasing.)