Layer 1 blockchain
BNB Smart Chain ticker BNB
Summary
Proof of Staked Authority in the Parlia engine of a go-ethereum fork. BNB holders stake or delegate to validators; a daily election after 00:00 UTC keeps the 45 highest-staked (21 'Cabinet', 24 'Candidates'). Each epoch 21 of them (18 Cabinet, 3 Candidates) take turns producing blocks in a proof-of-authority rotation. Blocks have been 0.45 seconds apart since the Fermi hard fork on 14 January 2026. A fast-finality layer (BEP-126) has validators sign BLS votes: a block becomes final once it and its direct child each gather votes from at least two-thirds of the set, normally within two blocks. Rewards come from transaction fees rather than new issuance. Outside block builders assemble almost all blocks and the in-turn validator seals them; BNB Chain reported about 0.1% built locally in the days after the Pasteur hard fork. 123456911
Design
- System
- Layer 1 blockchainBNB Smart Chain (BSC, chain ID 56) is an EVM-compatible chain with its own elected validator set and consensus. It does not post data to or settle on Ethereum and is not pegged to another chain's security. Since BNB Beacon Chain's final sunset hard fork on 19 November 2024, BSC is the main BNB Chain ledger. opBNB (a rollup on BSC) and BNB Greenfield (a storage chain) are separate networks and are not described by these cells. The package's layer-1 class is kept.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- The 21 validators chosen for the epoch take turns; a validator must self-delegate at least 2,000 BNB. BNB Chain's validator page (updated July 2025) lists a 200 BNB slash and 30-day jail for double signing or conflicting finality votes, and a 10 BNB slash and 2-day jail for missing 150 or more blocks in 24 hours. BNB Chain reported 33 block builders active in the three-day window ending 1 September 2026.
- Fork choice
- Parlia prefers the branch with the higher justified block from fast-finality votes; if both branches have the same justified block it falls back to greater accumulated difficulty. If fewer than two-thirds of validators vote, finality stalls and the chain keeps running under that heaviest-chain rule, so recent blocks can still be reorganized until votes resume.
Qualifications
- Finality · Contested. BNB Chain documents finality within two blocks once two-thirds of validators vote, with slashing for conflicting votes. A USENIX Security 2025 paper describes three attacks that delay finality or stop it progressing, and its authors say BNB Chain's team acknowledged them. An August 2026 public report in the client repository claims that, during the daily validator-set switch, two branches could finalize conflicting blocks with no slashable offence; the report had been assigned but showed no maintainer reply on 2026-09-27. When votes fall short, blocks keep coming without finality.
- Decentralization · Partial. Consensus participation is capped at 45 elected validators, 21 producing per epoch, with a 2,000 BNB self-delegation minimum. Delegation is open to any BNB holder, but operator identities and stake concentration were not verified in this review.
- Rollup security model · Not applicable. BSC runs the same virtual machine, account format and tooling as Ethereum, but it posts no data to, and does not settle on, Ethereum, so rollup security and data-availability models do not apply.
- Companion chains · Not applicable. BNB Beacon Chain stopped producing blocks after its final sunset hard fork (19 November 2024) and its cross-chain link to BSC is closed. BNB Greenfield is a separate storage chain and opBNB a separate rollup; neither is described by the BSC cells.
Tradeoffs
- Emphasizes
- Scalability
- Gives up
- Decentralization of block production and validation: 45 elected validators, of which 21 take turns each epoch, and node hardware well beyond a typical home computer. In October 2022, after a bridge exploit, BNB Chain contacted its 26 active validators one by one and they paused the chain together; BNB Chain says organizing that response took about five hours. It shows that a small set can halt the chain. Finality also depends on two-thirds of that small set voting honestly and on time.Security is not listed as a design emphasis because it rests on an elected set plus a finality overlay that peer-reviewed research (USENIX Security 2025) and an open August 2026 report have questioned; BNB Chain's own 2026 roadmap frames its priorities as speed and throughput. Readers who count fast finality with slashable votes as a security emphasis may reasonably disagree.
- Full node at home
- Demanding 678BNB Chain's node guide (dated July 2024) lists a 16-core CPU for every node type: a fast node with 32 GB RAM and a 2 TB SSD, a full node with 64 GB RAM and a 3 TB SSD, and an archive node with 128 GB RAM and a 10 TB SSD (NVMe recommended), each with at least 5 MB/s of bandwidth; the client README adds 8k IOPS. These figures predate 0.45-second blocks, and the docs advise starting from a snapshot rather than syncing from genesis.
- Throughput claims
- Lab benchmark: 5,200 tx/s 12Controlled benchmark; not observed network behavior.BNB Chain states about 400 million gas per second alongside this figure, after H1 2026 client optimizations (baseline stated as about 2,800 tx/s).H1 2026 optimization results reported in a post dated 2026-07-08Vendor-reported benchmark with no published workload, transaction mix, hardware or method; not observed mainnet load. Does not show whether full nodes on the published minimum hardware keep up, and ignores state growth and propagation across a wide node set.
- Lab benchmark: 2,324 tx/s 10Controlled benchmark; not observed network behavior.Before-and-after figure, not a range: BNB Chain says QA test network throughput rose from 1,237 to 2,324 tx/s at the same 450 ms interval with the Pasteur change.Pre-activation QA test network benchmark cited in the Pasteur announcement dated 2026-08-14Testnet benchmark of one change; the transaction mix and hardware were not stated. Not an observed mainnet rate and not comparable with other chains' figures; ignores state growth and spam or decoy load.
- Theoretical peak: 100,000 tx/s 12Theoretical peak; not comparable across chains or with observed load.Stated as '100K+' for a next-generation architecture, not for BSC as it runs today.Design target; the roadmap plans a testnet by the end of 2026 and mainnet in early 2027A target for a system that was not on a public testnet at review time; not comparable. No hardware, bandwidth, state-growth or node-count assumptions were published.
Scaling layers
- opBNB · Rollup, mainnet 161718192031
OP Stack (Bedrock) rollup anchored to BSC. BNB Chain's opBNB FAQ (2024) says the opBNB team runs the sequencer, describes it as a centralized component, and says individual users cannot yet run validator or aggregator nodes. Withdrawals through the official bridge wait a 7-day challenge window. A zero-knowledge fault-proof design was a 2024 proof of concept; whether permissionless fault proofs are live in 2026 was not verified.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | EVM contracts could implement hash- and time-locked swaps, but no deployed trust-minimized swap mechanism on BSC was reviewed. |
| Authenticated data publication | Built into the protocolLimited scope | Blob transactions (BEP-336, enabled): a transaction records a versioned hash of each blob's KZG commitment, blocks travel with their blobs, and nodes check that each commitment matches its hash and, under a KZG proof, its blob, so full nodes hold the data for readers to fetch and check. Limited: nodes are required to keep blobs for only about 18 days, and there is no way to find updates. BNB Greenfield, a separate storage chain whose buckets and objects can be mirrored to BSC through a bridge secured by a validator multisig, was not assessed against this row. 1521 |
| Light clients | Built into the protocolLimited scope | Fast-finality votes (BEP-126): consensus produces what a light client checks, since BSC validators sign BLS votes on blocks, and Hyperbridge documents an on-chain light client that checks those votes for its own bridging. Limited: no BNB Chain-maintained light client for wallets was found, and a community wishlist issue opened on 26 August 2026 says BSC wallets and apps mostly rely on centralized RPC providers; the community client it offers is, by its author's account, not audited. 2223 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to BSC was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | BSC runs the EVM from a go-ethereum fork, so spend conditions are written as smart contracts. 16 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; Safe's deployment registry lists its version 1.4.1 smart-account contracts on BNB Smart Chain (chain ID 56). A Safe account needs a set number of owners to approve each spend, lets owners be replaced and can add modules, including one that restores access under set conditions, but no cited source shows a delay or recovery module deployed there, and an owner threshold alone meets neither part of this row. Whether Safe's app supports BNB Smart Chain was not checked. 3940 |
| Rollups | Ecosystem software (publisher not distinguished) Earlier definition | opBNB is an OP Stack rollup anchored to BSC and developed by BNB Chain, whose team runs its sequencer; it is a separate network, not part of the BSC protocol. See the scaling options in this profile. 1617 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Established in the ecosystemPancakeSwap | PancakeSwap documents itself as an automated market maker and lists BNB Chain first among the chains it runs on. Liquidity depth was not measured and other venues were not reviewed. 2425 |
| Issuer-native stablecoins | Established in the ecosystemUSD1 (World Liberty Financial, custodied by BitGo) | The USD1 issuer documentation lists a BSC contract (0x8d0d000ee44948fc98c9b98a4fa4921476f08b0d); here native means an issuer-listed contract on BSC, not a protocol asset. BNB Chain's September 2026 fee campaign names USD1 among the stablecoins it sponsors; USD1 supply on BSC was not measured. Tether's network list gives only its gold token, not USDT, for BSC, and Circle's USDC list does not include BSC, so neither issuer lists the USDT or USDC tokens used on BSC as its own deployment. 2026272829 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on BSC were not reviewed. |
| Bridges | Established in the ecosystemopBNB Bridge (BNB Chain), Greenfield Bridge (BNB Chain), BNB Chain Bridge route aggregator (Stargate, Celer, deBridge, Meson, LayerZero, Mayan), Chainlink CCIP (used by USD1), Circle CCTP (USYC only) | BNB Chain runs bridges to its own opBNB and Greenfield networks and an aggregator that shows third-party routes into and out of BSC; it says it does not operate those routes. Circle's CCTP lists BSC for USYC only, not USDC. The cross-chain link to the retired Beacon Chain is closed. Risk: Each third-party route carries its own trust model, which this review did not assess. In October 2022 a forged proof against the native bridge between Beacon Chain and BSC released 2 million BNB, and BNB Chain had to contact validators one by one to pause the chain, which it says took about five hours to organize. opBNB withdrawals wait 7 days and depend on a proof arrangement whose 2026 status was not verified; the Greenfield bridge relies on a validator multisig. 1821263031323334 |
| Block explorers | Established in the ecosystemBscScan, BSCTrace (NodeReal) | BNB Chain's quick guide lists BscScan and NodeReal's BSCTrace. Explorer indexes are provider data, not canonical consensus; other explorers were not reviewed. 35 |
| Hardware wallets | Established in the ecosystemLedger, Trezor | See custody rows: Ledger's and Trezor's own pages list BNB and BEP-20 tokens on BNB Smart Chain in their wallet apps. 363738 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Yes | Can: Manage and send BNB on BNB Smart Chain in Ledger Wallet (formerly Ledger Live), approving transactions on the device in its Binance Smart Chain app Can: Manage BEP-20 tokens on BNB Smart Chain in the same app Cannot: Manage assets from the retired BNB Beacon Chain in Ledger Wallet; Ledger's 2021 announcement limited Ledger Live to BNB Smart ChainLedger's BEP-20 page still uses the older name Binance Smart Chain and is undated; its support articles returned no content for this review, so which BEP-20 tokens Ledger Wallet displays today was not verified. 3637 |
| Trezor | Native supportSame as native: Yes | Can: Use BNB Smart Chain in Trezor Suite (version 24.11.2 or later) on Safe 5, Safe 3, Model T or Model One with the minimum firmware versions Trezor lists Can: Hold any BEP-20 token; tokens Suite does not recognize show as unknown and can be used by entering the contract address Cannot: Use other Binance-related chains; Trezor says its support is specific to BNB Smart ChainTrezor's page warns that malicious smart contracts are common on BNB Smart Chain. Staking from Trezor Suite was not mentioned and was not verified. 38 |
Public data
iKnow Blockchain has no public-data lookups for BNB Smart Chain yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
BNB Chain announced BSC Payment Lane for Q4 2026
BNB Chain described a planned reserved-blockspace floor for payments: native BNB transfers, USDT and USDC transfers and governance-approved tokens would get a minimum share of block gas that grows during congestion and shrinks as demand falls. Priority fees would still order transactions, and validators are to vote on the reserve size and thresholds before launch.
- Proposal:announced design; parameters pending a validator vote
- Implementation:not observed
- Release:planned for Q4 2026
- Activation:not active at review
Source: BNB Chain Blog — BSC Payment Lane: Reserved Blockspace That Keeps Payments Moving (external site)
-
Pasteur hard fork scheduled and then activated on BSC mainnet
BNB Chain announced the Pasteur hard fork for 25 August 2026 at 02:30 UTC with client v1.7.7. It lets builders hand validators pre-executed blocks so validators skip a second execution pass (BEP-675), rejects duplicate validators in bridge signature checks (BEP-682) and makes rotated validator keys lose privileges while still facing pending slashes (BEP-695). A 14 September post confirmed it went live on 25 August.
- Proposal:BEP-673 meta proposal with BEP-675, BEP-682 and BEP-695
- Implementation:shipped in client v1.7.7
- Release:mandatory mainnet release
- Activation:activated on mainnet 2026-08-25 02:30 UTC
Sources: BNB Chain Blog — Pasteur Hardfork Arrives on BSC Mainnet on August 25 (external site) · BNB Chain Docs — Pasteur Upgrade of BSC (external site) · BNB Chain (GitHub) — bsc v1.7.7 (Pasteur hardfork) (external site) · BNB Chain Blog — Post-Pasteur Hard Fork: BSC Packs 28% More Gas Per Block With More Scale Ahead (external site)
-
Osaka/Mendel hard fork announced for 28 April 2026
BNB Chain announced the Osaka/Mendel hard fork, nine BEPs combining six Ethereum improvements with BNB Chain changes. It caps gas per transaction at 16,777,216, caps block size, adds a count-leading-zeros opcode, adjusts some gas costs, limits blob transactions, speeds fast-finality voting with an in-memory vote pool and adds an eth_config RPC method. The docs mark it enabled on mainnet from 28 April 2026 at 02:30 UTC.
- Proposal:BEP-658 meta proposal including BEP-652
- Implementation:shipped in client v1.7.2
- Release:mandatory mainnet release
- Activation:enabled on mainnet 2026-04-28 02:30 UTC
Sources: BNB Chain Blog — Osaka/Mendel Hard Fork: Strengthening BNB Chain After Sub-Second Speed Gains (external site) · BNB Chain Docs — Mendel Upgrade of BSC (external site) · BNB Chain (GitHub) — bsc v1.7.2 (Osaka/Mendel hardfork) (external site) · BNB Chain Blog — BNB Chain H2 2026 Tech Roadmap: Doubling Down on Speed (external site)
-
Fermi hard fork announced, cutting BSC block time to 0.45 seconds
BNB Chain announced the Fermi hard fork for 14 January 2026 at 02:30 UTC with client v1.6.4. It shortened the block interval from 0.75 to 0.45 seconds and bundled extended fast-finality voting rules, block-level access lists, incremental snapshots and an EVM execution optimization.
- Proposal:BEP-590, BEP-592, BEP-593, BEP-610 and BEP-619
- Implementation:shipped in client v1.6.4 with a v1.6.5 follow-up
- Release:mandatory mainnet release
- Activation:activated on mainnet 2026-01-14 02:30 UTC; 0.45-second blocks described as current in later sources
Sources: BNB Chain Blog — Fermi Hard Fork Accelerates BSC to 0.45-Second Block Times (external site) · BNB Chain Docs — Fermi Hardfork (BSC) (external site) · BNB Chain Blog — Osaka/Mendel Hard Fork: Strengthening BNB Chain After Sub-Second Speed Gains (external site) · BNB Chain Docs — Introduction - BSC Develop (external site)
Topics your AI can explain
Your AI can explain these topics for BNB Smart Chain through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Operator identities and stake concentration of the 45 elected validators were not verified; BscScan's validator page could not be read in this review.
- Slash amounts and jail periods come from a validator page last updated July 2025, before 0.45-second blocks; whether the downtime threshold still applies unchanged, and the undelegation waiting period, were not verified.
- The share of fees burned today was not verified; the burn rule specified an initial 10% that governance can change.
- Node hardware guidance is dated July 2024 (client README: December 2023) and predates 0.45-second blocks; current chain size and bandwidth needs were not measured.
- Whether later upgrades (for example the extended voting rules shipped with Fermi) fix the finality attacks in the USENIX Security 2025 paper, or the August 2026 public report of conflicting finalization, was not verified; the report had been assigned but showed no maintainer reply.
- Whether opBNB fault proofs are live and open to anyone in 2026 was not verified; the reviewed opBNB FAQ and proof-of-concept post date from 2024.
- Some official BNB Chain pages are stale: the BSC product page still shows 3-second blocks and an upcoming Plato upgrade, and the introduction page still describes Beacon Chain transfers. This profile relies on dated hard-fork posts and docs instead.
- Who issues the widely used USDT and USDC tokens on BSC was not confirmed from a primary source; Tether and Circle do not list their own issuance on BSC.
- Whether USD1 supply on BSC is minted there directly or moved in over Chainlink CCIP was not confirmed from the issuer; FDUSD and other stablecoins were not verified from their issuers.
- Ledger's BNB Chain support articles returned no content; the device app name comes from Ledger's undated BEP-20 page, and which BEP-20 tokens Ledger Wallet displays today was not verified.
- The length of the October 2022 chain pause was not found in BNB Chain's posts; they say only that organizing the coordinated pause took about five hours.
- Payment or state channels and algorithmic stablecoins on BSC were not reviewed. Garden, a third-party hash-locked swap service, lists BNB Chain as a live chain; its contracts on BSC were not reviewed, so the swap row is not assessed yet.
- The third-party bridge routes (Stargate, Celer, deBridge, Meson, LayerZero, Mayan) and Chainlink CCIP were not reviewed for trust model or current status.
- All throughput figures are BNB Chain's own benchmark or target numbers without a published method; no observed mainnet rate was classified.
- BSC Payment Lane, a reserved-blockspace design for payments, is announced for the fourth quarter of 2026 and awaits a validator vote on its parameters; it is not described as live.
- How much data is published through blob transactions on BSC, and by whom, was not measured; the roughly 18-day blob retention comes from BEP-336. The BNB Beacon Chain final-sunset date comes from BNB Chain's announcement (docs.bnbchain.org/announce/final-sunset-bc-mainnet), which this profile no longer lists as a source because of its 40-source limit.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Introduction - BSC Develop (external site)
- BSC Validator Overview (external site)
- Staking Overview (external site)
- Slashing Overview (external site)
- BEP-126: Introduce Fast Finality Mechanism (external site)
- bnb-chain/bsc (external site)
- Run a Full Node on BNB Smart Chain (external site)
- Node Best Practices (external site)
- Fermi Hard Fork Accelerates BSC to 0.45-Second Block Times (external site)
- Pasteur Hardfork Arrives on BSC Mainnet on August 25 (external site)
- Post-Pasteur Hard Fork: BSC Packs 28% More Gas Per Block With More Scale Ahead (external site)
- BNB Chain H2 2026 Tech Roadmap: Doubling Down on Speed (external site)
- Does Finality Gadget Finalize Your Block? A Case Study of Binance Consensus (USENIX Security 2025) (external site)
- Safety issue in Binance Consensus (issue #3800, opened 2026-08-23) (external site)
- BEP-336: Implement EIP-4844: Shard Blob Transactions (external site)
- opBNB (external site)
- Protocol FAQs - opBNB (external site)
- Withdrawal - opBNB (external site)
- Zk fault proof for opBNB (external site)
- 0 Fee Transactions for USDC, USD1 & U Extended until September 30! (external site)
- Cross-Chain Programmability - BNB Greenfield (external site)
- Wishlist: Parlia light client / trust-minimized local JSON-RPC for wallets (issue #132) (external site)
- Parlia (external site)
- PancakeSwap documentation (external site)
- PancakeSwap Exchange (external site)
- Contract Addresses - USD1 (external site)
- USD1 (external site)
- Supported Protocols (external site)
- USDC contract addresses (external site)
- CCTP supported blockchains (external site)
- BNB Chain Bridge (external site)
- BNB Chain Bridge - Cross-Chain Guide (external site)
- BNB Chain Ecosystem Update (7 October 2022) (external site)
- BNB Chain: A Decentralized Response (11 October 2022) (external site)
- BSC Quick Guide (external site)
- BEP20 Wallet (external site)
- Ledger now supports Binance Smart Chain (2021-08-13) (external site)
- Managing BNB Smart Chain (BSC) & BEP-20 Tokens in Trezor Suite (external site)
- SafeL2 v1.4.1 deployments by chain ID (safe-deployments registry) (external site)
- How Safe Smart Accounts work (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding