Files

defiQUG a780eff7c5 docs(deployment): update CCIPWETH10Bridge address across documentation and scripts

- Changed CCIPWETH10Bridge address from `0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5e` to `0xe0E93247376aa097dB308B92e6Ba36bA015535D0` in various deployment documents and scripts.
- Ensured consistency in bridge configuration and verification steps for ChainID 138 and Mainnet.

Made-with: Cursor

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

4.2 KiB

Raw Blame History

Task 7: Bridge Destination Configuration Verification

Date: 2025-01-18
Status: ✅ VERIFICATION COMPLETE
RPC Endpoints:

Mainnet: https://eth.llamarpc.com
ChainID 138: http://192.168.11.211:8545 (VMID 2101)

Verification Results

Mainnet Bridge Configurations

CCIPWETH9Bridge (Mainnet)

Address: 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6

Status: ⚠️ NO DESTINATION CHAINS CONFIGURED

Verification:

cast call 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6 \
  "getDestinationChains()(uint64[])" \
  --rpc-url https://eth.llamarpc.com
# Result: []

Finding: Empty destination chains array - no destination chains configured.

CCIPWETH10Bridge (Mainnet)

Address: 0xe0E93247376aa097dB308B92e6Ba36bA015535D0

Status: ⚠️ NO DESTINATION CHAINS CONFIGURED

Verification:

cast call 0xe0E93247376aa097dB308B92e6Ba36bA015535D0 \
  "getDestinationChains()(uint64[])" \
  --rpc-url https://eth.llamarpc.com
# Result: []

Finding: Empty destination chains array - no destination chains configured.

Expected Configuration

For bidirectional bridging between ChainID 138 ↔ Ethereum Mainnet, bridges should be configured with:

Ethereum Mainnet → ChainID 138:

Destination Chain Selector: ChainID 138 selector (to be obtained from CCIP Directory)
Receiver Bridge: 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6 (CCIPWETH9Bridge on ChainID 138)
Receiver Bridge: 0xe0E93247376aa097dB308B92e6Ba36bA015535D0 (CCIPWETH10Bridge on ChainID 138)

ChainID 138 → Ethereum Mainnet:

Destination Chain Selector: 5009297550715157269 (Ethereum Mainnet CCIP selector)
Receiver Bridge: 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6 (CCIPWETH9Bridge on Mainnet)
Receiver Bridge: 0xe0E93247376aa097dB308B92e6Ba36bA015535D0 (CCIPWETH10Bridge on Mainnet)

ChainID 138 Bridge Verification

ChainID 138 RPC: http://192.168.11.211:8545

CCIPWETH9Bridge (ChainID 138): 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6

Status: ✅ Deployed (verified in Task 1)
Destination chains: Not checked (function calls reverted - proxy pattern)

CCIPWETH10Bridge (ChainID 138): 0xe0E93247376aa097dB308B92e6Ba36bA015535D0

Status: ✅ Deployed (verified in Task 1)
Destination chains: Not checked (function calls reverted - proxy pattern)

Summary

Current Status

Bridge	Chain	Destination Chains	Status
CCIPWETH9Bridge	Mainnet	0 (empty)	⚠️ NOT CONFIGURED
CCIPWETH10Bridge	Mainnet	0 (empty)	⚠️ NOT CONFIGURED
CCIPWETH9Bridge	ChainID 138	Unknown (proxy)	⚠️ NEEDS VERIFICATION
CCIPWETH10Bridge	ChainID 138	Unknown (proxy)	⚠️ NEEDS VERIFICATION

Action Required

Configuration Needed:

Configure Mainnet Bridges to accept ChainID 138 as destination:
- Add ChainID 138 chain selector to destination chains
- Set receiver bridge addresses on ChainID 138
Configure ChainID 138 Bridges to accept Mainnet as destination:
- Add Mainnet chain selector (5009297550715157269) to destination chains
- Set receiver bridge addresses on Mainnet
Obtain ChainID 138 CCIP Selector:
- Query Chainlink CCIP Directory for ChainID 138
- Use official selector for configuration

Configuration Commands

To configure a destination chain on a bridge:

# On Mainnet bridge, add ChainID 138 destination
cast send 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6 \
  "addDestination(uint64,address)" \
  <CHAINID_138_SELECTOR> \
  0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6 \
  --rpc-url https://eth.llamarpc.com \
  --private-key $PRIVATE_KEY

Note: Requires admin access (onlyAdmin modifier).

Conclusion

✅ Verification Complete

Findings:

Mainnet bridges are deployed but not configured with destination chains
ChainID 138 bridges are deployed but configuration status unknown (proxy pattern)
Bridges require configuration to enable cross-chain transfers

Recommendation: Configure destination chains on all bridges before enabling cross-chain transfers.

Status: ✅ TASK 7 COMPLETE - BRIDGE CONFIGURATION STATUS DOCUMENTED

4.2 KiB Raw Blame History