Add USDY token metadata

[hmoragrega]

Summary by CodeRabbit

• New Features

  • Added support for the "USDY" token, including enhanced metadata for improved integration and display within applications.
  • Introduced detailed attributes such as name, symbol, and logo for the newly supported token.

• Improvements

  • Updated validation processes to skip an additional market during the validation workflow, enhancing efficiency.
  • Upgraded dependencies and Go version to improve performance and stability of the application.

[coderabbitai]

Walkthrough

The update introduces the "USDY" token to the token_meta.json file, enhancing the metadata framework with vital details like the token's address and logo. Additionally, the GitHub Actions workflow has been updated to allow the validator to skip an extra market during validation. Furthermore, dependency versions in the go.mod file have been upgraded, and code simplifications were made in the validator's logic, collectively improving token management and system efficiency.

Changes

Files	Change Summary
pkg/token/token_meta.json	Added new entry for "USDY" token with attributes: address, coinGeckoId, denom, metaSource, and metadata.
.github/workflows/test.yaml	Updated Go version to ^1.22 and expanded the --market-skip-list to include an additional market ID.
go.mod	Updated Go version to 1.22 and upgraded multiple dependencies, enhancing overall functionality and stability.
internal/validator/main.go	Simplified variable declarations and error handling in the findMarketOnAllNetwork function.

Poem

In the garden of tokens, we cheer with delight,
USDY blooms like a star in the night. 🌟
With a logo so fine and details so clear,
It hops into wallets, spreading good cheer!
So here’s to the change, let’s dance and be free,
A rabbit’s delight, oh, what fun it will be! 🐇✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a107693 and 2fe7617.

Files selected for processing (1)

• pkg/token/token_meta.json (1 hunks)

Additional comments not posted (2)

pkg/token/token_meta.json (2)

1921-1931: Verify the empty address field.

The address field for the "USDY" token is empty. Ensure that this is intentional and does not affect the functionality.

---

1921-1931: LGTM!

The new entry for the "USDY" token is well-formed and consistent with other entries in the file.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2fe7617 and f503c92.

Files selected for processing (1)

• .github/workflows/test.yaml (1 hunks)

Additional comments not posted (1)

.github/workflows/test.yaml (1)

27-27: Verify the correctness of the new market identifier.

Ensure that the new market identifier 0x315e5cd5ee24b3a1e1396679885b5e42bbe18045105d1662c6618430a131d117 is accurate and intended to be skipped during validation.

Verification successful

---

The new market identifier is correct.

The new market identifier 0x315e5cd5ee24b3a1e1396679885b5e42bbe18045105d1662c6618430a131d117 is present in the pkg/token/token_meta.json file, confirming its validity and intended use.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the correctness of the new market identifier.

# Test: Search for the new market identifier in the codebase. Expect: Valid references to the new market identifier.
rg --type json '0x315e5cd5ee24b3a1e1396679885b5e42bbe18045105d1662c6618430a131d117'

Length of output: 184

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f503c92 and aa00ef1.

Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

Files selected for processing (3)

• .github/workflows/test.yaml (1 hunks)
• go.mod (1 hunks)
• internal/validator/main.go (2 hunks)

Files skipped from review due to trivial changes (1)

• internal/validator/main.go

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/test.yaml

Additional comments not posted (7)

go.mod (7)

3-3: Update Go version to 1.22.

The Go version has been updated from 1.20 to 1.22. Ensure that the codebase is compatible with Go 1.22 and that all CI/CD pipelines are updated accordingly.

---

5-5: Add toolchain directive for Go 1.22.0.

The toolchain directive has been added for Go 1.22.0. Ensure that the toolchain is correctly configured and compatible with the project requirements.

---

8-8: Update github.com/InjectiveLabs/sdk-go dependency to v1.51.0.

The github.com/InjectiveLabs/sdk-go dependency has been updated from v1.48.17 to v1.51.0. Verify that the new version is compatible with the existing codebase and that any breaking changes are addressed.

---

13-13: Update github.com/sirupsen/logrus dependency to v1.9.3.

The github.com/sirupsen/logrus dependency has been updated from v1.9.0 to v1.9.3. This update may include bug fixes and minor improvements. Ensure that the new version does not introduce any issues.

---

19-19: Update cosmossdk.io/core dependency to v0.11.0.

The cosmossdk.io/core dependency has been updated from v0.5.1 to v0.11.0. Verify that the new version is compatible with the existing codebase and that any breaking changes are addressed.

---

49-49: Update github.com/cosmos/cosmos-sdk dependency to v0.50.7.

The github.com/cosmos/cosmos-sdk dependency has been updated from v0.47.3 to v0.50.7. This update may include new features, bug fixes, and performance improvements. Ensure that the new version is compatible with the existing codebase and that any breaking changes are addressed.

---

170-170: Add replacement for github.com/bandprotocol/bandchain-packet.

The replacement for github.com/bandprotocol/bandchain-packet has been added to use github.com/InjectiveLabs/bandchain-packet v0.0.4-0.20230327115226-35199d4659d5. Ensure that this replacement is necessary and that the new version is compatible with the existing codebase.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between aa00ef1 and b46d49b.

Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

Files selected for processing (3)

• .github/workflows/test.yaml (1 hunks)
• go.mod (1 hunks)
• internal/validator/main.go (2 hunks)

Files skipped from review due to trivial changes (1)

• internal/validator/main.go

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/test.yaml

Additional comments not posted (4)

go.mod (4)

3-3: Upgrade to Go 1.22.

The Go version has been updated to 1.22. Ensure that the codebase is compatible with the new version and takes advantage of any new features or performance improvements.

---

8-13: Dependency updates.

Dependencies such as github.com/InjectiveLabs/sdk-go, github.com/sirupsen/logrus, and cosmossdk.io/core have been updated. Ensure that the codebase is compatible with these new versions and that any new features or improvements are utilized.

---

17-167: Indirect dependency updates.

Several indirect dependencies have been updated. Ensure that the codebase is compatible with these new versions and that any new features or improvements are utilized.

---

170-170: Replacement directive added.

A replacement directive has been added for github.com/bandprotocol/bandchain-packet. Ensure that this replacement does not introduce any issues and that it is compatible with the rest of the codebase.