chore: update chains config

[Hemanthghs]

Summary by CodeRabbit

• New Features

  • Updated API endpoints for various blockchain networks to enhance connectivity and performance.

• Bug Fixes

  • Ensured all network configurations reflect the new API base URL, improving reliability across multiple networks.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
resolute	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 20, 2024 0:13am

[coderabbitai]

Walkthrough

The pull request focuses on updating the API endpoints for various blockchain networks in the chainsInfo.ts file. It replaces the old API base URL with a new one across multiple network configurations, ensuring that all relevant properties reflect this change. The update does not involve any alterations to the logic or structure of the code.

Changes

Files	Change Summary
frontend/src/utils/chainsInfo.ts	Updated API base URL from https://api.beta.resolute.vitwit.com to https://api.resolute.vitwit.com for multiple blockchain networks, including Agoric, Akash, CosmosHub, and others.

Possibly related PRs

• chore: update networks config #1258: This PR updates the REST and RPC endpoints for the OmniflixHub network in the same chainsInfo.ts file, indicating a direct connection to the changes made in the main PR regarding API endpoint updates for various blockchain networks.

🐇 In the code, we hop and play,
Updating URLs, hip-hip-hooray!
From beta to the new, we leap,
For all the chains, our promise we keep.
With every change, our paths align,
A smoother journey, oh how divine! 🌟

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8204002 and f978397.

Files selected for processing (1)

• frontend/src/utils/chainsInfo.ts (25 hunks)

Additional comments not posted (13)

frontend/src/utils/chainsInfo.ts (13)

31-32: Verify the new API base URL is functional.

The rest and rpc properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

34-34: Verify the backup API endpoints are functional.

The restURIs array has been updated to use the new base URL. Please ensure that the APIs are reachable and functional at all the endpoints listed in this array.

---

122-124: Verify the new API base URL is functional.

The rest and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

201-203: Verify the new API base URL is functional.

The rest and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

279-282: Verify the new API base URL is functional.

The rest, rpc and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

358-360: Verify the new API base URL is functional.

The rest, rpc and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

436-438: Verify the new API base URL is functional.

The rest, rpc and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

515-518: Verify the new API base URL is functional.

The rest, rpc and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

599-601: Verify the new API base URL is functional.

The rest and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

675-678: Verify the new API base URL is functional.

The rest, rpc and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

763-765: Verify the new API base URL is functional.

The rest and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

842-845: Verify the new API base URL is functional.

The rest, rpc and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

924-927: Verify the new API base URL is functional.

The rest, rpc and restURIs properties have been updated to use the new base URL https://api.resolute.vitwit.com. Please ensure that all the required APIs are fully functional at this new URL before deploying the change to production.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.