Skip to content

chore: add base v1 migration docs#1278

Draft
danyalprout wants to merge 1 commit intomasterfrom
danyal/migration-docs
Draft

chore: add base v1 migration docs#1278
danyalprout wants to merge 1 commit intomasterfrom
danyal/migration-docs

Conversation

@danyalprout
Copy link
Copy Markdown
Contributor

What changed? Why?
Setup a docs page for node operators and the V1 migration. TODO: Update binary links to v0.7.0 when released.

Notes to reviewers

How has it been tested?
Locally

@mintlify
Copy link
Copy Markdown

mintlify bot commented Apr 7, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
base 🟢 Ready View Preview Apr 7, 2026, 4:21 PM

@cb-heimdall
Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

---

<Warning>
Base V1 is an upgrade that introduces Osaka features on Base and TEE/ZK proof systems. It requires migrating to Base-native clients.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on the Specs summary, confirming that this Fusaka and not Osaka?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fusaka = Fulu (consensus layer) and Osaka (execution layer)

Since we only inherit ethereum execution, it's only the Osaka part of "Fusaka" that applies to Base.


Replace `op-node` with `base-consensus` by updating your environment variables.

1. Set `USE_BASE_CONSENSUS=true` in your `.env` file.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is USE_BASE_CONSENSUS defined in this repo? I thought that was just internal to our infra.


### Environment Variable Mapping

If you use [base/node](https://github.com/base/node), most variables are already set in `.env.mainnet` and `.env.sepolia`. If you build from [base/base](https://github.com/base/base), use the table below to map your `op-node` environment variables to `base-consensus`. Most are optional. Run `base-consensus node --help` for the full list.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should specify which env variables (or cli flags) are required for validator nodes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants