fbda1b4beb
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>
2.4 KiB
2.4 KiB
LINK Token Decision for Phase 3 Deployment
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Date: 2026-01-18
Status: ✅ DECISION: USE EXISTING LINK TOKEN
✅ Recommended Approach
Use Existing LINK Token: 0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03
Why This Makes Sense
- ✅ Already Deployed: Contract exists and verified (3,779 bytes)
- ✅ Sufficient Supply: ~999,980 LINK available
- ✅ Configured: Already in
.envasLINK_TOKEN - ✅ Compatible: Same interface as canonical LINK (ERC20)
- ✅ Ready: No deployment needed - can proceed immediately
Current Configuration
# smom-dbis-138/.env
LINK_TOKEN=0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03
CCIP_FEE_TOKEN=0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03
❌ Why Not Deploy Canonical Address
Canonical Address: 0x514910771AF9Ca656af840dff83E8264EcF986CA
Challenges:
- ❌ CREATE2 Required: Cannot deploy to exact address using standard CREATE
- ❌ Complex Setup: Requires CREATE2Factory + salt calculations
- ❌ Unnecessary: Existing LINK token works perfectly for CCIP fees
- ❌ Time Consuming: Would delay Phase 3 deployment
Status: Address is empty on ChainID 138 (confirmed)
🚀 Action Plan
For Phase 3 Bridge Deployment:
-
✅ Verify LINK Token (already done):
cast code 0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03 \ --rpc-url http://192.168.11.211:8545 -
✅ Verify Supply (already done):
- ~999,980 LINK available at deployer address
-
✅ Configuration Ready (already done):
LINK_TOKENset in.envCCIP_FEE_TOKENset in.env
-
✅ Proceed with Bridge Deployment:
- Use existing LINK token for fee payments
- No deployment needed
📋 Summary
| Aspect | Status | Notes |
|---|---|---|
| Existing LINK Token | ✅ Ready | 0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03 |
| Canonical Address | ❌ Empty | Would require CREATE2 |
| Token Supply | ✅ Sufficient | ~999,980 LINK |
| Configuration | ✅ Complete | Already in .env |
| Deployment Needed | ❌ No | Ready to use |
Decision: ✅ USE EXISTING LINK TOKEN - Proceed with Phase 3 bridge deployment.
Status: ✅ DECISION MADE - READY FOR PHASE 3
Last Updated: 2026-01-18