Skip to content
Crypto.world

The Ledger

BNB Chain Publishes Technical Design for Its New L1

BNB Chain’s New L1 design targets 200-millisecond blocks and transaction pre-confirmations in about 20 milliseconds. The documentation describes an internal devnet, not a public testnet or mainnet, and flags its shielded pool as unaudited.

BNB Chain Publishes Technical Design for Its New L1

200-millisecond blocks, with a second clock for execution

BNB Chain’s new Layer 1 targets a 200-millisecond block interval and transaction pre-confirmations in roughly 20 milliseconds, according to technical documentation dated October 22. The design, called New L1, is an EVM-compatible network aimed at latency-sensitive activity, including high-frequency trading, payments, confidential finance and agent-driven applications.

Those figures describe different stages, not a single promise that transactions become irreversible in 20 milliseconds. A pre-confirmation is a validator’s revocable signal about a transaction’s ordering and position. The documentation targets sub-second finality for transaction order, while execution finality comes later, after a subsequent block records the execution result and that block finalizes.

Consensus can move before the EVM finishes

New L1 separates transaction ordering from execution. Validators agree on the order without first running every transaction; execution proceeds asynchronously and its results appear in later blocks. BNB Chain says the split keeps consensus from waiting on EVM throughput, while an adaptive execution lag can grow under load and shrink when activity eases.

The network uses an enhanced version of Parlia, BNB Smart Chain’s Proof-of-Staked-Authority consensus, with cross-block BLS votes. Its design also removes the global mempool: transactions go to the current and next block proposer. For developers, that changes transaction handling and monitoring even as the documentation says existing Solidity contracts and standard transaction flows remain compatible.

BNB stays the asset, but fees work differently

The documentation says BNB remains New L1’s native asset; the proposed network does not introduce a separate token. A BNB Smart Chain bridge is in development, but it is not live. The network also adds native account-abstraction transactions, supporting batched calls, passkey signing, delegated keys and gas sponsorship without requiring a bundler or an EntryPoint contract.

One migration detail could affect application costs: New L1 charges against the gas limit a user declares, rather than the gas the EVM actually consumes. A transaction submitted with a need for 70,000 gas but a declared limit of 500,000 would be charged for the declared 500,000, according to BNB Chain’s porting guide. Developers must avoid excessive gas-limit padding.

The devnet has no public endpoint yet

BNB Chain says New L1 currently runs as an internal, multi-validator devnet. Its network name and chain ID remain unsettled, and the documentation lists no public RPC endpoint, faucet or hosted block explorer. “The network is highly unstable and subject to breaking changes,” the BNB Chain documentation says.

The proposed shielded pool would let users transact with sender, recipient and amount hidden while leaving ordinary EVM transactions transparent. But the team’s own documentation says the pool’s circuits are unaudited and its trusted setup came from an external ceremony; it warns users not to treat the feature as safe for real value. The public testnet, mainnet and bridge are still ahead, with no public network endpoint available in the published network details.

Sources

  1. Original source BNB Chain Documentation · page 1 docs.bnbchain.org

Other pages read

  1. BNB Chain Documentation · page 2 docs.bnbchain.org
  2. BNB Chain Documentation · page 3 docs.bnbchain.org
  3. BNB Chain Documentation · page 4 docs.bnbchain.org
  4. BNB Chain Documentation · Async execution docs.bnbchain.org

Related stories

Explore

More articles