From 3debf63c93bdb446f6b5f13451ccc4906f3b05d3 Mon Sep 17 00:00:00 2001 From: Serhat Dolmaci Date: Thu, 9 Apr 2026 15:46:24 +0300 Subject: [PATCH 1/3] fix(run-a-base-node): update stale base-org/node links to base/node --- docs/base-chain/node-operators/run-a-base-node.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 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 c26979c79..44ba1b7e6 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,7 +66,7 @@ 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). +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`. 4. Run `docker compose up`. Confirm you get a response from: From ebaf370682ddb7b545ce31f51e0528dcabaa758c Mon Sep 17 00:00:00 2001 From: Serhat Dolmac Date: Thu, 9 Apr 2026 16:06:36 +0300 Subject: [PATCH 2/3] fix(troubleshooting): update stale base-org/node link to base/node --- docs/base-chain/node-operators/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/base-chain/node-operators/troubleshooting.mdx b/docs/base-chain/node-operators/troubleshooting.mdx index ade7224cc..fbb1a5526 100644 --- a/docs/base-chain/node-operators/troubleshooting.mdx +++ b/docs/base-chain/node-operators/troubleshooting.mdx @@ -124,4 +124,4 @@ Refer to the [Snapshots](/base-chain/node-operators/snapshots) guide for the cor If you’ve followed this guide and are still encountering issues, seek help from the community: - **Discord**: Join the [Base Discord](https://discord.gg/buildonbase) and post in the `🛠｜node-operators` channel, providing details about your setup, the issue, and relevant logs. -- **GitHub**: Check the [Base Node repository issues](https://github.com/base-org/node/issues) or open a new one if you suspect a bug. +- **GitHub**: Check the [Base Node repository issues](https://github.com/base/node/issues) or open a new one if you suspect a bug. From 06e9fc83ba1fe70bb346db5e827e6d80a3e15ff0 Mon Sep 17 00:00:00 2001 From: Serhat Dolmac Date: Thu, 9 Apr 2026 16:11:41 +0300 Subject: [PATCH 3/3] fix(launch-token): update archived base-org GitHub link to base --- docs/get-started/launch-token.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/get-started/launch-token.mdx b/docs/get-started/launch-token.mdx index 103ee0fae..bcccc57a8 100644 --- a/docs/get-started/launch-token.mdx +++ b/docs/get-started/launch-token.mdx @@ -428,7 +428,7 @@ Remember to always prioritize security, transparency, and community value when d Follow Base updates - + Contribute to Base development