$ show bnb-chain/BEPs
This is the official BNB Chain Evolution Proposal (BEP) repository — a governance/specification hub, not a software application. It contains 100+ BEPs and one BNB Application Proposal (BAP-578) that jointly define protocol changes for BNB Smart Chain (BSC), the Beacon Chain, opBNB, and Greenfield. Proposals cover consensus mechanics (fast finality BEP-126, short block intervals BEP-520/BEP-670, consecutive block production BEP-341), EVM semantics adopted from Ethereum EIPs (blob transactions, transient storage, PUSH0, set-code transactions), cryptographic precompiles (BLS12-381, secp256r1, KZG), cross-chain interoperability (BEP-171, BEP-293, BEP-363), staking and governance migration (BEP-294, BEP-297, BNB Chain Fusion BEP-333), and token standards (BEP-2, BEP-20, CAS20 BEP-702).
The LLM identified 3 files worth highlighting for reuse:
A complete, hand-crafted test vector suite for seven BLS12-381 precompile operations (G1/G2 add, mul, multiexp, pairing check, field-to-curve map) including JSON negative/failure cases and expected gas costs. Paired with field_to_curve.md and fast_subgroup_checks.md, which specify the mathematical construction precisely enough to reimplement from scratch. Directly extractable to any EVM chain or cryptographic library validating EIP-2537-style BLS operations.
The meta-proposal (modeled on EIP-1) defining BEP/BAP statuses, numbering rules, the proposal workflow, and the mandatory document skeleton (preamble, abstract, motivation, specification, rationale, backward compatibility, license). Reusable as a governance pattern for any open ecosystem needing structured technical change management with hardfork tracking.
A data-driven analysis of 16M+ BSC blocks quantifying the real impact of a proposed 90M transaction gas limit cap, showing only 0.008% of transactions would be affected. Demonstrates a repeatable pattern for grounding consensus parameter changes in rigorous on-chain evidence rather than assertion.