What happens on BNB Smart Chain on August 25, 2026 On August 25, 2026 at 02:30 UTC, BNB Smart Chain activates the Pasteur hardfork. If you hold BNB, delegate your balance or plan a transfer o
On August 25, 2026 at 02:30 UTC, BNB Smart Chain activates the Pasteur hardfork. If you hold BNB, delegate your balance or plan a transfer on a BEP20 chain in the hours before, this is the date to pay brief attention to. For the vast majority of investors, the core of the news is this: there is nothing to do with your coins themselves. The chain switches to the new software automatically, your wallet shows the same balance afterwards, and your address stays the same. That reassurance appears in almost no German-language coverage, because nearly all of it is written around the possible price effect. Which is precisely why it comes first here.
What you should plan for actively is this: if you want to make a BNB deposit or withdrawal on a centralised exchange, or start a BEP20 transfer on BNB Smart Chain, move it either to the time before roughly 02:20 UTC or to several hours after activation. Binance has suspended BEP20 deposits and withdrawals for all tokens around the fork, while trading continues. Delegators who stake their balance through a validator should check once whether their particular validator is running the new client version. For DeFi users, one residual uncertainty remains, and it is the one at the heart of every chain split: in rare cases a hardfork can disrupt individual protocols for a few hours.
The rest of this article is the short version of what stands in the two official announcements from the BNB Chain Foundation and in the Binance maintenance notice, translated into the question that actually concerns you. I link the primary sources so that you can check any point yourself if you need to.
A hardfork is a change to the rules by which a blockchain produces valid blocks. Every node in the network has to run the new software, otherwise it loses its connection to the chain. The opposite term is soft fork: it only tightens the rules, so that old nodes continue to regard the new blocks as valid. With a hardfork that is not possible. In a contentious hardfork the chain splits into two branches, and every holder's single coin becomes two. That is exactly what could be observed most recently on October 31, 2026 with the separation of eCash (ECX) from Bitcoin, for which we have written a separate guide.
Pasteur is not such a case. It is a planned network upgrade, supported by the entire validator set and rolled out in a coordinated client version. There is no snapshot, no new coin, no 1:1 credit. Your BNB address remains the same address, your balance remains the same balance. The fork only changes the rules by which the chain continues writing from block X onwards. That is also why nobody is asking you to move your coins somewhere else before August 25, and it is precisely this trap that current phishing waves want to set for you, advertising a supposed "migration" with a form field for your seed. There is no migration with Pasteur. Anyone who asks you to enter your seed wants your money.
The time of 02:30 UTC given in the announcements is an estimate, not a guarantee. As with every Ethereum Virtual Machine fork, activation is tied to a block height, meaning a specific block on the chain. Because blocks on BNB Smart Chain are produced at a rhythm of seconds but not to the millisecond, the real activation moment can shift by a few minutes in either direction. If you want to see the actual moment, follow a block explorer: from the announced block onwards, the validators' node client switches to the new version.
In practice this means that if you want to be safe, you do not plan your action for the minute of 02:30 UTC, but for a window that ends at least 30 minutes before it or begins at least 30 minutes after it. The BNB Chain Foundation has also made a habit of publishing the final status updates on the rollout on its blog and in a dedicated announcement channel; anyone sitting nervously on an open transaction will find the real state of play there. Important for context: BNB Smart Chain has passed through more than five hardforks in the past 24 months without major disruption, among them Feynman, Haber, Haber-Fix, Bohr and Lorentz. That is no reason for complacency, but it is a track record.
Pasteur bundles two improvement proposals, called BEP-682 and BEP-695 in BNB Chain's own language. Both sound technical, but the core can be stated in a single sentence: both proposals make the bridge between the old Beacon Chain and the Smart Chain more secure and close a gap that could theoretically have been abused for an attack on assets in the network. For you as a BNB holder, that means the chain your balance sits on becomes somewhat more robust against a particular type of bridge attack. The last publicly known incidents at L1 level showing this pattern date back two years, but durable forward protection costs a coordinated fork.
BEP-682 closes a weakness in the so-called CometBFT light client, the part of the software that verifies on the Smart Chain which blocks from the Beacon Chain are valid. Without this correction, a validator could in theory have signed two contradictory bridge messages without the other side automatically noticing. After the fork, such an attempt is rejected at the protocol level. BEP-695 tightens the rules under which validators have to rotate their signing keys, making it impossible to replay old, compromised keys. Both are so-called hardening changes: invisible to you as a user in everyday terms, until one day an attack appears on the network and comes to nothing because of them.
If you want to know how secure such a chain stands in international comparison, our overview of regulated crypto exchanges with BaFin authorisation lists the firms that carry BNB as a tradable asset; the diligence of these providers factors fork histories in.
The window around 02:30 UTC decides whether transfers back up. The sand runs faster than the announcements suggest. If your BNB sits on a centralised exchange, you need to do nothing at all for the coin itself. The provider adapts the client software of its wallet infrastructure, and your account remains unchanged. Binance puts it in the announcement linked above along these lines: Binance will handle all technical requirements for BNB Chain (BEP20) holders. Translated, that means: we take care of it, you do not have to do anything.
What Binance does explicitly switch on is a temporary pause of deposits and withdrawals for all BEP20 tokens from around 02:25 UTC on August 25. This applies to BNB, but also to every other token running on BNB Smart Chain, from large stablecoins down to small project tokens. Order book trading stays open during this period, so you can continue to buy and sell; only the flow of coins to and from the exchange pauses. When Binance reopens that flow is announced only in general terms in the same notice, and it usually happens one to two hours after confirmed activation.
If you are planning a genuine on-chain movement during this time, for example withdrawing BNB to your own wallet or depositing from a wallet to the exchange, you have three practical options.
First: put the transfer through before the window, in practice on August 24 or by 02:00 UTC on August 25 at the latest. Second: move it to the afternoon or evening of August 25. Third: if you absolutely must transfer and your provider pauses the BEP20 route, check whether the same exchange offers the same coin on a different chain. Many stablecoins, for instance, also sit on Ethereum, TRON or Solana, and those chains are unaffected by the BSC fork. Keep in mind that the network fee on Ethereum can be a multiple of the BSC fee, so you should run a cost comparison for the substitute chain.
If you want to take the occasion to switch or diversify, our comparison of the best crypto exchanges for the German market lists the firms with solid regulation, and our hardware wallet comparison covers the devices that let you take your balance out of a provider's custody. Both are decisions that reach far beyond any single fork, and the fork is one of those occasions worth using to make them once.
If your BNB sits in a self-custodied wallet, the same core applies: the coin stays where it is, your address stays the same, your seed phrase stays the same. What you may have to adjust is the RPC endpoint through which your wallet talks to the chain. Anyone using one of the public standard endpoints from Binance or Ankr has nothing to do, as those providers update their nodes in good time. Anyone running a self-operated node or using a less common RPC should check in the hours before the fork whether that node has the Pasteur version installed. Otherwise your wallet will not see the new chain for a few hours, though your balance would be untouched and would display correctly again after switching to an updated RPC.
For hardware wallets from Ledger and Trezor the position is this: the devices themselves are unaffected by the fork and still sign transactions to your address. What you should update in the companion app is the BNB Smart Chain app or, with Trezor via Suite, the firmware, once the manufacturers have released an update with Pasteur compatibility. These updates are typically rolled out in the 48 hours after the fork; until then it remains unproblematic, because the device's actual signature is independent of the chain rule.
And once again the warning, because every fork opens the same attack vector: no wallet provider, no exchange and no node operator will ask you by email, message or pop-up to enter your seed, your private keys or a signature anywhere in order to "migrate to the new chain". Such requests are phishing without exception. The fork happens at the protocol level, without any action from you; and even if an update to your wallet software were required, it would come through your operating system's regular app store or the manufacturer's official website, never through a link in an unsolicited message.
Anyone who delegates BNB on the Smart Chain, meaning anyone who has bound their balance to a validator in order to earn staking rewards, has a single checkpoint before August 25. The question: is my validator running the Pasteur client version? If yes, everything is settled. If no, it risks no longer participating in the new chain; under the BEP-695 rule its slot will be penalised or temporarily removed from the active set in the event of a relevant delay. The BNB Chain Foundation warns in its announcement in so many words that a validator failing to adapt its setup could suffer penalties or exclusion from the active set. For you as a delegator, such an exclusion is annoying because your rewards drop out in the short term; your coins themselves are not lost in the process.
Where do you check this? The overwhelming majority of professional validator operators on BSC, among them Everstake, Figment, Kraken, Coinbase Cloud and the nodes operated by Binance itself, publish their client status on their own status pages or on their X channels. Anyone delegating with a smaller, unknown validator should ask actively about Pasteur once; the window between announcement and activation, at roughly eleven days, is large enough to switch validators before the fork if the answer fails to arrive or fails to convince. Switching is possible on BSC without an undelegation lock-up, and the new validator takes over the rewards from the next epoch.
If you want to use the opportunity to review your staking strategy as a whole, our comparison of the best staking platforms lists the providers that support BNB and other proof-of-stake networks, with yields, lock-up periods and fees side by side. That is a decision which, once made, holds for years and moves far more return than the timing of any single fork.
If your assets sit in DeFi protocols on BSC, for example in a PancakeSwap pool, in a Venus lending contract or as an LP token in a yield aggregator, the position is this: your positions stay in the contracts, and the smart contracts themselves are not moved. What can happen in rare cases is a brief misrepresentation in a protocol's front end, because it displays older data from a not yet updated RPC in the first minutes after the fork. Avoid entering new positions or moving larger amounts in the first hour after 02:30 UTC, because the windows in which the front end does not match the actual balance are windows of elevated slippage risk.
For BEP20 tokens that are not BNB, meaning stablecoins such as USDT and USDC on BSC, wrapped tokens such as WBTC or WETH on BSC, and the thousands of smaller project tokens, the same technical principle applies: the contracts live on the chain, they are not touched by the rule change, and the address of your balance stays the same. The only practical effect is the deposit and withdrawal pause at centralised exchanges mentioned above. Anyone holding a project token in a vesting contract whose payout would have fallen due precisely on August 25 may in exceptional cases see a delay of a few hours. That is irritating, but it is not a loss.
Security and control in balanced proportion. That is the measure of whether a network upgrade succeeds. German coverage is dominated by the price forecast ahead of the hardfork. Five pieces from Wallstreet Online since August 17, several analyses at FinanzNachrichten, plus articles at Boerse Express and The Coin Republic, and the question runs almost throughout: how far will BNB rise or fall before and after August 25? The honest answer is that nobody knows, and anyone quoting a number is selling you an opinion as a fact.
What could be observed historically is this: event-driven hardforks, meaning those that bring no real change in supply but improve security or efficiency, mostly have no lasting effect on the coin price. Short-term moves of a few percent in either direction are common and can often be explained by expectations already priced in before activation. Anyone holding BNB for the long term will not be able to read the fork out of the chart in five years. Anyone looking to trade short term should give the price moves around such events no more weight than those moves deserve: noise, not signal.
What Pasteur does to the economics of the chain is a separate point. The changes to validator rules and bridge security do not alter the supply of BNB, they do not alter the burn under the quarterly buybacks, and they do not alter the structure of staking rewards. Anyone expecting Pasteur to create scarcity or raise yields will be disappointed. But anyone reading the fork precisely as visible proof that the chain continues to be maintained and hardened has a reason to view that positively over the medium to long term. This view is explicitly an assessment, not a forecast.
A look back helps with context. BNB Smart Chain has seen several hardforks in its history that passed largely unnoticed by users. Feynman in the summer of 2024 cut block time to three seconds and introduced a new governance structure; Haber and the later Haber-Fix update hardened the calculation of block hashes and their treatment in consensus; Bohr at the end of 2024 cut away outdated Byzantine fault tolerance paths and tightened validator rotation; Lorentz in the spring of 2026 substantially shortened the time to final confirmation of a block, the so-called finality, and was therefore the most visible change from a user's point of view. Pasteur follows the same series in cadence and scope.
None of these forks led to a prolonged network outage, none to a chain split, none to a situation in which users had to claim their own balance. The only practically relevant side effect, transaction delays in the window around activation and a few hours of waiting at centralised exchanges, is to be expected with Pasteur at the same probability as with its predecessors. That is why this article's recommendation for most readers is to do nothing, other than keeping transfers out of the window. Anyone operating the chain or working as a validator has a different perspective; for the passive holder, Pasteur is an administrative process that does not concern them.
(As of August 20, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)
