chore: remove CoinEasy and add EasyChain icon

[jobotics]

Depends on defuse-protocol/defuse-sdk#555

Summary by CodeRabbit

• Chores

  • Updated the "@defuse-protocol/defuse-sdk" dependency to the latest version.
  • Updated several token entries to use "easychain" as the chain name instead of "coineasy".

• New Features

  • Improved logging integration for error reporting, including enhanced log sanitization and a new debug log level for more consistent and secure monitoring.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
defuse-widget	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 23, 2025 4:50pm

[coderabbitai]

Walkthrough

This update modifies three areas: it bumps the "@defuse-protocol/defuse-sdk" dependency version in package.json, updates the chainName property from "coineasy" to "easychain" for several tokens in src/constants/tokens.ts, and enhances Sentry logging in initSDK by sanitizing logging contexts and adding a debug log level.

Changes

File(s)	Change Summary
package.json	Updated "@defuse-protocol/defuse-sdk" version from "^1.0.0-beta.203" to "^1.0.0-beta.204".
src/constants/tokens.ts	Changed chainName from "coineasy" to "easychain" for multiple tokens in PRODUCTION_TOKENS.
src/libs/defuse-sdk/initSDK.ts	Improved Sentry logging: added debug level, sanitized contexts, introduced utility functions.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant initSDK
    participant Logger
    participant Sentry

    App->>initSDK: Initialize SDK
    initSDK->>Logger: Configure log levels (debug, info, warn, error)
    Logger->>initSDK: Log message with contexts
    initSDK->>initSDK: Sanitize contexts
    initSDK->>Sentry: Send sanitized log/context

Loading

Estimated code review effort

2 (~15 minutes)

Possibly related PRs

• chore: bump defuse-sdk #477: Also updates the "@defuse-protocol/defuse-sdk" dependency version in package.json.
• chore: bump defuse-sdk #474: Performs a similar dependency version bump for "@defuse-protocol/defuse-sdk".
• chore: bump @defuse-protocol/defuse-sdk #488: Updates the same dependency, indicating ongoing maintenance of defuse-sdk versions.

Suggested reviewers

• cawabunga-bytes

Poem

A hop and a skip, a version anew,
Tokens renamed, with chains in view.
Sentry logs now clean and bright,
Debugging made a sheer delight.
With every hop, the code refines—
🐇✨ Easychain shines!

---

📜 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 6d5250a and 5869738.

⛔ Files ignored due to path filters (3)

• public/static/icons/network/coineasy.svg is excluded by !**/*.svg
• public/static/icons/network/easychain.svg is excluded by !**/*.svg
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (3)

• package.json (1 hunks)
• src/constants/tokens.ts (5 hunks)
• src/libs/defuse-sdk/initSDK.ts (4 hunks)

🧬 Code Graph Analysis (1)

src/libs/defuse-sdk/initSDK.ts (1)

src/utils/logger.ts (2)

• Context (3-3)
• Contexts (4-4)

🧰 Additional context used

🧬 Code Graph Analysis (1)

src/libs/defuse-sdk/initSDK.ts (1)

src/utils/logger.ts (2)

• Context (3-3)
• Contexts (4-4)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: semgrep-cloud-platform/scan
• GitHub Check: semgrep-cloud-platform/scan
• GitHub Check: test
• GitHub Check: Supabase Preview

🔇 Additional comments (10)

src/constants/tokens.ts (5)

135-135: LGTM: Systematic chain name update from CoinEasy to EasyChain.

The change correctly updates the chainName from "coineasy" to "easychain" as part of the rebranding effort mentioned in the PR objectives.

---

325-325: LGTM: Chain name consistently updated.

The NEAR token chainName is correctly updated to "easychain" following the same pattern as other tokens.

---

448-448: LGTM: USDT token chainName updated correctly.

The chainName change maintains consistency with the overall EasyChain rebranding effort.

---

660-660: LGTM: ETH token chainName updated as expected.

The change aligns with the systematic rebranding from CoinEasy to EasyChain across all affected tokens.

---

767-767: LGTM: All “coineasy” references removed

A comprehensive scan of the repository (excluding node_modules) found no remaining references to “coineasy.” The final AURORA token chainName update to “easychain” is consistent, and all dependent code has been updated.

src/libs/defuse-sdk/initSDK.ts (4)

3-3: LGTM: Appropriate type imports for context sanitization.

The import of Context and Contexts types from @sentry/types provides proper typing for the new sanitization functionality.

---

28-28: LGTM: Debug log level added for development consistency.

Adding the debug log level to the development logger configuration ensures interface consistency between development and production modes.

---

53-72: LGTM: Comprehensive context sanitization for Sentry logging.

The addition of context sanitization across all log levels (debug, info, warn, error) is excellent defensive programming. This ensures:

• Invalid context data won't cause runtime errors when sent to Sentry
• Only properly structured context objects are included in logs
• Consistent behavior across all logging methods

The implementation correctly applies sanitizeContexts() to all methods that accept contexts.

---

87-104: LGTM: Well-implemented context sanitization utilities.

The utility functions are well-designed:

isContext function:

• Correctly validates that values are objects (not null, not arrays)
• Matches the expected Context type structure

sanitizeContexts function:

• Properly handles undefined input
• Safely filters out invalid context values
• Returns undefined when no valid contexts exist, preventing empty objects from being sent
• Uses appropriate typing with Contexts interface

The implementation follows defensive programming practices and handles edge cases correctly.

package.json (1)

18-18: LGTM: SDK version bump aligns with improvements.

The version increment from ^1.0.0-beta.203 to ^1.0.0-beta.204 appropriately reflects the SDK enhancements for improved Sentry logging and context sanitization seen in the initSDK.ts changes.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

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

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

[supabase]

Updates to Preview Branch (chore/add-easychain-icon) ↗︎

Deployments	Status	Updated
Database	✅	Wed, 23 Jul 2025 16:41:51 UTC
Services	✅	Wed, 23 Jul 2025 16:41:51 UTC
APIs	✅	Wed, 23 Jul 2025 16:41:51 UTC

Tasks are run on every commit but only new migration files are pushed.
Close and reopen this PR if you want to apply changes from existing seed or migration files.

Tasks	Status	Updated
Configurations	✅	Wed, 23 Jul 2025 16:41:52 UTC
Migrations	✅	Wed, 23 Jul 2025 16:41:53 UTC
Seeding	✅	Wed, 23 Jul 2025 16:41:54 UTC
Edge Functions	✅	Wed, 23 Jul 2025 16:41:54 UTC

---

View logs for this Workflow Run ↗︎.
Learn more about Supabase for Git ↗︎.