logo
Documentation
Initializing search
    BNB Chain GitHub
    • Home
    • Announcements
    • BNB Smart Chain
    • New L1 devnet
    • opBNB
    • BNB Greenfield
    • Developer Kit
    • BNB Chain Fusion
    BNB Chain GitHub
    • Home
    • Announcements
    • BNB Smart Chain
    • New L1
      • Overview
        • Network Information
        • Migrating from BSC
        • Quick Guide
        • Transaction Types
        • Transaction Lifecycle
        • Examples
        • JSON-RPC
        • Consensus
        • Async Execution
        • State DB
        • Multi-Lane
        • Pre-confirmation
        • Account Abstraction
        • Privacy
        • Overview
        • System Contracts
      • FAQ
    • opBNB
    • BNB Greenfield
    • Developer Kit
    • BNB Chain Fusion
    1. Home
    2. New L1

    New L1

    New L1 is a high-performance, EVM-compatible Layer 1 built for latency-sensitive on-chain activity: sub-second finality, native account abstraction, transaction pre-confirmation, Multi-Lane reserved capacity, and an on-chain shielded (privacy) pool.

    Status

    New L1 is currently in devnet. The network is highly unstable and subject to breaking changes.

    Overview

    What New L1 is and how it's built

    Get Started

    Run a local devnet and connect over JSON-RPC

    Consensus

    Parlia PoSA with BLS fast finality

    Native Account Abstraction

    Batched calls, session keys, and sponsored gas, with no bundler required

    Transaction Pre-confirmation

    Sub-second, best-effort inclusion signals ahead of finality

    Multi-Lane

    Reserved gas capacity for latency-sensitive transaction classes

    Shielded Pool (Privacy)

    Native, opt-in private transfers via zk proofs

    Governance

    On-chain, token-weighted parameter and validator-set governance

    JSON-RPC Reference

    Standard eth_* methods plus New L1 extensions

    October 22, 2026

    Cookie consent

    We use cookies to recognize your repeated visits and preferences, as well as to measure the effectiveness of our documentation and whether users find what they're searching for. With your consent, you're helping us to make our documentation better.