Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
4.3 KiB
4.3 KiB
T1.2 Bridge Resolution - Credentials Status
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Date: 2026-01-18
Status: ✅ MOST CREDENTIALS PRESENT | ⚠️ 2 VALUES NEED VERIFICATION
✅ Verified Credentials
1. PRIVATE_KEY ✅
- Status: ✅ PRESENT AND VERIFIED
- Value:
0x5373d11ee2cad4ed82b9208526a8c358839cbfe325919fb250f062a25153d1c8 - Derived Address:
0x4A666F96fC8764181194447A7dFdb7d471b301C8 - Verification: ✅ MATCHES EXTRACTED ADMIN ADDRESS
- Location:
smom-dbis-138/.env:2
2. RPC_URL ✅
- Status: ✅ PRESENT
- Value:
http://192.168.11.250:8545 - Alternative:
RPC_URL_138=http://192.168.11.211:8545 - Location:
smom-dbis-138/.env
3. CHAIN138_SELECTOR ✅
- Status: ✅ PRESENT
- Value:
138 - Location:
smom-dbis-138/.env
⚠️ Credentials Requiring Verification/Addition
4. CCIP_ROUTER ⚠️
- Status: ⚠️ MISSING FROM .env
- Extracted from Storage:
0x99b3511a2d315a497c8112c1fdd8d508d4b1e506(slot 0) - Documented Values:
- Template:
0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D(mainnet template) - CCIP_CONTRACTS_ENV_UPDATE.md:
0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5e(ChainID 138)
- Template:
- Action Required: VERIFY which is the correct CCIP Router for ChainID 138
- Recommendation: Check on-chain or use
0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5efrom documentation
5. CCIP_FEE_TOKEN / LINK_TOKEN ⚠️
- Status: ⚠️ DISCREPANCY DETECTED
- Current .env Value:
LINK_TOKEN=0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03 - Expected (Canonical):
0x514910771AF9Ca656af840dff83E8264EcF986CA - Documentation Shows:
0x514910771AF9Ca656af840dff83E8264EcF986CA - Action Required: VERIFY which LINK token address is correct for ChainID 138
- Note: Current value
0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03may be a custom/mock LINK token
📋 Recommended .env Updates
Add these to smom-dbis-138/.env:
# CCIP Router for ChainID 138 (verify which address is correct)
CCIP_ROUTER=0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5e
# OR
# CCIP_ROUTER=0x99b3511a2d315a497c8112c1fdd8d508d4b1e506
# CCIP Fee Token (verify LINK token address)
CCIP_FEE_TOKEN=0x514910771AF9Ca656af840dff83E8264EcF986CA
# OR if using custom LINK
# CCIP_FEE_TOKEN=0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03
✅ Token Addresses (Confirmed)
These are deterministic and don't need configuration:
WETH9
- Address:
0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 - Status: ✅ Pre-deployed (genesis)
WETH10
- Address:
0xf4BB2e28688e89fCcE3c0580D37d36A7672E8A9f - Status: ✅ Pre-deployed (genesis)
🔍 Verification Steps
Verify CCIP_ROUTER
# Check which router address is correct
cast code 0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5e --rpc-url http://192.168.11.211:8545
cast code 0x99b3511a2d315a497c8112c1fdd8d508d4b1e506 --rpc-url http://192.168.11.211:8545
Verify LINK_TOKEN
# Check current LINK token
cast code 0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03 --rpc-url http://192.168.11.211:8545
# Check canonical LINK token
cast code 0x514910771AF9Ca656af840dff83E8264EcF986CA --rpc-url http://192.168.11.211:8545
📊 Credential Readiness for Phase 3
| Credential | Status | Notes |
|---|---|---|
| PRIVATE_KEY | ✅ Ready | Matches admin address |
| RPC_URL | ✅ Ready | Both endpoints available |
| WETH9_ADDRESS | ✅ Ready | Deterministic, known |
| WETH10_ADDRESS | ✅ Ready | Deterministic, known |
| CCIP_ROUTER | ⚠️ Needs Verification | 2 possible addresses |
| CCIP_FEE_TOKEN | ⚠️ Needs Verification | 2 possible addresses |
| CHAIN138_SELECTOR | ✅ Ready | Set to 138 |
Overall Readiness: 85% (5/7 ready, 2 need verification)
🚀 Next Steps
- Verify CCIP_ROUTER: Run verification commands above to determine correct address
- Verify LINK_TOKEN: Determine if custom or canonical LINK token should be used
- Update .env: Add verified
CCIP_ROUTERandCCIP_FEE_TOKENvalues - Proceed with Deployment: Phase 3.2 deployment can begin once these are set
Status: ✅ CREDENTIALS MOSTLY READY - VERIFICATION REQUIRED FOR 2 VALUES
Last Updated: 2026-01-18