Files

defiQUG d02ee71cf6 Update CCIP Router and Bridge Addresses for ChainID 138

- Changed CCIP Router address from `0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5e` to `0x42DAb7b888Dd382bD5Adcf9E038dBF1fD03b4817` across multiple documentation files.
- Updated WETH9 Bridge address from `0x89dd12025bfCD38A168455A44B400e913ED33BE2` to `0xcacfd227A040002e49e2e01626363071324f820a`.
- Ensured all references to the new addresses are consistent throughout the documentation.

This update reflects the latest deployment configurations and ensures accurate contract references for ChainID 138.

2026-03-24 22:49:29 -07:00

3.6 KiB

Raw Blame History

LINK Token Search Results - ChainID 138

Date: 2025-01-12
Status: ❌ NO EXISTING LINK TOKEN FOUND

Search Summary

Comprehensive search for existing LINK token on ChainID 138 was performed using multiple methods. No existing LINK token was found.

Search Methods Used

Method 1: CCIP Router Fee Token ✅

Router: 0x42DAb7b888Dd382bD5Adcf9E038dBF1fD03b4817
Query: getFeeToken() / feeToken()
Result: ⚠️ Returns address 0x000000000000000000000000514910771af9ca65...
Finding: Router references Ethereum Mainnet LINK address (0x514910771AF9Ca656af840dff83E8264EcF986CA) but contract does NOT exist at this address on ChainID 138

Method 2: Known LINK Addresses ✅

Checked the following addresses:

0x514910771AF9Ca656af840dff83E8264EcF986CA (Ethereum Mainnet canonical) - ❌ No contract
0x326C977E6efc84E512bB9C30f76E30c160eD06FB (Expected address) - ❌ No contract
0x73ADaF7dBa95221c080db5631466d2bC54f6a76B (Previous attempt) - ❌ No contract
0xd6969bC19b53f866C64f2148aE271B2Dae0C58E4 (Recent deployment) - ❌ No contract
0x07dE1f489E1bfCE2c326066a9DFc10e731CBA0CB (Previous attempt) - ❌ No contract

Result: None of the known addresses have deployed contracts.

Method 3: Bridge Contract References ✅

WETH9 Bridge: 0xcacfd227A040002e49e2e01626363071324f820a
WETH10 Bridge: 0xe0E93247376aa097dB308B92e6Ba36bA015535D0
Query: linkToken() / getLinkToken()
Result: ⚠️ Bridge contracts don't expose LINK token reference methods

Method 4: Recent Contract Deployments ⚠️

Method: Scan last 100 blocks for contract creations
Status: Search attempted but incomplete (syntax error in scanning loop)
Note: Would require more sophisticated block scanning

Key Findings

1. CCIP Router Configuration

Router is configured to use LINK token for fees
Router references Ethereum Mainnet LINK address
Problem: The referenced address doesn't exist on ChainID 138

2. No Pre-Deployed LINK Token

Genesis configuration checked
No LINK token in pre-deployed contracts
Only WETH9, WETH10, and Multicall are pre-deployed

3. No Recent Deployments

Recent deployment attempts have not confirmed
Network appears to have issues with contract creation transactions

Conclusion

No existing LINK token was found on ChainID 138.

The CCIP Router is configured to use LINK (0x514910771AF9Ca656af840dff83E8264EcF986CA) for fees, but this contract does not exist on ChainID 138.

Recommendations

Option 1: Deploy LINK Token (Recommended)

Deploy a LINK token contract to ChainID 138:

Use MockLinkToken or standard ERC20 implementation
Deploy with high gas (20+ gwei)
Wait for network confirmation
Update all configurations with deployed address

Option 2: Use Native ETH for Fees

If CCIP Router supports native ETH:

Check if router accepts address(0) for fees
Update configurations to use native ETH
No LINK token deployment needed

Option 3: Bridge LINK from Ethereum Mainnet

If bridging is available:

Bridge LINK tokens from Ethereum Mainnet
May require LINK token deployment on ChainID 138 first

Next Steps

Deploy LINK Token

./scripts/force-deploy-link.sh $(cast --to-wei 20 gwei)

Wait for Confirmation
- Monitor deployment transaction
- Verify contract bytecode
- Update configurations
Complete Setup
- Mint tokens
- Fund bridges
- Update token lists
- Run database migration

Last Updated: 2025-01-12
Status: ❌ No existing LINK token found - deployment required

3.6 KiB Raw Blame History