- 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
146 lines
3.8 KiB
Markdown
146 lines
3.8 KiB
Markdown
# Bidirectional Bridge Configuration - Final Status
|
|
|
|
**Date**: 2025-01-18
|
|
**Status**: ✅ **PARTIALLY COMPLETE**
|
|
|
|
---
|
|
|
|
## Configuration Summary
|
|
|
|
### ✅ Mainnet → ChainID 138 (COMPLETE)
|
|
|
|
**Status**: ✅ **SUCCESSFULLY CONFIGURED**
|
|
|
|
| Bridge | Address | Destination Selector | Status |
|
|
|--------|---------|---------------------|--------|
|
|
| CCIPWETH9Bridge | `0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6` | `5009297550715157269` | ✅ Configured |
|
|
| CCIPWETH10Bridge | `0xe0E93247376aa097dB308B92e6Ba36bA015535D0` | `5009297550715157269` | ✅ Configured |
|
|
|
|
**Result**: Both Mainnet bridges can now send to ChainID 138 ✅
|
|
|
|
### ⚠️ ChainID 138 → Mainnet (BLOCKED)
|
|
|
|
**Status**: ⚠️ **EXECUTION REVERTED**
|
|
|
|
**Error**: `Execution reverted` when attempting to configure ChainID 138 bridges
|
|
|
|
**Possible Causes**:
|
|
1. Proxy pattern - Direct contract calls may not work
|
|
2. Destination already exists
|
|
3. Different contract interface on ChainID 138
|
|
4. Validation failing on ChainID 138 contracts
|
|
|
|
**Investigation Needed**:
|
|
- Check if destinations already configured via proxy
|
|
- Verify contract interface matches
|
|
- Check admin permissions on ChainID 138 contracts
|
|
|
|
---
|
|
|
|
## Current Configuration State
|
|
|
|
### Mainnet Bridges ✅
|
|
|
|
- **WETH9 Bridge**: Destination `5009297550715157269` configured
|
|
- **WETH10 Bridge**: Destination `5009297550715157269` configured
|
|
|
|
**Verification**:
|
|
```bash
|
|
cast call 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6 \
|
|
"getDestinationChains()(uint64[])" \
|
|
--rpc-url https://eth.llamarpc.com
|
|
# Result: [5009297550715157269] ✅
|
|
```
|
|
|
|
### ChainID 138 Bridges ⚠️
|
|
|
|
- **WETH9 Bridge**: Configuration attempted but reverted
|
|
- **WETH10 Bridge**: Configuration attempted but reverted
|
|
|
|
**Status**: Unknown (may be proxy pattern issue)
|
|
|
|
---
|
|
|
|
## Technical Details
|
|
|
|
### Admin Verification
|
|
|
|
- **Address**: `0x4A666F96fC8764181194447A7dFdb7d471b301C8`
|
|
- **Mainnet**: ✅ Verified as admin
|
|
- **ChainID 138**: ⏳ Needs verification
|
|
|
|
### Chain Selectors
|
|
|
|
- **Mainnet**: `5009297550715157269` ✅
|
|
- **ChainID 138**: `5009297550715157269` (from networks.json)
|
|
|
|
### RPC Endpoints
|
|
|
|
- **Mainnet**: `https://eth.llamarpc.com` ✅
|
|
- **ChainID 138**: `http://192.168.11.211:8545` ✅
|
|
|
|
---
|
|
|
|
## What Was Accomplished
|
|
|
|
✅ **PRIVATE_KEY configured** in `.env`
|
|
✅ **RPC endpoints fixed** and verified
|
|
✅ **Mainnet → ChainID 138 configuration completed** (2 transactions)
|
|
✅ **Scripts executed successfully** for Mainnet direction
|
|
✅ **Verification tools working**
|
|
|
|
---
|
|
|
|
## Remaining Work
|
|
|
|
### ChainID 138 → Mainnet Configuration
|
|
|
|
**Issue**: Execution reverted when configuring ChainID 138 bridges
|
|
|
|
**Next Steps**:
|
|
1. Investigate proxy pattern on ChainID 138
|
|
2. Check if destinations already exist via different method
|
|
3. Verify contract ABI/interface on ChainID 138
|
|
4. Check if different admin address needed for ChainID 138
|
|
5. Consider manual configuration via explorer or different tool
|
|
|
|
---
|
|
|
|
## Success Metrics
|
|
|
|
| Metric | Status |
|
|
|--------|--------|
|
|
| PRIVATE_KEY configured | ✅ |
|
|
| RPC endpoints working | ✅ |
|
|
| Mainnet → ChainID 138 | ✅ 100% |
|
|
| ChainID 138 → Mainnet | ⚠️ 0% (blocked) |
|
|
| **Overall Progress** | **50% (1 of 2 directions)** |
|
|
|
|
---
|
|
|
|
## Documentation
|
|
|
|
All configuration scripts and documentation are complete:
|
|
|
|
- ✅ `execute-full-bidirectional-config.sh`
|
|
- ✅ `configure-bridge-destinations.sh`
|
|
- ✅ `configure-chain138-to-mainnet.sh`
|
|
- ✅ `configure-mainnet-to-chain138.sh`
|
|
- ✅ `verify-bridge-configuration.sh`
|
|
- ✅ `check-prerequisites.sh`
|
|
- ✅ `BIDIRECTIONAL_CONFIGURATION_GUIDE.md`
|
|
- ✅ `BIDIRECTIONAL_READY_FOR_EXECUTION.md`
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
✅ **Mainnet → ChainID 138**: Successfully configured
|
|
⚠️ **ChainID 138 → Mainnet**: Blocked by execution revert
|
|
|
|
**Next Action**: Investigate ChainID 138 bridge contract interface/proxy pattern to complete bidirectional configuration.
|
|
|
|
---
|
|
|
|
**Status**: ✅ **50% COMPLETE - ONE DIRECTION CONFIGURED**
|