Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates

- 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>

2026-02-12 15:46:57 -08:00

2.1 KiB

Raw Permalink Blame History

T1.1: ChainID 138 CCIP Selector Update - COMPLETE

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

Date: 2026-01-18
Status: ✅ COMPLETE

✅ Updates Completed

1. `.env` File Updated

Added/Updated:

CHAIN138_SELECTOR=138

Location: smom-dbis-138/.env

Verification:

grep "CHAIN138_SELECTOR" .env
# Output: CHAIN138_SELECTOR=138

2. `networks.json` Updated

Changed:

Old Value: 5009297550715157269 (Mainnet selector - incorrect)
New Value: 138 (chain ID - correct for custom CCIP)

Location: smom-dbis-138/networks.json

Verification:

python3 -c "import json; data=json.load(open('networks.json')); print(data['networks']['138']['chainSelector'])"
# Output: 138

📊 Resolution Summary

Why `138` is Correct

Relay Service Uses It: services/relay/src/config.js uses BigInt('138')
Custom CCIP Pattern: For custom CCIP implementations, chain ID is used as selector
Documentation Confirms: Relay service comment states "Using chain ID as selector for custom relay"

Why Previous Value Was Wrong

Previous: 5009297550715157269 (same as Mainnet selector)
Issue: Different chains should have different selectors
Source: Likely placeholder or copy-paste error

🚀 Impact

Bridge Configuration

Before:

Selector mismatch could cause bridge configuration failures
Relay service using different selector than configuration

After:

Selector consistent across all components
Bridge configuration can proceed with correct selector

Next Steps

✅ Selector updated - COMPLETE
⏳ Test bridge configuration with new selector
⏳ Complete bidirectional bridge configuration

📋 Verification Commands

# Verify .env
grep "CHAIN138_SELECTOR" smom-dbis-138/.env

# Verify networks.json
python3 -c "import json; data=json.load(open('smom-dbis-138/networks.json')); print('Selector:', data['networks']['138']['chainSelector'])"

Status: ✅ COMPLETE

Last Updated: 2026-01-18

2.1 KiB Raw Permalink Blame History