From 83ce90f8f5f05a16e611aba44e6a4f2118aae372 Mon Sep 17 00:00:00 2001 From: Erhnysr Date: Mon, 6 Apr 2026 22:47:00 +0300 Subject: [PATCH 1/2] docs: add RPC usage clarification note Adds a clarification note about using the correct RPC endpoint when building on Base. --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index d3d19bbbb..52dd475ce 100644 --- a/README.md +++ b/README.md @@ -164,3 +164,6 @@ The core team will review opened PRs. The SLA is 2 weeks, generally on a first-c ## Storybook for UI components See `storybook/README.md` for details on local Storybook and component docs. +## Additional Note + +When building on Base, always ensure that you are using the correct RPC endpoint for the intended network (mainnet or testnet). Misconfiguration can lead to failed transactions or unexpected behavior. From e9ab3e9aee5e11c15276547dc15f98b09f4fc5d1 Mon Sep 17 00:00:00 2001 From: erhan yasar Date: Sat, 11 Apr 2026 20:52:54 +0300 Subject: [PATCH 2/2] fix: replace deprecated docker-compose with docker compose v2 and update stale repo links - Replace all instances of 'docker-compose' with 'docker compose' (Compose v2) in run-a-base-node.mdx, matching the syntax used in the node repo's README - Update stale github.com/base-org/node link to github.com/base/node Docker Compose v1 (docker-compose) was deprecated in July 2023 and removed in Docker Desktop 4.33. The node repository README already uses 'docker compose' (v2 syntax) exclusively, so the docs should match. --- docs/base-chain/node-operators/run-a-base-node.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/base-chain/node-operators/run-a-base-node.mdx b/docs/base-chain/node-operators/run-a-base-node.mdx index 046d47ec0..c241ae917 100644 --- a/docs/base-chain/node-operators/run-a-base-node.mdx +++ b/docs/base-chain/node-operators/run-a-base-node.mdx @@ -3,7 +3,7 @@ title: Run a Node description: A tutorial that teaches how to set up and run a Base Node. --- -This tutorial will walk you through setting up your own [Base Node](https://github.com/base-org/node). +This tutorial will walk you through setting up your own [Base Node](https://github.com/base/node). ## Objectives @@ -66,9 +66,9 @@ You'll need your own L1 RPC URL. This can be one that you run yourself, or via a ## Running a Node -1. Clone the [repo](https://github.com/base-org/node). -2. Ensure you have an Ethereum L1 full node RPC available (not Base), and set `OP_NODE_L1_ETH_RPC` & `OP_NODE_L1_BEACON` (in the `.env.*` file if using `docker-compose`). If running your own L1 node, it needs to be synced before Base will be able to fully sync. -3. Uncomment the line relevant to your network (`.env.sepolia`, or `.env.mainnet`) under the 2 `env_file` keys in `docker-compose.yml`. +1. Clone the [repo](https://github.com/base/node). +2. Ensure you have an Ethereum L1 full node RPC available (not Base), and set `OP_NODE_L1_ETH_RPC` & `OP_NODE_L1_BEACON` (in the `.env.*` file if using `docker compose`). If running your own L1 node, it needs to be synced before Base will be able to fully sync. +3. Uncomment the line relevant to your network (`.env.sepolia`, or `.env.mainnet`) under the 2 `env_file` keys in `docker-compose.yml` (Docker Compose v2). 4. Run `docker compose up`. Confirm you get a response from: ```bash Terminal @@ -112,7 +112,7 @@ Once your node is synced, you can enable Flashblocks to serve 200ms preconfirmat To enable Flashblocks, start your node with the following environment variables: ```sh -NODE_TYPE=base CLIENT=reth RETH_FB_WEBSOCKET_URL="wss://mainnet.flashblocks.base.org/ws" docker-compose up +NODE_TYPE=base CLIENT=reth RETH_FB_WEBSOCKET_URL="wss://mainnet.flashblocks.base.org/ws" docker compose up ``` | Variable | Description | Values |