Skip to content

fix: update stale base-org/node links to base/node #1297

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
erhnysr wants to merge 2 commits into
base: master
Choose a base branch
from
+6 −3
Open

fix: update stale base-org/node links to base/node #1297

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
83ce90f
docs: add RPC usage clarification note
erhnysr Apr 6, 2026
eaf7ff3
fix: update stale base-org/node links to base/node
erhnysr Apr 11, 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
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
4 changes: 2 additions & 2 deletions docs/base-chain/node-operators/run-a-base-node.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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:
Expand Down
2 changes: 1 addition & 1 deletion docs/base-chain/node-operators/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,4 +126,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.