BNB Chain just shipped Pasteur. The hidden safety rules are now the story.
Pasteur puts two quiet assumptions in public: who can validate bridge messages, and who gets to build blocks before validators sign.
CryptoVibe Desk · bnb-chain · bsc · pasteur
- →BNB Chain's BSC mainnet reached the scheduled Pasteur upgrade time on August 25 at 02:30 UTC, per its release page.
- →The important changes reject duplicate bridge validators and support builder-proposed blocks with validator blind signing.
- →Watch whether validators and RPC teams report signing or block-building issues before September ends.
- hard fork → A hard fork is a network upgrade where nodes must follow new rules to stay on the same chain.
- bridge validator → A bridge validator helps approve messages or transfers between one chain and another.
- blind signing → Blind signing means a validator signs a block proposal without seeing every detail inside it first.
- builder-proposed block → A builder-proposed block is a block assembled by a separate builder before a validator signs it.
BNB Chain just reached Pasteur on BSC mainnet. The scheduled time was August 25 at 02:30 UTC, per BNB Chain's release page. The mainnet note is short. The useful detail sits in the earlier Chapel testnet change list.
The code-level story is not branding. Pasteur rejects duplicate bridge validators and adds support for builder-proposed blocks with validator blind signing. That puts bridge assumptions and block-building flow on the front page. They were always security-critical. Now they're harder to ignore.
At the contract level, duplicate bridge-validator rejection is the cleaner change. A bridge validator set should not count the same party twice. If it does, the numbers don't add up. Your funds depend on the bridge counting distinct signers, not repeated entries wearing different labels.
The block-building change is trickier. Builder-proposed blocks can make block production more specialized. Validator blind signing can also narrow what validators inspect before signing. The tradeoff is cleaner block flow for more trust in the builder path. That's the catch.
BNB Chain lists more upgrade work too. The release materials point to a genesis-contract v1.2.6 commit URL. The engineers know this is infrastructure. The marketing version calls it an upgrade. Read the PR diff, not the thread.
For BSC users, Pasteur is not a new app feature. It's a security and block-production change. If you're building on BSC, watch the signing path now, not after the first weird block lands.
BNB Chain's choice to make duplicate bridge-validator rejection a hard-fork rule was correct because bridge security cannot depend on off-chain cleanup.
By September 30, watch for zero Pasteur-related chain rollbacks and no validator reports of bad blind-signing behavior on BSC mainnet.
Primary links and supporting reads used by the desk for this story.
Forward this.
