skills.rest
mejango
mejangoCOMMUNITY
Explore all skills by this author →
𝕏@me_jangoGitHub

jb-omnichain-erc20-config

Configure per-chain ERC20 token addresses for Juicebox V5 omnichain deployments.

Updated Jan 17, 2026
Search Tags:#multichain#ERC20#omnichain#Juicebox#token-addresses#terminal-configurations
One-click install
npx skills add https://github.com/mejango/juicy-vision --skill jb-omnichain-erc20-config
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jb-omnichain-erc20-config
Source: https://github.com/mejango/juicy-vision/tree/main/.claude/skills/jb-omnichain-erc20-config
Command: npx skills add https://github.com/mejango/juicy-vision --skill jb-omnichain-erc20-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes cross-chain ERC20 token address mismatches when deploying Juicebox V5 omnichain projects. It enables per-chain terminal configurations and accurate per-chain token mappings to prevent deploying with a single address across chains or defaulting to NATIVE_TOKEN.

Core Features & Use Cases

  • Per-chain terminal configuration overrides: specify different ERC20 addresses for each chain.
  • ERC20 address extraction: derive per-chain token addresses from approved terminals and accounting contexts.
  • Automated sucker configuration generation: produce correct cross-chain token mappings for each chain pair, ensuring deployments reflect per-chain tokens.
  • Use Case: Deploy a Juicebox V5 project across Sepolia, OP Sepolia, Base Sepolia, and Arb Sepolia with distinct USDC addresses.

Quick Start

Provide a chainConfigs array with per-chain terminalConfigurations that include the correct ERC20 token addresses for each chain, then invoke the omnichain launch function (without passing a single shared suckerDeploymentConfiguration). The system will auto-generate per-chain configurations and verify per-chain token addresses during the launch.

Frequently Asked Questions about jb-omnichain-erc20-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix cross-chain ERC20 token address mismatches when deploying Juicebox V5 omnichain projects?▼

To configure per-chain terminal overrides for Juicebox V5, provide a chainConfigs array where each entry specifies terminalConfigurations with the correct ERC20 token address for that specific chain. This prevents defaulting to NATIVE_TOKEN in Sucker mappings.

Why does my Juicebox V5 Sucker mapping default to NATIVE_TOKEN across multiple chains?▼

Sucker mappings default to NATIVE_TOKEN when per-chain token addresses are not explicitly extracted from approved terminals and accounting contexts. Provide per-chain terminalConfigurations to ensure deployments reflect correct ERC20 addresses across chains.

How do I deploy a Juicebox V5 project across multiple chains with distinct USDC addresses?▼

To deploy across chains like Sepolia and Base Sepolia with distinct USDC addresses, provide per-chain terminalConfigurations in a chainConfigs array, then invoke the omnichain launch function without passing a shared suckerDeploymentConfiguration. The system auto-generates per-chain configurations and verifies token addresses.

Can I specify different ERC20 addresses for each chain in a Juicebox V5 omnichain setup?▼

Yes, you can specify different ERC20 addresses for each chain using per-chain terminal configuration overrides within your chainConfigs array. This enables accurate per-chain token mappings and automated sucker configuration generation for each chain pair.

Do I need to manually pass a suckerDeploymentConfiguration for Juicebox V5 omnichain launches?▼

No, you do not need to manually pass a shared suckerDeploymentConfiguration for Juicebox V5 omnichain launches. The system automatically generates cross-chain sucker deployment configurations when you provide a chainConfigs array with per-chain terminalConfigurations.

Related Skills

Explore More Software Engineering Skills→
widnyanawidnyana
4

evm-decimal-validation

Validate ERC20 token decimals against on-chain values across EVM chains.

Community
Intermediate
EojEdredEojEdred

bridge-dev

Scaffold a Rust pallet-bridge for cross-chain transfers between Flare and Partition chains.

Community
Intermediate
ccashwellccashwell
120

multichain-deployment

Deploy identical protocol addresses across multiple blockchains using deterministic CREATE2 factories.

Community
Advanced
gategate
34

gate-info-riskcheck

Analyzes token contract security and address risk using on-chain data.

Official
Advanced