feat: regenerate asset data 08/11/2025

[0xean]

Generated from CI.

Summary by CodeRabbit

• Chores
  • Updated asset color map with a new color across major networks (e.g., Ethereum, BNB Chain, Polygon, Base) for improved visual consistency.
  • Refreshed related-asset index to provide more accurate and comprehensive related asset suggestions.
  • Added a state migration (version 158) to clear cached assets, ensuring users receive updated data after the refresh.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new color entry to color-map JSON for multiple chains, refreshes the related-asset index dataset with widespread mapping updates and a new key (41), and registers a new migration (158) to run clearAssets.

Changes

Cohort / File(s)	Summary of Changes
Color map augmentation scripts/generateAssetData/color-map.json	Inserted new color code "#2397B8" across several chain sections; added mapping for eip155:8453 ERC-20 address.
Related asset index refresh src/lib/asset-service/service/encodedRelatedAssetIndex.json	Comprehensive rewrite of asset→related IDs mappings; introduced new key 41; numerous lists updated with new IDs (e.g., 18416, 18441, 19405, 19406, 17106). Structure remains flat map of integers to integer arrays.
State migration update src/state/migrations/index.ts	Added migration entry 158: clearAssets to clearAssetsMigrations.

Sequence Diagram(s)

sequenceDiagram
  participant App
  participant MigrationManager
  participant clearAssets
  participant StateStore

  App->>MigrationManager: Run pending migrations
  MigrationManager->>MigrationManager: Check version 158
  alt 158 pending
    MigrationManager->>clearAssets: Invoke
    clearAssets->>StateStore: Purge asset-related state
    StateStore-->>MigrationManager: Acknowledged
  end
  MigrationManager-->>App: Migration complete

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~15 minutes

Possibly related PRs

• feat: regenerate asset data 08/09/2025 #10242: Similar regeneration touching color-map, related-asset index, and migrations.
• feat: regenerate asset data 08/06/2025 #10203: Updates the same data files and adds a clearAssets migration entry.
• feat: regenerate asset data 08/04/2025 #10180: Concurrent large refresh of encodedRelatedAssetIndex.json plus color map and migration changes.

Suggested reviewers

• gomesalexandre
• NeOMakinG

Poem

A nibble of blue in the color map bright,
New trails between assets by moonlit night,
Version 158 hops in with cheer,
Clearing old nests, keeping state clear.
I twitch my whiskers—index anew!
Onward I bound: B8, bold, and blue. 🐇✨

✨ 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: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 73b5e32 and f36d434.

⛔ Files ignored due to path filters (6)

• 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_42161/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/**

📒 Files selected for processing (3)

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

🧰 Additional context used

📓 Path-based instructions (3)

**/*

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

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

Files:

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

**/*.{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

**/*.{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)

⏰ 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). (1)

• GitHub Check: Install and Cache

🔇 Additional comments (13)

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

201-202: Approve migration 158 addition to clearAssetsMigrations

• clearAssetsMigrations now maps keys 0 through 158 to clearAssets.
• assetsPersistConfig in src/state/reducer.ts uses version: Math.max(...Object.keys(clearAssetsMigrations).map(Number)), so it will automatically pick up 158.
• createMigrate(clearAssetsMigrations, …) is wired correctly.

LGTM—no further changes required.

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

1654-1654: LGTM: Routine data refresh; entry format looks correct.

Checksum-cased ERC-20 address and 6-digit hex color are valid. File naming (kebab-case, .json) complies with guidelines.

---

1759-1759: LGTM: Valid CAIP-19 key and color hex.

No semantic issues; consistent with prior entries for eip155:1.

---

1828-1828: LGTM: Data addition only.

CAIP-19 format and color code are valid; no logic involved.

---

2102-2102: LGTM: Consistent formatting.

Address casing and color hex are valid; aligns with existing palette.

---

2361-2361: LGTM: Entry is well-formed.

Key matches eip155 ERC-20 pattern; color hex passes quick visual check.

---

2917-2917: LGTM: No issues spotted.

Key formatting and color code are OK for eip155:1.

---

7762-7762: LGTM: Arbitrum token color entry looks valid.

Key format eip155:42161/erc20:0x… and hex color are correct.

---

8132-8132: LGTM: Data-only change with valid value.

No structural concerns; consistent with neighboring entries.

---

8882-8882: LGTM: BSC BEP-20 entry is well-formed.

Key uses expected bep20 segment; color hex is valid.

---

13476-13476: LGTM: Entry formatting checks out.

Checksummed address and 6-hex color are valid for eip155:8453.

---

13721-13721: LGTM: Valid addition.

Key/value formats align with the rest of the 8453 section.

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

1-1: Routine asset data refresh from CI — LGTM

Per team learnings for “feat: regenerate asset data” PRs, skipping deep review. JSON structure is valid; new key 41 is present; no issues spotted.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

LGTM: New 8453 ERC-20 color set (#2397B8).

Key and value formats are valid. Given this is a routine generated dataset, keeping review light per team preference.

Run this quick validation to sanity-check the whole file (JSON validity, color hexes, and eip155 token key formats):

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

FILE="scripts/generateAssetData/color-map.json"

# 1) Validate JSON structure
jq -e type "$FILE" >/dev/null

# 2) Ensure all color values are 6-hex-digit codes
invalid_colors="$(jq -r 'to_entries[] | .value' "$FILE" | grep -Pv '^#[0-9A-Fa-f]{6}$' || true)"
if [ -n "$invalid_colors" ]; then
  echo "Invalid color codes found:"
  echo "$invalid_colors"
  exit 1
fi

# 3) Validate only eip155 token keys against ERC-20/BEP-20 formats (avoid false positives on non-EVM assets)
invalid_eip155_keys="$(jq -r 'to_entries[] | .key' "$FILE" \
  | grep '^eip155:' \
  | grep -Pv '^eip155:[0-9]+/(erc20|bep20):0x[0-9A-Fa-f]{40}$' || true)"
if [ -n "$invalid_eip155_keys" ]; then
  echo "Invalid eip155 token asset IDs:"
  echo "$invalid_eip155_keys"
  exit 1
fi

echo "color-map.json passed validation."

Length of output: 1228

---

Adjust EIP-155 key validation to allow native chain (slip44) entries

The CI validation script is currently rejecting all eip155: keys that aren’t ERC-20 or BEP-20 (e.g. eip155:1/slip44:60), but our color-map includes native-coin colors keyed by slip44. Please update the regex in the validation step to also accept slip44 entries.

Locations to update:
• The shell snippet in your CI or scripts/generateAssetData/… validation script

Example diff:

- invalid_eip155_keys="$(jq -r 'to_entries[] | .key' "$FILE" \
-   | grep '^eip155:' \
-   | grep -Pv '^eip155:[0-9]+/(erc20|bep20):0x[0-9A-Fa-f]{40}$' || true)"
+ invalid_eip155_keys="$(jq -r 'to_entries[] | .key' "$FILE" \
+   | grep '^eip155:' \
+   | grep -Pv '^eip155:[0-9]+/(?:erc20|bep20):0x[0-9A-Fa-f]{40}$|^eip155:[0-9]+/slip44:[0-9]+$' || true)"

This change will let both token and native-chain (slip44) asset IDs pass validation.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In scripts/generateAssetData/color-map.json around line 13219, the CI validation
currently rejects eip155 asset IDs that use slip44 for native coins; update the
validation regex in the CI/shell snippet (or the scripts/generateAssetData
validation script) so it accepts keys of the form
eip155:<chainId>/(erc20|bep20|slip44):<tokenId> — i.e. extend the alternation to
include slip44 and ensure the slip44 capture matches a numeric identifier (not
an ERC‑20 hex address); replace the existing pattern with one that allows slip44
entries and run the validation to confirm both token (erc20/bep20) and
native-chain (slip44) IDs pass.

[coderabbitai]

🧹 Nitpick (assertive)

Filename not in kebab-case (guideline nit)

Current: encodedRelatedAssetIndex.json. Consider encoded-related-asset-index.json when/if feasible, though this may be out-of-scope for autogenerated assets.

🤖 Prompt for AI Agents

In src/lib/asset-service/service/encodedRelatedAssetIndex.json (lines 1-1) the
filename uses camelCase rather than the project guideline kebab-case; rename the
file to encoded-related-asset-index.json and update all references to it
(imports, require calls, asset manifests, build scripts, tests, and any
generator/config that produces this file), perform the rename with git mv to
preserve history, run the build/test suite to catch missing references, and if
the file is autogenerated adjust the generator/config to emit the kebab-case
name instead of patching callers.

[0xApotheosis]

Diff sane, runtime check sane.