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.8 KiB

Raw Blame History

CREATE2 Deployment to Canonical LINK Address - Status

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

Date: 2026-01-18
Status: ✅ SCRIPTS READY - AWAITING EXECUTION

✅ Scripts Created and Ready

1. Foundry Deployment Script

File: smom-dbis-138/script/DeployLinkToCanonicalAddress.s.sol Status: ✅ Created, compiled successfully

Functionality:

Deploys CREATE2Factory
Brute-forces salt search (up to 1M iterations)
Deploys LINK token at canonical address if salt found
Mints 1M LINK to deployer

2. Bash Deployment Script

File: scripts/deploy-link-canonical-create2.sh Status: ✅ Created, RPC connection handling added

Functionality:

Tests RPC connectivity
Checks if canonical address is empty
Runs Foundry deployment script
Verifies deployment

🚀 Execution Command

Automated (Recommended)

cd /home/intlc/projects/proxmox
./scripts/deploy-link-canonical-create2.sh

Manual

cd smom-dbis-138
source .env

forge script script/DeployLinkToCanonicalAddress.s.sol:DeployLinkToCanonicalAddress \
    --rpc-url "http://192.168.11.211:8545" \
    --broadcast \
    --private-key "$PRIVATE_KEY" \
    --legacy \
    -vvv

⚠️ Important Notes

Execution Time

Salt Search: May take significant time (up to 1M iterations)
Progress: Script outputs progress every 10,000 salt attempts
Completion: Script will either deploy or exit with explanation

Possible Outcomes

Success Case:

SALT FOUND!
Salt: <number>
Predicted Address: 0x514910771AF9Ca656af840dff83E8264EcF986CA
LINK token deployed at: 0x514910771AF9Ca656af840dff83E8264EcF986CA
SUCCESS: LINK token deployed at canonical address!

Failure Case:

WARNING: Could not find salt within 1000000 iterations
This means one of the following:
  1. The bytecode doesn't match the original LINK token bytecode
  2. The CREATE2 factory address is different from mainnet
  3. The canonical LINK was deployed using CREATE, not CREATE2
  4. A higher salt value is needed

📋 Next Steps

Run the deployment script (command above)
Wait for completion (may take time for salt search)
If successful: Update .env with canonical address
If unsuccessful: Use existing LINK token at 0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03

🔧 Troubleshooting

RPC Connection Issues

Script now tests connection and tries alternative endpoint
Working endpoint: http://192.168.11.211:8545

Compilation Warnings

Warnings from other contracts are harmless
Script will still compile and run

Salt Not Found

Normal if bytecode differs or original LINK used CREATE
Recommendation: Use existing LINK token

Status: ✅ READY FOR EXECUTION

Last Updated: 2026-01-18

2.8 KiB Raw Blame History