a780eff7c5
- 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
258 lines
6.4 KiB
Markdown
258 lines
6.4 KiB
Markdown
# Bidirectional Configuration - Complete Implementation
|
|
|
|
**Date**: 2025-01-18
|
|
**Status**: ✅ **ALL SCRIPTS AND GUIDES COMPLETE**
|
|
|
|
## Summary
|
|
|
|
All scripts and documentation for full bidirectional bridge configuration are complete. The system can now configure both directions:
|
|
- ChainID 138 → Ethereum Mainnet ✅
|
|
- Ethereum Mainnet → ChainID 138 ✅
|
|
|
|
---
|
|
|
|
## Implementation Complete
|
|
|
|
### ✅ Configuration Scripts (5 scripts)
|
|
|
|
1. ✅ **`configure-bridge-destinations.sh`**
|
|
- Full bidirectional configuration
|
|
- Automatically reads selector from networks.json if available
|
|
- Configures both directions in one run
|
|
|
|
2. ✅ **`configure-chain138-to-mainnet.sh`**
|
|
- Configure ChainID 138 → Mainnet only
|
|
- Doesn't require ChainID 138 selector
|
|
- Can run independently
|
|
|
|
3. ✅ **`configure-mainnet-to-chain138.sh`**
|
|
- Configure Mainnet → ChainID 138 only
|
|
- Requires ChainID 138 selector
|
|
- Reads from .env or networks.json
|
|
|
|
4. ✅ **`execute-full-bidirectional-config.sh`**
|
|
- Executes full bidirectional configuration
|
|
- Handles selector detection automatically
|
|
- Orchestrates all configuration steps
|
|
|
|
5. ✅ **`verify-bridge-configuration.sh`**
|
|
- Verifies all bridge configurations
|
|
- Shows current destination status
|
|
- Reports what's configured vs expected
|
|
|
|
---
|
|
|
|
### ✅ Documentation
|
|
|
|
1. ✅ **`BIDIRECTIONAL_CONFIGURATION_GUIDE.md`**
|
|
- Step-by-step configuration guide
|
|
- Selector determination instructions
|
|
- Troubleshooting guide
|
|
|
|
2. ✅ **`CHAIN138_SELECTOR_NOTES.md`**
|
|
- Selector reference documentation
|
|
- Options for selector determination
|
|
- Recommendations
|
|
|
|
3. ✅ **`NEXT_STEPS_EXECUTION_STATUS.md`**
|
|
- Current execution status
|
|
- What can be done now
|
|
- What needs input
|
|
|
|
---
|
|
|
|
## ChainID 138 Selector Status
|
|
|
|
### Current Status
|
|
|
|
**Source**: `networks.json`
|
|
```json
|
|
"chainSelector": "5009297550715157269"
|
|
```
|
|
|
|
**Note**: This is the same selector as Ethereum Mainnet. Options:
|
|
|
|
1. **Use networks.json value**: `5009297550715157269`
|
|
- Configured in the file
|
|
- Scripts will auto-detect this
|
|
|
|
2. **Use chain ID**: `138`
|
|
- For custom CCIP implementations
|
|
- If networks.json value doesn't work
|
|
|
|
3. **Official Chainlink CCIP**: Query CCIP Directory
|
|
- If using official Chainlink CCIP
|
|
- May require ChainID 138 registration
|
|
|
|
---
|
|
|
|
## Execution Options
|
|
|
|
### Option 1: Full Bidirectional (Automated)
|
|
|
|
```bash
|
|
# This script handles everything automatically
|
|
./scripts/configuration/execute-full-bidirectional-config.sh
|
|
```
|
|
|
|
**What it does**:
|
|
1. Configures ChainID 138 → Mainnet
|
|
2. Attempts Mainnet → ChainID 138 (using selector from networks.json)
|
|
3. Verifies configuration
|
|
|
|
### Option 2: Step-by-Step Manual
|
|
|
|
```bash
|
|
# Step 1: Configure ChainID 138 → Mainnet
|
|
./scripts/configuration/configure-chain138-to-mainnet.sh
|
|
|
|
# Step 2: Configure Mainnet → ChainID 138 (if selector available)
|
|
./scripts/configuration/configure-mainnet-to-chain138.sh
|
|
|
|
# Step 3: Verify
|
|
./scripts/configuration/verify-bridge-configuration.sh
|
|
```
|
|
|
|
### Option 3: Use Full Script
|
|
|
|
```bash
|
|
# If selector is in .env or networks.json
|
|
./scripts/configuration/configure-bridge-destinations.sh
|
|
```
|
|
|
|
---
|
|
|
|
## Selector Configuration
|
|
|
|
### Automatic Detection
|
|
|
|
Scripts will try to find selector in this order:
|
|
1. `CHAIN138_SELECTOR` in `.env`
|
|
2. `chainSelector` in `networks.json` (for ChainID 138)
|
|
3. Manual input required if neither available
|
|
|
|
### Manual Configuration
|
|
|
|
```bash
|
|
# Option 1: Add to .env
|
|
echo "CHAIN138_SELECTOR=5009297550715157269" >> .env
|
|
|
|
# Option 2: Use chain ID (for custom CCIP)
|
|
echo "CHAIN138_SELECTOR=138" >> .env
|
|
|
|
# Option 3: Use official Chainlink selector (if obtained)
|
|
echo "CHAIN138_SELECTOR=<official-selector>" >> .env
|
|
```
|
|
|
|
---
|
|
|
|
## Bridge Configuration Matrix
|
|
|
|
### After Full Configuration
|
|
|
|
| Source Chain | Destination Chain | Selector Used | Receiver Bridge | Status |
|
|
|--------------|-------------------|---------------|-----------------|--------|
|
|
| ChainID 138 | Mainnet | `5009297550715157269` | Mainnet Bridge | ⏳ To configure |
|
|
| Mainnet | ChainID 138 | `<CHAIN138_SELECTOR>` | ChainID 138 Bridge | ⏳ To configure |
|
|
|
|
**Bridge Pairs**:
|
|
- WETH9: ChainID 138 `0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6` ↔ Mainnet `0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6`
|
|
- WETH10: ChainID 138 `0xe0E93247376aa097dB308B92e6Ba36bA015535D0` ↔ Mainnet `0x04E1e22B0D41e99f4275bd40A50480219bc9A223`
|
|
|
|
---
|
|
|
|
## Execution Status
|
|
|
|
### ✅ Ready to Execute
|
|
|
|
1. ✅ **ChainID 138 → Mainnet**: Ready (selector known)
|
|
2. ⏳ **Mainnet → ChainID 138**: Ready (selector from networks.json available)
|
|
|
|
### Execution Command
|
|
|
|
```bash
|
|
# Execute full bidirectional configuration
|
|
./scripts/configuration/execute-full-bidirectional-config.sh
|
|
```
|
|
|
|
**Prerequisites**:
|
|
- `PRIVATE_KEY` set in `.env` (or environment)
|
|
- Admin access to bridges
|
|
- RPC endpoints accessible
|
|
|
|
---
|
|
|
|
## Verification After Configuration
|
|
|
|
### Check Configuration
|
|
|
|
```bash
|
|
./scripts/configuration/verify-bridge-configuration.sh
|
|
```
|
|
|
|
### Manual Verification
|
|
|
|
```bash
|
|
# Check Mainnet bridges
|
|
cast call 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6 \
|
|
"getDestinationChains()(uint64[])" \
|
|
--rpc-url https://eth.llamarpc.com
|
|
|
|
# Check ChainID 138 bridges
|
|
cast call 0x3304b747E565a97ec8AC220b0B6A1f6ffDB837e6 \
|
|
"getDestinationChains()(uint64[])" \
|
|
--rpc-url http://192.168.11.211:8545
|
|
```
|
|
|
|
**Expected**: Both bridges should show destination chain selectors in the arrays.
|
|
|
|
---
|
|
|
|
## Troubleshooting
|
|
|
|
### Selector Issues
|
|
|
|
**If selector is incorrect**:
|
|
1. Remove incorrect destination: Use `removeDestination()` function
|
|
2. Reconfigure with correct selector
|
|
3. Verify configuration
|
|
|
|
**If selector causes conflicts**:
|
|
- Check if same selector used for multiple chains
|
|
- Verify selector matches CCIP implementation
|
|
- Test with small transfer first
|
|
|
|
### Configuration Failures
|
|
|
|
**"only admin" error**:
|
|
- Verify `PRIVATE_KEY` has admin access
|
|
- Check admin address: `cast call <BRIDGE> "admin()" --rpc-url <RPC>`
|
|
|
|
**"destination already exists"**:
|
|
- Destination may already be configured
|
|
- Verify with `getDestinationChains()`
|
|
- Remove and re-add if needed
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
✅ **All bidirectional configuration scripts and documentation complete**
|
|
|
|
**Scripts Created**: 5
|
|
- Full bidirectional configuration script
|
|
- Individual direction scripts
|
|
- Verification script
|
|
- Execution orchestration script
|
|
|
|
**Documentation Created**: 3 guides
|
|
- Configuration guide
|
|
- Selector notes
|
|
- Execution status
|
|
|
|
**Status**: ✅ **READY FOR FULL BIDIRECTIONAL CONFIGURATION**
|
|
|
|
---
|
|
|
|
**Next Action**: Run `./scripts/configuration/execute-full-bidirectional-config.sh` to configure both directions.
|