From b6b9847cd295bfa0463510748ace0dc2b8f05613 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 c406366f5468aff3511785df4827e8edb3ee3286 Mon Sep 17 00:00:00 2001 From: Erhnysr Date: Fri, 22 May 2026 22:48:20 +0300 Subject: [PATCH 2/2] docs(azul): add BASE_NODE_L2_ENGINE_AUTH_RAW to env mapping table and FAQ BASE_NODE_L2_ENGINE_AUTH_RAW was missing from the op-node to base-consensus environment variable mapping table, and there was no guidance in the FAQ about setting a secure JWT secret. Operators migrating from op-node need to know that: - BASE_NODE_L2_ENGINE_AUTH_RAW must be explicitly set - The default placeholder value is insecure for nodes using host networking or custom port mappings - A secure value can be generated with: openssl rand -hex 32 Related to base/node#1087 --- docs/base-chain/node-operators/base-v1-upgrade.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/base-chain/node-operators/base-v1-upgrade.mdx b/docs/base-chain/node-operators/base-v1-upgrade.mdx index 46325ef6b..3420e7e3c 100644 --- a/docs/base-chain/node-operators/base-v1-upgrade.mdx +++ b/docs/base-chain/node-operators/base-v1-upgrade.mdx @@ -117,6 +117,7 @@ If you use [base/node](https://github.com/base/node), most variables are already | `OP_NODE_L1_TRUST_RPC` | `BASE_NODE_L1_TRUST_RPC` | | `OP_NODE_L2_ENGINE_RPC` | `BASE_NODE_L2_ENGINE_RPC` | | `OP_NODE_L2_ENGINE_AUTH` | `BASE_NODE_L2_ENGINE_AUTH` | +| — | `BASE_NODE_L2_ENGINE_AUTH_RAW` | | — | `BASE_NODE_L2_ENGINE_AUTH_ENCODED` | | `OP_NODE_P2P_BOOTNODES` | `BASE_NODE_P2P_BOOTNODES` | | `OP_NODE_P2P_LISTEN_IP` | `BASE_NODE_P2P_LISTEN_IP` | @@ -151,6 +152,7 @@ If you use [base/node](https://github.com/base/node), most variables are already ## FAQ +- **Do I need to set `BASE_NODE_L2_ENGINE_AUTH_RAW`?** Yes — this must be set to a secure random hex string shared between the execution and consensus containers. Generate one with `openssl rand -hex 32`. Nodes using host networking or custom port mappings that rely on the default placeholder value are exposed to unauthenticated Engine API access. - **Do I need to re-sync?** Not if you are already running OP Reth. Existing data is compatible. - **What if I'm on `op-geth` or `nethermind`?** You need to switch to `base-reth-node`. Use a [Reth snapshot](/base-chain/node-operators/snapshots) to bootstrap. - **Do OP namespace RPCs still work?** Yes, all existing RPCs are supported.