feat: integrate Blast (81457) as second-class Relay chain#11933
feat: integrate Blast (81457) as second-class Relay chain#11933gomesalexandre merged 7 commits intodevelopfrom
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…, and state migration - Add blastChainId to WRAPPED_NATIVE_CONTRACT_BY_CHAIN_ID (0x4300...0004, not standard OP Stack) - Add blastAssetId to generateChainRelatedAssetIndex ETH array - Add VITE_BLAST_NODE_URL and VITE_FEATURE_BLAST to vite-env.d.ts - Add VITE_WORLDCHAIN_NODE_URL and VITE_FEATURE_WORLDCHAIN to vite-env.d.ts - Bump clearAssets migration to 301 - Regenerate Blast chain assets (105 tokens) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…order Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Description
Integrate Blast (EVM chain ID 81457, CAIP
eip155:81457) as a second-class citizen chain in ShapeShift Web, following the exact same pattern as Hemi.This is PR 10 of 17 in a sequential chain integration series. These PRs must be reviewed and merged in order, as each builds on the previous one (stacked branches).
PR merge order:
What's included:
BlastMainnet = 'eip155:81457')blastand native asset IDethereum(ETH-native chain)Blast), CSP headers, viem/ethers clients, Zerion mapping62 files changed, 362 insertions, 3 deletions.
Issue (if applicable)
N/A
Risk
Low — This is a standard second-class chain integration behind a feature flag (
Blast). No existing chain behavior is modified. All changes follow the established pattern used by Hemi and other EVM chains.Testing
Engineering
Blastfeature flag via/flagsroute (click settings modal header 5 times)yarn lintandyarn type-check— both should passOperations
Screenshots (if applicable)
N/A — No visual changes; chain integration is behind a feature flag.