chore(spaceward): added chiado chain to spaceward config

[jjheywood]

Summary by CodeRabbit

• New Features
  • Added support for the Warden Protocol Chiado testnet, enhancing the application’s blockchain capabilities.
  • Introduced a new asset list for the Chiado testnet, featuring the native token "award" with associated metadata.

[coderabbitai]

Walkthrough

Walkthrough

The changes involve the addition of a new blockchain protocol, Warden Protocol Chiado, and its associated assets to the application. This includes updates to the App.tsx file to integrate the new protocol and asset list, as well as the introduction of a detailed chain configuration in the chains.ts file, defining various properties and parameters related to the new testnet.

Changes

File	Change Summary
spaceward/src/App.tsx	Added imports for wardenprotocolchiado and wardenprotocolchiadoAssets, integrated them into the ChainProvider and assetLists arrays.
spaceward/src/config/chains.ts	Introduced new chain configuration for Warden Protocol Chiado, detailing properties such as name, network type, fees, staking, APIs, and asset management.

Possibly related PRs

• restrict tokens to testnet only #589: The changes in this PR involve modifications to the handling of asset queries and network configurations, which may relate to the new blockchain protocol and asset support introduced in the main PR.
• feat(spaceward): fix qa issues #877: This PR includes updates to the validation logic, which could potentially interact with the new blockchain configurations and asset management introduced in the main PR.

Suggested labels

spaceward

Suggested reviewers

• alex-nax

---

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.

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.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

spaceward/src/App.tsx (1)

118-118: LGTM: New chain and assets integrated correctly.

The wardenprotocolchiado chain and wardenprotocolchiadoAssets are correctly added to the ChainProvider component, following the existing pattern for other chain configurations.

Consider adding a comment above these new additions to improve code readability, especially if more chains are expected to be added in the future. For example:

 chains={[
   ...chains,
   wardenprotocollocal,
   wardenprotocoldevnet,
   wardenprotocolbuenavista,
+  // Add new chains below this line
   wardenprotocolchiado,
 ]}
 assetLists={[
   ...assets,
   wardenprotocollocalAssets,
   wardenprotocoldevnetAssets,
   wardenprotocolbuenavistaAssets,
+  // Add new asset lists below this line
   wardenprotocolchiadoAssets,
 ]}

Also applies to: 125-125

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 78301ea and f4ef114.

Files selected for processing (2)

• spaceward/src/App.tsx (2 hunks)
• spaceward/src/config/chains.ts (1 hunks)

Additional comments not posted (3)

spaceward/src/App.tsx (1)

8-9: LGTM: New chain configuration imports added correctly.

The new imports for wardenprotocolchiado and wardenprotocolchiadoAssets are added consistently with the existing import pattern for other chain configurations.

spaceward/src/config/chains.ts (2)

352-433: LGTM: Chain configuration structure is consistent

The new chain configuration for Warden Protocol Chiado follows the same structure as existing configurations, maintaining consistency across the file. The chain-specific details such as chain_name, chain_id, and pretty_name are correctly set for the Chiado testnet.

Verify and update the codebase section if necessary

The codebase section (lines 381-408) appears to be copied from other configurations. Please verify and update the following if needed:

• Git repository URL
• Recommended and compatible versions
• Genesis URL

Confirm the correctness of API endpoints

The API endpoints (lines 409-423) use environment variables (env.rpcURL and env.apiURL). Please ensure these variables are correctly set for the Chiado testnet in the environment configuration.

---

435-466: LGTM: Asset list configuration is consistent and complete

The asset list for Warden Protocol Chiado is well-structured and consistent with other asset lists in the file. The token details, including denominations and exponents, are correctly set for an Ethereum-compatible chain.

Verify logo and image URLs

Please confirm that the logo and image URLs (lines 455-456 and 460-461) are correct and accessible for the Chiado testnet. These URLs are currently using the same paths as other configurations, which may be intentional if the assets are shared across networks.