Update denoms.ts

[mattnyy84]

Fixing $bINJ denom and adding $SYN denom

Summary by CodeRabbit

• New Features

  • Added recognition for two additional verified token denoms, enabling balances, prices, and transfers for bINJ and SYN from new sources.

• Chores

  • Removed a deprecated bINJ denom from the verified list to reduce clutter and prevent mismatches.
  • All other verified tokens remain unchanged.

[coderabbitai]

Walkthrough

Update to verifiedTokenFactoryDenoms: removed one denom entry, added two new entries; no API or signature changes.

Changes

Cohort / File(s)	Summary of Changes
Token factory denom registry src/data/tokens/denoms.ts	In verifiedTokenFactoryDenoms: removed inj10q36ygr0pkz7ezajcnjd2f0tat5n737yg6g6d5/bINJ; added inj1dxp690rd86xltejgfq2fa7f2nxtgmm5cer3hvu/bINJ and inj1a6xdezq7a94qwamec6n6cnup02nvewvjtz6h6e/SYN. Other entries unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A whisk of code, a hop, a spin—
One denom out, two hopping in.
Addresses burrow, arrays align,
Carrots counted, checks are fine.
I twitch my ears—release begins! 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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

🧹 Nitpick comments (1)

src/data/tokens/denoms.ts (1)

16-16: Adding SYN expands scope beyond the PR intent—please confirm it’s intended and vetted

The PR description mentions fixing $bINJ only. Introducing a new verified denom (SYN) typically requires separate curation. If this was intentional and meets your “verified” criteria, consider updating the PR title/description; otherwise, move it to a separate PR to keep scope focused.

If you decide to keep this PR scoped strictly to $bINJ, apply this diff to drop the SYN line:

-  'factory/inj1a6xdezq7a94qwamec6n6cnup02nvewvjtz6h6e/SYN',

📜 Review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 23d29ed and 9ef60da.

📒 Files selected for processing (1)

• src/data/tokens/denoms.ts (1 hunks)

🔇 Additional comments (1)

src/data/tokens/denoms.ts (1)

15-15: bINJ factory denom correction looks good

The format follows the expected factory/<inj address>/<subdenom> pattern and the casing matches prior conventions. No issues spotted with this replacement.