feat: add wrapped fzaar

[ALPAC-4]

add wfZAAR token

Summary by CodeRabbit

• New Features
  • Introduced a new asset, "Wrapped fZAAR," to the asset list.
  • The asset now features comprehensive details, including multi-denomination configurations and enhanced visual assets for improved display across platforms.

[coderabbitai]

Walkthrough

The pull request updates the asset list configuration by adding a new entry for "Wrapped fZAAR." This entry includes a detailed structure with denomination units, base, display name, symbol, trace information for both wrapped and IBC types, and image/logo URIs. The modifications ensure the asset is properly represented in the system with all necessary metadata.

Changes

File	Summary
testnets/initia/assetlist.json	Added new asset "Wrapped fZAAR" with details including description, two denomination units (ibc token and wfZAAR), base, display name, symbol, traces for wrapped and IBC types, and corresponding image/logo URIs.

Possibly related PRs

• feat: add zaar #246: Introduces a similar new asset entry ("Fake Zaar") in the registry, involving comparable structured metadata changes.

Suggested reviewers

• simcheolhwan

Poem

I’m a rabbit with a code-bound beat,
Hopping through JSON with nimble feet.
"Wrapped fZAAR" now leaps onto the scene,
A shiny asset, crisp and clean.
Carrots and code, a celebration so sweet!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0c9d0eb and 657a28f.

📒 Files selected for processing (1)

• testnets/initia/assetlist.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Cloudflare Pages: registry-initiation-1

🔇 Additional comments (3)

testnets/initia/assetlist.json (3)

387-402: Asset Metadata Verification for Wrapped fZAAR
The new asset entry accurately defines the metadata for wfZAAR. The description, denom_units (with the IBC base unit at exponent 0 and the wrapped token at exponent 6), base, display, name, and symbol fields are correctly set and consistent with similar assets in the list.

---

403-426: IBC Trace Configuration Check
The asset includes two trace objects: one for the wrapped type and another for ibc. Note that in the ibc trace, the counterparty specifies a channel_id of "channel-0" while the chain object provides "channel-1341" and a matching transfer path. Please verify that this mismatch is intentional and aligns with the intended IBC routing or network configuration.

---

428-437: Image and Branding Confirmation
Both the "images" and "logo_URIs" fields point to URLs under "zaar/images" (ZAAR.png and ZAAR.svg). Confirm that using the Zaar branding assets for the wfZAAR token is correct and that no adjustments are needed to reflect the wrapped fZAAR naming if separate branding is desired.

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[cloudflare-workers-and-pages]

Deploying registry-initiation-1 with    Cloudflare Pages

Latest commit:	657a28f
Status:	✅  Deploy successful!
Preview URL:	https://a05650ff.registry-initiation-1.pages.dev
Branch Preview URL:	https://feat-wrapped-fzaar.registry-initiation-1.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

testnets/initia/assetlist.json (1)

402-403: Optional: Populate coingecko_id if available
Currently, the "coingecko_id" field is an empty string. If the wfZAAR token is listed on Coingecko, consider adding the corresponding ID to this field. This enhancement would improve the asset’s integration with pricing and market data tools.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 563aee4 and 0c9d0eb.

📒 Files selected for processing (1)

• testnets/initia/assetlist.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Cloudflare Pages: registry-initiation-1

🔇 Additional comments (1)

testnets/initia/assetlist.json (1)

385-437: New asset entry for "Wrapped fZAAR" is structured correctly
The new asset entry includes all the essential fields—such as "description", "denom_units" (with both the IBC denom and the wfZAAR variant), "base", "display", "name", "symbol", and detailed "traces" for both wrapped and IBC types—as well as the image and logo URIs. Please double-check that the chain parameters (e.g., contract address, channel id, and path) are correct to ensure smooth integration with downstream systems.

[cloudflare-workers-and-pages]

Deploying registry-devnet with    Cloudflare Pages

Latest commit:	657a28f
Status:	✅  Deploy successful!
Preview URL:	https://6866bd50.registry-devnet.pages.dev
Branch Preview URL:	https://feat-wrapped-fzaar.registry-devnet.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying registry-testnet with    Cloudflare Pages

Latest commit:	657a28f
Status:	✅  Deploy successful!
Preview URL:	https://58a638d9.initia-registry-testnets.pages.dev
Branch Preview URL:	https://feat-wrapped-fzaar.initia-registry-testnets.pages.dev

View logs