BNB Chain Details New L1 With 200ms Blocks, No New Token

BNB stays central as New L1 develops beside BSC

BSC remains the general-purpose network serving the existing ecosystem. New L1 is designed for applications that need architectural changes and faster transaction handling, rather than a mandatory migration of BSC’s users or contracts.

The official network parameters specify a 200-millisecond block interval, equivalent to about five blocks a second. The chain’s name is still marked to be determined, its chain ID is not finalized, and the page warns that devnet parameters may change.

BNB remains the economic link. The overview says BNB will move from BSC through a native bridge, still under development, and pay network fees. The documentation does not announce a live bridge or a token conversion window.

Its governance design also uses staked BNB. Staking creates a non-transferable voting ledger called govBNB at a one-to-one ratio; voting power becomes active after delegation. That ledger is distinct from launching another tradable asset.

The distinction limits what the announcement establishes for holders. It identifies a planned additional use for BNB but supplies no public-network transaction volume or fee revenue. A running internal network cannot yet show how much demand paying users will generate.

New L1’s 20ms signal is not settled execution

The speed figures describe different stages. BNB Chain targets transaction-order finality in under one second, while a smaller streamed block can deliver an earlier signal in roughly 20 milliseconds.

The preconfirmation specification calls that early signal a validator’s promise about inclusion and ordering. It can be revoked and says nothing about whether the transaction succeeds when executed.

That separates a responsive application screen from a completed transfer. The network orders transactions independently of running their instructions, so an application can learn where a transaction belongs before its resulting balance changes are settled.

Execution finality comes later, after a subsequent block records the execution commitment and that block finalizes. The documentation tells applications relying on state changes to wait for that stage. Describing the earlier 20-millisecond signal as irreversible settlement would overstate the design.

For trading and payment developers, this changes what a confirmation indicator should mean. An early acknowledgment can improve responsiveness, but releasing goods or crediting withdrawable balances depends on the later result.

The same distinction applies when comparing New L1 with Solana’s Alpenglow finality upgrade. Block intervals, early promises and final execution measure different things; a smaller headline latency alone does not establish equivalent settlement guarantees.

BNB developers face new fees and unfinished privacy

The BSC migration checklist identifies a direct cost change: New L1 charges for the gas limit submitted with a transaction, rather than only the computation actually used.

Gas is the unit used to price network computation. In the documentation’s example, a call needing 70,000 gas but submitted with a 500,000 limit is charged for 500,000. Large safety buffers therefore become expensive, while setting the limit too low can still make execution fail.

The checklist says existing contract bytecode can run unchanged, but applications using block counts to measure elapsed time need review. Faster blocks alter vesting periods, price-observation windows and auction durations written around a previous block cadence.

The separate account-abstraction guide describes native passkey signing, batches of up to 64 calls, limited delegated keys and fee sponsorship. Sponsorship lets another account pay transaction costs; it does not mean the network has eliminated those costs.

Privacy is less mature. The shielded-pool documentation describes optional transfers that hide sender, recipient and amount, but explicitly says the feature is unaudited and not production-ready. Its cryptographic setup is imported rather than based on a New L1 ceremony, with both issues remaining open before mainnet.

These are published development limitations, rather than a reported theft or wallet compromise. They put a practical boundary around the privacy claim while the network remains internal.

Alternative.me’s Bitcoin sentiment index stood at 50, or Neutral, on October 26, compared with 54 the previous day. It measures broader Bitcoin sentiment, not readiness or demand for New L1.

The official FAQ confirms that mainnet is not live. The next verifiable steps are public network details, an operational bridge and updated privacy-readiness disclosures; the current manual does not provide a firm public launch date.