From fd87c8885a5dd9cf7cf02354b8f61277b99b74d5 Mon Sep 17 00:00:00 2001 From: Danyal Prout Date: Tue, 2 Jun 2026 11:31:24 -0500 Subject: [PATCH] chore: remove bcp pages --- docs/agents.md | 1 - docs/base-chain/specs/bcps/bcp-0000.mdx | 103 ------------------------ docs/base-chain/specs/bcps/index.mdx | 11 --- docs/docs.json | 7 -- docs/llms-full.txt | 2 - docs/llms.txt | 2 - 6 files changed, 126 deletions(-) delete mode 100644 docs/base-chain/specs/bcps/bcp-0000.mdx delete mode 100644 docs/base-chain/specs/bcps/index.mdx diff --git a/docs/agents.md b/docs/agents.md index 7a3369ade..7f959aeca 100644 --- a/docs/agents.md +++ b/docs/agents.md @@ -82,7 +82,6 @@ npx skills add base/base-skills |base-chain/quickstart:base-solana-bridge,connecting-to-base,deploy-on-base,why-base |base-chain/security:avoid-malicious-flags,bug-bounty,report-vulnerability,security-council |base-chain/specs:overview -|base-chain/specs/bcps:bcp-0000,index |base-chain/specs/protocol:batcher,overview |base-chain/specs/protocol/bridging:bridges,deposits,messengers,withdrawals |base-chain/specs/protocol/consensus:derivation,index,p2p,rpc diff --git a/docs/base-chain/specs/bcps/bcp-0000.mdx b/docs/base-chain/specs/bcps/bcp-0000.mdx deleted file mode 100644 index c09191448..000000000 --- a/docs/base-chain/specs/bcps/bcp-0000.mdx +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: "BCP-0000: BCP Process" -description: "BCP-0000 defines the Base Change Proposal process, establishing the template and standards for proposing, reviewing, and accepting protocol changes." ---- - -## Abstract - -BCP-0000 defines the Base Change Proposal (BCP) process — the mechanism by which changes to the Base -Chain protocol are proposed, reviewed, and accepted. A BCP is a design document providing a -complete specification of a proposed change, serving as the source of truth for implementation. - -## Motivation - -Base Chain needs a transparent, structured process for evolving its protocol. Without a formal -process, changes risk being underdocumented, inconsistently reviewed, or difficult to track across -stakeholders. BCPs provide a single canonical artifact per change: a self-contained specification -that captures the what, why, and how, from initial proposal through final acceptance. - ---- - -# Specification - -## BCP Types - -There are two types of BCPs: - -- **Standards Track** — describes a change to the Base Chain protocol itself: execution rules, - consensus, bridging, fault proofs, or other on-chain behavior. Most BCPs are Standards Track. -- **Meta** — describes a change to the BCP process or introduces governance around how the - protocol is evolved. BCP-0000 is a Meta BCP. - -## BCP Statuses - -A BCP moves through the following statuses over its lifetime: - -``` -Draft → Review → Accepted → Final - └→ Rejected - └→ Withdrawn -``` - -| Status | Description | -| ------ | ----------- | -| **Draft** | The BCP is being authored and is not yet ready for formal review. | -| **Review** | The BCP is complete and open for community and core team feedback. | -| **Accepted** | The BCP has been approved and is scheduled for implementation. | -| **Final** | The BCP has been implemented and deployed to mainnet. | -| **Rejected** | The BCP was reviewed and not accepted. | -| **Withdrawn** | The author(s) withdrew the BCP before a decision was reached. | -| **Deprecated** | A previously Final BCP has been superseded by a later BCP. | - -## BCP Numbering - -BCPs are assigned a number at the time of their first Draft commit. Numbers are assigned -sequentially starting from 1 (BCP-0001). The number is permanent and is never reused, even if the -BCP is rejected or withdrawn. BCP-0000 is reserved for this process document. - -## BCP Format - -Each BCP is a Markdown file stored at `docs/specs/pages/bcps/bcp-{NNNN}.md` in the -[base repository](https://github.com/base/base). It must begin with the title as an H1 -heading followed by the body sections below. - -### Required Sections - -**Abstract** — A 2–4 sentence high-level summary of the proposed change. - -**Motivation** — An explanation of the problem this BCP solves and why the proposed approach was -chosen over alternatives. Include links to prerequisite specs or relevant context. - -**Specification** — A complete description of the change: state transitions, data structures, -encodings, interface definitions, and any invariants that must hold. The specification must be -precise enough for an independent engineer to implement and test without inferring details. - -**Invariants** (if applicable) — Explicit invariants that must always hold after the change is -applied, and critical cases the test suite must cover. - -### Optional Sections - -Additional sections (e.g. **Security Considerations**, **Backwards Compatibility**, -**Reference Implementation**) may be added as needed. - -## Process - -1. **Draft** — An author opens a PR to the base repository adding a new BCP file. The PR - description should link to any relevant prior discussion. -2. **Review** — The PR is marked ready for review. Core team members and community stakeholders - review the specification for correctness, completeness, and alignment with Base's design goals. -3. **Accepted / Rejected** — The core team makes a final decision. If accepted, the BCP is merged - and assigned a Final status once the implementation ships to mainnet. If rejected, the BCP is - merged with Rejected status and a brief rationale added to the BCP. -4. **Final** — The BCP is updated to Final status when its implementation is deployed to mainnet. - -## BCP Index - -The [BCPs index page](./index) lists all BCPs with their current status. Authors are -responsible for keeping their BCP's status up to date as it progresses. - -# Invariants - -- Every BCP has a unique, permanent number. -- Every BCP that reaches Final status has a corresponding implementation deployed to mainnet. -- A Deprecated BCP must reference the superseding BCP. diff --git a/docs/base-chain/specs/bcps/index.mdx b/docs/base-chain/specs/bcps/index.mdx deleted file mode 100644 index 93fadb82f..000000000 --- a/docs/base-chain/specs/bcps/index.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: "Base Change Proposals (BCPs)" -description: "Index of Base Chain Proposals (BCPs) — design documents describing proposed changes to the Base Chain protocol." ---- - -BCPs are design documents that describe changes to the Base Chain protocol. Each BCP provides a -complete specification that serves as the source of truth for implementation. - ---- - -- [BCP-0000: BCP Template and Purpose](/base-chain/specs/bcps/bcp-0000) diff --git a/docs/docs.json b/docs/docs.json index b635d0de2..2d43d8395 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -332,13 +332,6 @@ } ] }, - { - "group": "BCPs", - "pages": [ - "base-chain/specs/bcps/index", - "base-chain/specs/bcps/bcp-0000" - ] - }, { "group": "Reference", "pages": [ diff --git a/docs/llms-full.txt b/docs/llms-full.txt index 2f1cc7ed5..fe9652da4 100644 --- a/docs/llms-full.txt +++ b/docs/llms-full.txt @@ -109,7 +109,6 @@ const client = createPublicClient({ chain: base, transport: http() }) ## Base Chain - [Flashblocks Overview](https://docs.base.org/base-chain/flashblocks/overview): Understand the sequencer architecture, block building algorithm, and integration options for Flashblocks on Base. -- [Base Change Proposals (BCPs)](https://docs.base.org/base-chain/specs/bcps/index): Index of Base Chain Proposals (BCPs) — design documents describing proposed changes to the Base Chain protocol. - [Overview](https://docs.base.org/base-chain/specs/overview): Technical specification of the Base Chain protocol, covering block derivation, execution, transaction propagation, and state verification. - [Specification](https://docs.base.org/base-chain/specs/protocol/consensus/index): Specification of the Base rollup node, describing its components and role in L2 block derivation and consensus. - [L2 Execution Engine](https://docs.base.org/base-chain/specs/protocol/execution/index): Specification of the L2 execution engine, detailing EIP-1559 parameters, fee vaults, Engine API usage, and execution layer behavior. @@ -187,7 +186,6 @@ const client = createPublicClient({ chain: base, transport: http() }) - [Bug Bounty](https://docs.base.org/base-chain/security/bug-bounty) - [Reporting Vulnerabilities](https://docs.base.org/base-chain/security/report-vulnerability): The Base procedures for reporting vulnerabilities. - [Security Council for Base](https://docs.base.org/base-chain/security/security-council): This page outlines the purpose, goals, structure, and responsibilities of the Security Council for Base. -- [BCP-0000: BCP Process](https://docs.base.org/base-chain/specs/bcps/bcp-0000): BCP-0000 defines the Base Change Proposal process, establishing the template and standards for proposing, reviewing, and accepting protocol changes. - [Batcher](https://docs.base.org/base-chain/specs/protocol/batcher): Specification of the batcher (batch submitter), the component responsible for posting L2 sequencer data to L1 for data availability. - [Standard Bridges](https://docs.base.org/base-chain/specs/protocol/bridging/bridges): Specification of the standard bridges enabling cross-domain ETH and ERC20 token transfers between L1 and L2 on Base. - [Deposits](https://docs.base.org/base-chain/specs/protocol/bridging/deposits): Specification of the deposit mechanism for Base, detailing how L1 transactions are converted into L2 deposit transactions. diff --git a/docs/llms.txt b/docs/llms.txt index 8838662bf..7b55e59fe 100644 --- a/docs/llms.txt +++ b/docs/llms.txt @@ -21,7 +21,6 @@ ## Base Chain - [Flashblocks Overview](https://docs.base.org/base-chain/flashblocks/overview): Understand the sequencer architecture, block building algorithm, and integration options for Flashblocks on Base. -- [Base Change Proposals (BCPs)](https://docs.base.org/base-chain/specs/bcps/index): Index of Base Chain Proposals (BCPs) — design documents describing proposed changes to the Base Chain protocol. - [Overview](https://docs.base.org/base-chain/specs/overview): Technical specification of the Base Chain protocol, covering block derivation, execution, transaction propagation, and state verification. - [Specification](https://docs.base.org/base-chain/specs/protocol/consensus/index): Specification of the Base rollup node, describing its components and role in L2 block derivation and consensus. - [L2 Execution Engine](https://docs.base.org/base-chain/specs/protocol/execution/index): Specification of the L2 execution engine, detailing EIP-1559 parameters, fee vaults, Engine API usage, and execution layer behavior. @@ -99,7 +98,6 @@ - [Bug Bounty](https://docs.base.org/base-chain/security/bug-bounty) - [Reporting Vulnerabilities](https://docs.base.org/base-chain/security/report-vulnerability): The Base procedures for reporting vulnerabilities. - [Security Council for Base](https://docs.base.org/base-chain/security/security-council): This page outlines the purpose, goals, structure, and responsibilities of the Security Council for Base. -- [BCP-0000: BCP Process](https://docs.base.org/base-chain/specs/bcps/bcp-0000): BCP-0000 defines the Base Change Proposal process, establishing the template and standards for proposing, reviewing, and accepting protocol changes. - [Batcher](https://docs.base.org/base-chain/specs/protocol/batcher): Specification of the batcher (batch submitter), the component responsible for posting L2 sequencer data to L1 for data availability. - [Standard Bridges](https://docs.base.org/base-chain/specs/protocol/bridging/bridges): Specification of the standard bridges enabling cross-domain ETH and ERC20 token transfers between L1 and L2 on Base. - [Deposits](https://docs.base.org/base-chain/specs/protocol/bridging/deposits): Specification of the deposit mechanism for Base, detailing how L1 transactions are converted into L2 deposit transactions.