Skip to content

Conversation

@anikaraghu
Copy link

@anikaraghu anikaraghu commented Oct 23, 2025

What changed? Why?
Updating node provider docs to say Reth is the recommended client.

Notes to reviewers
Removed some duplicated content and made other small updates

How has it been tested?
N/A

@cb-heimdall
Copy link
Collaborator

cb-heimdall commented Oct 23, 2025

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/2
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 1
Sum 2


- **Issue**: RPC/WS connection refused (e.g., `curl` to `localhost:8545` fails).
- **Check**: Is the L2 client container (`op-geth`/`op-reth`) running (`docker compose ps`)?
- **Check**: Is the L2 client container (`op-reth`/`op-geth`) running (`docker compose ps`)?
Copy link
Contributor

Choose a reason for hiding this comment

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

this would be base-node-reth in case they're running our node type instead of vanilla

tobidae-cb
tobidae-cb previously approved these changes Oct 24, 2025
@cb-heimdall cb-heimdall dismissed tobidae-cb’s stale review October 24, 2025 18:42

Approved review 3378205192 from tobidae-cb is now dismissed due to new commit. Re-request for approval.


- **Issue**: `optimism_syncStatus` (port `7545` on `op-node`) shows a large time difference or errors.
- **Action**: Check the logs for both `op-node` and the L2 client (`op-reth`/`op-geth`) around the time the status was checked to identify the root cause (e.g., L1 connection issues, L2 client issues).
- **Action**: Check the logs for both `op-node` and the L2 execution client around the time the status was checked to identify the root cause (e.g., L1 connection issues, L2 client issues).
Copy link
Contributor

@haardikk21 haardikk21 Oct 24, 2025

Choose a reason for hiding this comment

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

s/op-node/"the Rollup node" since the docker service name is simply node not op-node

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