feat: regenerate asset data 08/09/2025

[0xean]

Generated from CI.

Summary by CodeRabbit

• New Features

  • Updated and expanded the color mapping for blockchain assets, providing new color associations for various tokens across multiple chains.
  • Enhanced related asset indexing with numerous new and revised associations, improving asset relationship data.

• Chores

  • Added a new migration step to support future data updates.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change updates two JSON data files with new and removed asset mappings and modifies the migration manifest to include a new migration version. The asset color map and encoded related asset index both receive extensive content updates, while the migration index adds a new version entry referencing an existing migration function.

Changes

Cohort / File(s)	Change Summary
Asset Color Map Updates scripts/generateAssetData/color-map.json	Added new asset-to-color mappings, removed some existing ones, and updated several entries.
Encoded Related Asset Index Updates src/lib/asset-service/service/encodedRelatedAssetIndex.json	Modified arrays for many keys: added, removed, or reordered integer values; added new keys.
Migration Manifest Update src/state/migrations/index.ts	Added migration entry for version 157, mapped to the clearAssets migration function.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant Migrations
    participant AssetData

    App->>Migrations: Check migration manifest
    Migrations->>Migrations: Detect new migration version 157
    Migrations->>AssetData: Run clearAssets migration
    AssetData-->>Migrations: Asset data cleared
    Migrations-->>App: Migration complete

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat: regenerate asset data 08/01/2025 #10172: Updates the same JSON data files for asset color mappings and related asset indices, indicating related asset data regeneration.
• feat: regenerate asset data 08/06/2025 #10203: Modifies both color-map.json and encodedRelatedAssetIndex.json with similar types of additions/removals, suggesting coordinated asset data updates.
• feat: regenerate asset data 08/04/2025 #10180: Updates both asset color and related asset index JSON files, showing strong overlap in data and process.

Suggested reviewers

• gomesalexandre
• NeOMakinG

Poem

A hop, a skip, a JSON hop—
New colors bloom, old mappings drop.
Indices shuffle, migrations grow,
Data refreshed in a rabbit’s flow.
With every change, the assets gleam,
Code and carrots—what a team!
🥕✨

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat_regenerate_asset_data

---

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.
• 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.

Support

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

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 generate unit tests to generate unit tests for 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9f46efe and 61f8c1b.

⛔ Files ignored due to path filters (9)

• packages/caip/src/adapters/coincap/generated/eip155_1/adapter.json is excluded by !**/generated/**
• packages/caip/src/adapters/coingecko/generated/eip155_1/adapter.json is excluded by !**/generated/**
• packages/caip/src/adapters/coingecko/generated/eip155_137/adapter.json is excluded by !**/generated/**
• packages/caip/src/adapters/coingecko/generated/eip155_42161/adapter.json is excluded by !**/generated/**
• packages/caip/src/adapters/coingecko/generated/eip155_43114/adapter.json is excluded by !**/generated/**
• packages/caip/src/adapters/coingecko/generated/eip155_56/adapter.json is excluded by !**/generated/**
• packages/caip/src/adapters/coingecko/generated/eip155_8453/adapter.json is excluded by !**/generated/**
• packages/caip/src/adapters/coingecko/generated/solana_5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp/adapter.json is excluded by !**/generated/**
• packages/swapper/src/swappers/MayachainSwapper/generated/generatedTradableAssetMap.json is excluded by !**/generated/**

📒 Files selected for processing (3)

• scripts/generateAssetData/color-map.json (70 hunks)
• src/lib/asset-service/service/encodedRelatedAssetIndex.json (1 hunks)
• src/state/migrations/index.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/error-handling.mdc)

**/*.{ts,tsx}: ALWAYS use Result<T, E> pattern for error handling in swappers and APIs
ALWAYS use Ok() and Err() from @sniptt/monads for monadic error handling
ALWAYS use custom error classes from @shapeshiftoss/errors
ALWAYS provide meaningful error codes for internationalization
ALWAYS include relevant details in error objects
ALWAYS wrap async operations in try-catch blocks
ALWAYS use AsyncResultOf utility for converting promises to Results
ALWAYS provide fallback error handling
ALWAYS use timeoutMonadic for API calls
ALWAYS provide appropriate timeout values for API calls
ALWAYS handle timeout errors gracefully
ALWAYS validate inputs before processing
ALWAYS provide clear validation error messages
ALWAYS use early returns for validation failures
ALWAYS log errors for debugging
ALWAYS use structured logging for errors
ALWAYS include relevant context in error logs
Throwing errors instead of using monadic patterns is an anti-pattern
Missing try-catch blocks for async operations is an anti-pattern
Generic error messages without context are an anti-pattern
Not handling specific error types is an anti-pattern
Missing timeout handling is an anti-pattern
No input validation is an anti-pattern
Poor error logging is an anti-pattern
Using any for error types is an anti-pattern
Missing error codes for internationalization is an anti-pattern
No fallback error handling is an anti-pattern
Console.error without structured logging is an anti-pattern

**/*.{ts,tsx}: ALWAYS use camelCase for variables, functions, and methods
ALWAYS use descriptive names that explain the purpose for variables and functions
ALWAYS use verb prefixes for functions that perform actions
ALWAYS use PascalCase for types, interfaces, and enums
ALWAYS use descriptive names that indicate the structure for types, interfaces, and enums
ALWAYS use suffixes like Props, State, Config, Type when appropriate for types and interfaces
ALWAYS use UPPER_SNAKE_CASE for constants and configuration values
ALWAYS use d...

Files:

• src/state/migrations/index.ts

**/*

📄 CodeRabbit Inference Engine (.cursor/rules/naming-conventions.mdc)

**/*: ALWAYS use appropriate file extensions
Flag files without kebab-case

Files:

• src/state/migrations/index.ts
• scripts/generateAssetData/color-map.json
• src/lib/asset-service/service/encodedRelatedAssetIndex.json

**/*.{ts,tsx,js,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/react-best-practices.mdc)

USE Redux only for global state shared across multiple places

Files:

• src/state/migrations/index.ts

🧠 Learnings (1)

📓 Common learnings

Learnt from: NeOMakinG
PR: shapeshift/web#10136
File: src/lib/asset-service/service/encodedRelatedAssetIndex.json:1-1
Timestamp: 2025-07-29T10:22:27.037Z
Learning: PRs with titles starting with "feat: regenerate asset data" are routine daily asset updates that don't need detailed code analysis. Users prefer to skip automated reviews for these maintenance PRs using coderabbitai ignore.

🧬 Code Graph Analysis (1)

src/state/migrations/index.ts (1)

src/state/migrations/clearAssets.ts (1)

• clearAssets (6-8)

🔇 Additional comments (4)

src/state/migrations/index.ts (2)

200-200: LGTM: v157 entry added to clearAssetsMigrations

Consistent with prior contiguous versions (0–157). Per retrieved learnings, this is a routine asset-data regeneration PR; keeping review minimal.

---

200-200: No manual version bump needed for clearAssetsMigrations

The assetsPersistConfig.version is set to Math.max(...Object.keys(clearAssetsMigrations).map(Number)), so it automatically picks up the highest migration key (now 157). Your new entry at 157: clearAssets will run without any further changes.

Likely an incorrect or invalid review comment.

scripts/generateAssetData/color-map.json (1)

74-80: Routine asset color map refresh — approving; skipping deep review

CI-generated “feat: regenerate asset data” update. Content-only JSON changes; no structural or code risks detected.
Note: the local validation script suggested above uses a regex limited to eip155/erc20 and will reject valid CAIP-19 identifiers such as Bitcoin (bip122/.../slip44) and Cosmos (cosmos/.../slip44). If you’d like local checks, update the regex to cover all CAIP-19 namespaces (e.g. bip122, cosmos, etc.); otherwise, rely on existing CI validation.

Likely an incorrect or invalid review comment.

src/lib/asset-service/service/encodedRelatedAssetIndex.json (1)

1-1: Routine CI data refresh — LGTM

Data-only JSON update. No logic to review here. Assuming the generator produced this, content looks syntactically valid.

[coderabbitai]

🧹 Nitpick (assertive)

Filename is not kebab-case (repository guideline)

Guidelines say to flag files without kebab-case. Consider renaming to encoded-related-asset-index.json in a follow-up PR to avoid churn. Non-blocking for this automated update.

🤖 Prompt for AI Agents

In src/lib/asset-service/service/encodedRelatedAssetIndex.json at line 1, the
filename does not follow the repository guideline of using kebab-case. Rename
the file to encoded-related-asset-index.json in a separate follow-up PR to
comply with naming conventions without causing disruption to the current
automated update.

[0xApotheosis]

Diff sane,, runtime check sane.