Skip to content

docs: rename Protocol Overview to Base Protocol, merge into single page #1867

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mindapivessa wants to merge 2 commits into
base: master
Choose a base branch
from
Open

docs: rename Protocol Overview to Base Protocol, merge into single page #1867

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9c85279
docs: rename Protocol Overview to Base Protocol, merge into single page
mindapivessa Aug 28, 2026
72f808b
docs: nest protocol specs under Base Protocol group, split design goals
mindapivessa Aug 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/.mintignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,3 +8,4 @@ tone_of_voice.mdx
base-chain/network-information/bridging-and-withdrawals.mdx
base-chain/network-information/network-faucets.mdx
base-chain/quickstart/connecting-to-base.mdx
base-chain/specs/protocol/overview.mdx
4 changes: 2 additions & 2 deletions docs/base-chain/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,8 @@ Technical specifications for how Base works at the chain level, organized by top
<Card title="Flashblocks" icon="bolt" href="/base-chain/flashblocks/faq">
Sub-second block building, WebSocket data, and RPC usage.
</Card>
<Card title="Protocol Overview" icon="diagram-project" href="/base-chain/specs/protocol/overview">
Rollup architecture, core components, and user flows.
<Card title="Base Protocol" icon="diagram-project" href="/base-chain/specs/overview">
Design goals, rollup architecture, and core user flows.
</Card>
<Card title="Batcher" icon="layer-group" href="/base-chain/specs/protocol/batcher">
Posting L2 sequencer data to L1 for data availability.
Expand Down
23 changes: 23 additions & 0 deletions docs/base-chain/specs/design-goals.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
title: "Design Goals"
description: "Design philosophy and lineage of the Base Chain protocol specification."
---

## Design Goals

Our aim is to design a protocol specification that is:

- **Opinionated:** Simplicity through deliberate design choices. We identify the best solution and
commit to it.
- **Maximally Simple:** By focusing on just what Base needs, we radically simplify the stack. The
protocol spec and codebase should be understandable by a single developer.
- **Fast Cycles:** We ship upgrades frequently rather than batching risk into infrequent large ones.
We target six smaller, tightly scoped hard forks per year on a regular cadence, with fortnightly
releases.
- **Ethereum Aligned:** Base wins when Ethereum wins. We accelerate deployment of high-impact
changes ahead of L1 to provide data that informs the Ethereum roadmap.

## Lineage

Base Chain inherits Ethereum's EVM semantics, transaction rules, and L1-anchored security. It was
originally built on the [OP Stack](https://specs.optimism.io). After the Jovian Hardfork, Base Chain follows this specification.
Loading
Loading