Files
explorer-monorepo/docs/LINK_TOKEN_DEPLOYMENT_FIX_REPORT.md

3.4 KiB

LINK Token Deployment Fix Report

Date: 2025-01-12
Issue: LINK token deployment not confirming on network


Problem Analysis

Symptoms

  • Deployment transactions sent successfully (nonce advanced)
  • Contract not appearing at expected address
  • Multiple deployment attempts not confirming
  • Network is operational (blocks producing)

Root Cause Investigation

  1. Transaction Status: Nonce advanced to 42, indicating transactions were processed
  2. Contract Address: 0x0cb0192C056aa425C557BdeAD8E56C7eEabf7acF shows no bytecode
  3. Network Health: Blocks producing normally (151,450+)
  4. Possible Causes:
    • Deployment transactions failing/reverting silently
    • Network-specific deployment restrictions
    • Gas price too low (though we used 2-3 gwei)
    • Contract creation opcode restrictions

Solutions Attempted

Method 1: forge script with --broadcast

  • Transaction sent
  • Contract not confirmed

Method 2: forge create with explicit gas

  • Transaction sent
  • Contract not confirmed

Method 3: cast send --create with bytecode

  • Transaction sent
  • Contract not confirmed

Method 4: Higher gas price (3 gwei)

  • Transaction sent
  • Waiting for confirmation

Option 1: Check Block Explorer (Immediate)

Action: Check transaction status on block explorer

  • URL: https://explorer.d-bis.org
  • Search account: 0x4A666F96fC8764181194447A7dFdb7d471b301C8
  • Review recent transactions
  • Check for revert reasons

Action: Check if LINK token already exists on chain

  • Standard LINK: 0x514910771AF9Ca656af840dff83E8264EcF986CA
  • CCIP Router fee token
  • Pre-deployed tokens

Status:

  • Script created: scripts/diagnose-link-deployment.sh
  • Automatically checks known LINK addresses
  • Verifies token functions (name, symbol, balanceOf)
  • Updates .env automatically if found
  • ⚠️ Note: Standard LINK token typically does NOT have a public mint() function
  • ⚠️ If balance is low, LINK must be acquired from exchange/faucet

Option 3: Deploy via Remix IDE

Action: Use Remix IDE for deployment

  1. Go to https://remix.ethereum.org
  2. Deploy MockLinkToken contract
  3. Network: ChainID 138
  4. RPC: http://192.168.11.250:8545

Option 4: Check Network Restrictions

Action: Verify network allows contract creation

  • Check if CREATE opcode is enabled
  • Verify network configuration
  • Check for deployment restrictions

Current Status

Completed

  • Multiple deployment attempts made
  • Transactions sent successfully
  • Higher gas prices tried
  • All deployment methods attempted

Pending

  • Network confirmation of deployment
  • Contract bytecode verification
  • Token minting
  • Bridge funding

Next Steps

  1. Check Block Explorer

    • Verify transaction status
    • Check for revert reasons
    • Identify actual deployment address if different
  2. Wait for Network

    • Some networks have delayed confirmation
    • Wait additional time (5-10 minutes)
  3. Alternative Deployment

    • Use Remix IDE
    • Use Hardhat
    • Use different deployment method
  4. Network Investigation

    • Check if contract creation is restricted
    • Verify network configuration
    • Contact network administrators if needed

Last Updated: 2025-01-12
Status: Deployment pending network confirmation