README
BEPs
BEP stands for BNB Evolution Proposal. Each BEP will be a proposal document providing information to the BNB Chain ecosystem and community.
Here is the list of subjects of BEPs:
| Number | Title | Type | Status |
|---|---|---|---|
| BEP-1 | Purpose and Guidelines of BEP | Process | Living |
| BEP-2 | Tokens on BNB Beacon Chain | Standards | Enabled |
| BEP-3 | HTLC and Atomic Peg | Standards | Enabled |
| BEP-6 | Delist Trading Pairs on BNB Beacon Chain | Standards | Enabled |
| BEP-8 | Mini-BEP2 Tokens | Standards | Enabled |
| BEP-9 | Time Locking of Tokens on BNB Beacon Chain | Standards | Enabled |
| BEP-10 | Registered Types for Transaction Source | Standards | Enabled |
| BEP-12 | Introduce Customized Scripts and Transfer Memo Validation | Standards | Enabled |
| BEP-18 | State sync enhancement | Standards | Enabled |
| BEP-19 | Introduce Maker and Taker for Match Engine | Standards | Enabled |
| BEP-20 | Tokens on BNB Smart Chain | Standards | Enabled |
| BEP-67 | Price-based Order | Standards | Enabled |
| BEP-70 | List and Trade BUSD Pairs | Standards | Enabled |
| BEP-82 | Token Ownership Changes | Standards | Enabled |
| BEP-84 | Mirror BEP20 to BNB Beacon Chain | Standards | Enabled |
| BEP-86 | Dynamic Extra Incentive For BSC Relayers | Standards | Enabled |
| BEP-87 | Token Symbol Minimum Length Change | Standards | Enabled |
| BEP-89 | Visual Fork of BNB Smart Chain | Standards | Enabled |
| BEP-91 | Increase Block Gas Ceiling for BNB Smart Chain | Standards | Enabled |
| BEP-95 | Introduce Real-Time Burning Mechanism | Standards | Enabled |
| BEP-126 | Introduce Fast Finality Mechanism | Standards | Enabled |
| BEP-127 | Temporary Maintenance Mode for Validators | Standards | Enabled |
| BEP-128 | Improvement on BNB Smart Chain Staking Reward Distribution | Standards | Enabled |
| BEP-131 | Introduce candidate validators onto BNB Smart Chain | Standards | Enabled |
| BEP-151 | Decommission Decentralized Exchange on BNB Beacon Chain | Standards | Enabled |
| BEP-153 | Introduce native staking onto BNB Smart Chain | Standards | Enabled |
| BEP-159 | Introduce A New Staking Mechanism on BNB Beacon Chain | Standards | Draft |
| BEP-171 | Security Enhancement for Cross-Chain Module | Standards | Enabled |
| BEP-172 | Network Stability Enhancement On Slash Occur | Standards | Enabled |
| BEP-173 | Introduce Text Governance Proposal for BNB Smart Chain | Standards | Enabled |
| BEP-174 | Cross Chain Relayer Management | Standards | Enabled |
| BEP-188 | Early Broadcast Mature Block For In-Turn Validators | Standards | Withdrawn |
| BEP-194 | Node Discovery ENR filtering | Standards | Draft |
| BEP-206 | Hybrid Mode State Expiry | Standards | Stagnant |
| BEP-216 | Implement EIP 3855 PUSH0 instruction | Standards | Enabled |
| BEP-217 | Implement EIP3860 Limit and meter initcode | Standards | Enabled |
| BEP-221 | CometBFT Light Block Validation | Standards | Draft |
| BEP-225 | Implement EIP2565 ModExp Gas Cost | Standards | Enabled |
| BEP-226 | Enable EIP-1559 with base fee of 0 | Standards | Enabled |
| BEP-227 | Add BASEFEE opcode | Standards | Enabled |
| BEP-228 | Prevent deploying contracts starting with 0xEF | Standards | Enabled |
| BEP-229 | Implement EIP-2718 Typed Transaction Envelope | Standards | Enabled |
| BEP-230 | Implement EIP-2929 Gas cost increases for state access opcodes | Standards | Enabled |
| BEP-231 | Implement EIP-2930: Optional access lists | Standards | Enabled |
| BEP-255 | Beacon Chain Asset Reconciliation for Security Enhancement | Standards | Enabled |
| BEP-293 | Greenfield Link to opBNB | Standards | Draft |
| BEP-294 | BSC Native Staking after BC Fusion | Standards | Enabled |
| BEP-297 | BSC Native Governance Module | Standards | Enabled |
| BEP-299 | Token Migration after BC Fusion | Standards | Enabled |
| BEP-311 | Implement EIP-3651 Warm COINBASE | Standards | Enabled |
| BEP-312 | Announce EIP-6049 Deprecate SELFDESTRUCT | Standards | Enabled |
| BEP-319 | Optimize the incentive mechanism of the Fast Finality feature | Standards | Enabled |
| BEP-322 | Builder API Specification for BNB Smart Chain | Standards | Enabled |
| BEP-323 | Bundle Format for Greenfield | Standards | Enabled |
| BEP-333 | BNB Chain Fusion | Standards | Enabled |
| BEP-334 | Greenfield CrossChain Permission Module | Standards | Enabled |
| BEP-335 | Greenfield Simplify Storage Provider Exit | Standards | Enabled |
| BEP-336 | Implement EIP-4844: Shard Blob Transactions | Standards | Enabled |
| BEP-341 | Validators can produce consecutive blocks | Standards | Enabled |
| BEP-342 | Implement EIP-5656: MCOPY | Standards | Enabled |
| BEP-343 | Implement EIP-1153: Transient storage opcodes | Standards | Enabled |
| BEP-344 | Implement EIP-6780: SELFDESTRUCT only in same transaction | Standards | Enabled |
| BEP-345 | Implement EIP-7516: BLOBBASEFEE opcode | Standards | Enabled |
| BEP-346 | Streamline off-chain authentication on Greenfield | Standards | Enabled |
| BEP-362 | Greenfield Storage Fee Paymaster | Standards | Enabled |
| BEP-364 | Primary Storage Provider acts as the upload agent for object creation and update on Greenfield | Standards | Enabled |
| BEP-366 | PGreenfield Atomic Object Update | Standards | Candidate |
| BEP-402 | Complete Missing Fields in Block Header to Generate Signature | Standards | Enabled |
| BEP-404 | Clear Miner History when Switching Validator Set | Standards | Enabled |
| BEP-410 | Add Agent for Validators | Standards | Enabled |
| BEP-414 | EOA based Paymaster API Spec | Standards | Enabled |
| BEP-439 | Implement EIP-2537: Precompile for BLS12-381 curve operations | Standards | Enabled |
| BEP-440 | Implement EIP-2935: Serve historical block hashes from state | Standards | Enabled |
| BEP-441 | Implement EIP-7702: Set EOA account code | Standards | Enabled |
| BEP-466 | Make the block header format compatible with EIP-7685 | Standards | Enabled |
| BEP-496 | Implement EIP-7623: Increase calldata cost | Standards | Enabled |
| BEP-520 | Short Block Interval Phase One: 1.5 seconds | Standards | Enabled |
| BEP-524 | Short Block Interval Phase Two: 0.75 seconds | Standards | Enabled |
| BEP-563 | Enhanced Validator Network | Standards | Enabled |
| BEP-564 | bsc/2 - New Block Fetching Messages | Standards | Enabled |
| BEP-590 | Extended Voting Rules for Fast Finality Stability | Standards | Enabled |
| BEP-592 | Non-Consensus Based Block-Level Access List | Standards | Candidate |
| BEP-593 | Incremental Snapshot | Standards | Enabled |
| BEP-594 | L2 Fast Withdrawal by TEE | Standards | Draft |
| BEP-610 | Implement EVM Super Instruction | Standards | Candidate |
| BEP-619 | Short Block Interval Phase Three: 0.45 Seconds | Standards | Enabled |
| BEP-648 | Enhanced Fast Finality via In-Memory Voting Pool | Standards | Enabled |
| BEP-651 | Implement EIP-7823 Set upper bounds for MODEXP | Standards | Enabled |
| BEP-652 | Implement EIP-7825 Transaction Gas Limit Cap | Standards | Enabled |
| BEP-653 | Implement EIP-7883 ModExp Gas Cost Increase | Standards | Enabled |
| BEP-654 | Implement EIP-7939 Count Leading Zeros (CLZ) Opcode | Standards | Enabled |
| BEP-655 | Implement EIP-7934 RLP Execution Block Size Limit | Standards | Enabled |
| BEP-656 | Implement EIP-7910: eth_config JSON-RPC Method | Standards | Enabled |
| BEP-657 | Limit Blob Transaction Inclusion by Block Number | Standards | Enabled |
| BEP-658 | Hardfork Meta-Osaka/Mendel | Information | Enabled |
| BEP-659 | Implement EIP-7951 Precompile for secp256r1 Curve Support | Standards | Enabled |
| BEP-673 | Hardfork Meta-Pasteur | Information | Draft |
| BEP-675 | Builder-Proposed Block with Validator Blind Signing | Standards | Draft |
| BEP-677 | Implement EIP-8056 Scaled UI Amount | Standards | Draft |
| BEP-682 | Reject Duplicate Validators in CometBFT Light Block Validation | Standards | Draft |
| BEP-695 | Staking and Governance Security Hardening | Standards | Draft |
| BEP-706 | Millisecond-Precision Block Timestamp Precompile | Standards | Draft |
BAPs
BAP (BNB Application Proposal) defines standards for application layer interactions on BNB Chain. Unlike BEPs which govern core protocol changes, BAPs focus on establishing conventions and interfaces for how applications communicate and interact with each other within the BNB Chain ecosystem.
The process for submitting and managing BAPs follows the standardized workflow outlined in BEP-1: Purpose and Guidelines. BAP numbers are assigned based on the PR number, ensuring no overlap with BEP numbers.
Here is the list of subjects of BAPs:
| Number | Title | Type | Status |
|---|---|---|---|
| BAP-578 | BAP-578: Non-Fungible Agent (NFA) Token Standard | Application | Draft |
BNB Chain Upgrades
BNB Chain Upgrades(Mainnet): History & Forecast
BNB Chain Upgrades(Testnet): History & Forecast
How To Contribute
If you have an idea and want to make it a BEP/BAP, you may refer BEP-1