Skip to content

chore: update Eden default RPC#1399

Merged
paulbalaji merged 1 commit intomainfrom
update-eden-rpc
Feb 25, 2026
Merged

chore: update Eden default RPC#1399
paulbalaji merged 1 commit intomainfrom
update-eden-rpc

Conversation

@paulbalaji
Copy link
Collaborator

@paulbalaji paulbalaji commented Feb 25, 2026

Summary

  • Update Eden chain default RPC from https://eden-rpc.celestia.org to https://rpc.eden.gateway.fm

Test plan

  • Verify RPC endpoint is reachable
  • Build succeeds

🤖 Generated with Claude Code


Note

Low Risk
Single configuration change to the Eden RPC endpoint plus a patch-version changeset; risk is limited to potential connectivity/compatibility issues with the new RPC URL.

Overview
Updates the Eden chain metadata to switch the default rpcUrls endpoint from https://eden-rpc.celestia.org to https://rpc.eden.gateway.fm.

Adds a Changeset to publish @hyperlane-xyz/registry as a patch release reflecting the new default RPC.

Written by Cursor Bugbot for commit b6b9b05. This will update automatically on new commits. Configure here.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 25, 2026

Warning

Rate limit exceeded

@paulbalaji has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 39 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between da3fe05 and b6b9b05.

📒 Files selected for processing (2)
  • .changeset/update-eden-rpc.md
  • chains/eden/metadata.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-eden-rpc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@paulbalaji paulbalaji changed the title Update Eden default RPC chore: update Eden default RPC Feb 25, 2026
@paulbalaji paulbalaji enabled auto-merge February 25, 2026 18:22
@paulbalaji paulbalaji added this pull request to the merge queue Feb 25, 2026
Merged via the queue into main with commit 7b92d0b Feb 25, 2026
12 checks passed
@paulbalaji paulbalaji deleted the update-eden-rpc branch February 25, 2026 18:32
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

protocol: ethereum
rpcUrls:
- http: https://eden-rpc.celestia.org
- http: https://rpc.eden.gateway.fm
Copy link

Choose a reason for hiding this comment

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

Combined metadata remains stale

Medium Severity

Updating chains/eden/metadata.yaml alone leaves the aggregated chains/metadata.yaml entry for eden unchanged, so clients reading combined metadata still receive the old RPC URL. This makes the default RPC update ineffective for code paths that call getMetadata() instead of per-chain files.

Fix in Cursor Fix in Web

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.

2 participants