chore: add ezeth token meta

[ivan-angjelkoski]

Summary by CodeRabbit

• New Features
  • Introduced a new cryptocurrency token "ezETH" with complete metadata support in the platform.

[coderabbitai]

Walkthrough

This update introduces metadata for a new cryptocurrency token named "ezETH". The metadata includes essential details such as the token's address, coinGeckoId, denomination, name, symbol, decimals, and logo. This addition enriches the token's identification and integration capabilities within the system.

Changes

File Path	Change Summary
pkg/.../token_meta.json	Added metadata for "ezETH" including address, coinGeckoId, denom, and other details.

Poem

🌟🐰✨
In the digital fields so wide and vast,
A new token sprouts, its roots to cast.
"ezETH" it’s called, with details so clear,
A hop in the code, the future is near!
🌿🌼🚀

---

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration 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 3e37df5 and c1e2c64.

Files selected for processing (1)

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

Additional comments not posted (1)

pkg/token/token_meta.json (1)

1897-1907: Ensure the address and logo fields for "ezETH" are correctly populated before merging.

Verification successful

---

The verification process confirms that both the address and logo fields for "ezETH" are correctly populated in the pkg/token/token_meta.json file. There are no empty fields for this token entry, aligning with the requirements specified in the review comment.

• Address Field: Populated
• Logo Field: Populated

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Check if the 'address' and 'logo' fields for "ezETH" are populated.

# Test: Search for empty 'address' or 'logo' fields under "ezETH". Expect: No matches.
rg --type json '"ezETH": \{[^}]*"address": "",[^}]*"logo": ""' pkg/token/token_meta.json

Length of output: 90

---

---

Script:

#!/bin/bash
# Description: Check if the 'address' field for "ezETH" is populated.

# Test: Search for an empty 'address' field under "ezETH". Expect: No matches.
rg --type json '"ezETH": \{[^}]*"address": ""' pkg/token/token_meta.json

# Description: Check if the 'logo' field for "ezETH" is populated.

# Test: Search for an empty 'logo' field under "ezETH". Expect: No matches.
rg --type json '"ezETH": \{[^}]*"logo": ""' pkg/token/token_meta.json

Length of output: 146