BNB Chain’s release notes dated 16 October mark BSC v1.8.1 mandatory for Chapel testnet operators, MEV builders and sentry operators. Jenner is scheduled for 29 October 2026 at 02:30 UTC / 02:30 GMT. The release does not set an exact mainnet activation time.

17 October clarification — mainnet window and source chronology

The official Jenner announcement dated 13 October gives a late-November 2026 mainnet window, with the exact time still to be announced. Its testnet window is late October. The later v1.8.1 GitHub release dated 16 October supplies the precise Chapel testnet time above. These sources support a broad production target, rather than an exact mainnet activation appointment.

The 13 October page still says the hard-fork software has not been published. That wording predates the 16 October release and should not be used to deny the availability of v1.8.1. NetNapz has retrieved both sources; binaries have not been downloaded or tested. This update corrects the earlier headline’s omission of the mainnet window; it does not report a newly announced window on 17 October.

What the test introduces

The notes describe CAS20 controls for stablecoins and tokenized assets, including transfer restrictions and separate minting, burning and seizure roles. Token creation needs separate administrator activation. A payment lane reserves 5% of block gas by default for eligible transfers and listed contracts, subject to governance changes.

Operators are told to review RPC and gRPC changes before replacing binaries. One timestamp-override validation change applies immediately after upgrading, before Jenner activation. The official notes give implementation details; NetNapz has not tested the software.

NetNapz assessment

A testnet release is an opportunity to examine operational behaviour before production commitments. Institutions evaluating controlled assets should ask who holds each administrative role, how those powers can change and how restrictions affect exits. A compliance feature does not itself establish legal approval for an issued asset.

For application teams, compatibility testing matters as much as the headline feature list. Check existing integrations against the new client before assuming a successful restart means the whole service works. Builders should document the configuration they tested and retain a recovery procedure appropriate to their infrastructure.

For BNB holders, the relevant later evidence is a confirmed production schedule, successful deployment and measurable sustained use. The broad mainnet window is a planning target; the checked sources do not establish completed production deployment or incremental token demand. Tokenized exposure also requires examination of its issuer and legal rights; a technical standard alone cannot establish ownership of underlying company shares.

Verification scope

Official English release notes, the 13 October Jenner documentation and the 16 October GitHub release were checked on 17 October 2026. The existing story-matched BNB logo and its CC BY-SA 4.0 attribution are retained. No mainnet deployment or client-performance result is asserted.