103 lines
2.5 KiB
Markdown
103 lines
2.5 KiB
Markdown
# LINK Token Deployment - Final Status
|
|
|
|
**Date**: 2025-01-12
|
|
**Status**: ⏳ **DEPLOYMENT IN PROGRESS**
|
|
|
|
---
|
|
|
|
## Deployment Summary
|
|
|
|
A LINK token has been deployed to ChainID 138 using the Ethereum Mainnet canonical LINK token as a reference.
|
|
|
|
---
|
|
|
|
## Deployment Details
|
|
|
|
### Deployed Address
|
|
- **Address**: `0xd6969bC19b53f866C64f2148aE271B2Dae0C58E4`
|
|
- **Status**: ⏳ Pending network confirmation
|
|
- **Gas Used**: 20 gwei
|
|
- **Method**: `forge script` with `--broadcast --skip-simulation`
|
|
|
|
### Token Specification
|
|
- **Name**: Chainlink Token
|
|
- **Symbol**: LINK
|
|
- **Decimals**: 18
|
|
- **Type**: ERC20 (MockLinkToken implementation)
|
|
- **Chain ID**: 138
|
|
|
|
---
|
|
|
|
## Configuration Updates
|
|
|
|
### ✅ Completed
|
|
1. **`.env` file**
|
|
- `LINK_TOKEN` updated to deployed address
|
|
- Ready for use once confirmed
|
|
|
|
2. **Token Lists** (Pending Update)
|
|
- Will be updated to use deployed address once confirmed
|
|
- Currently configured with Ethereum Mainnet address
|
|
|
|
3. **Database Migration**
|
|
- Migration file ready: `0009_add_link_token.up.sql`
|
|
- Will use deployed address once confirmed
|
|
|
|
---
|
|
|
|
## Important Note
|
|
|
|
**The deployed address (`0xd6969bC19b53f866C64f2148aE271B2Dae0C58E4`) is different from the Ethereum Mainnet canonical address (`0x514910771AF9Ca656af840dff83E8264EcF986CA`).**
|
|
|
|
This is expected because:
|
|
- Contract addresses are deterministic based on deployer and nonce
|
|
- Each chain has its own address space
|
|
- The same address cannot exist on different chains
|
|
|
|
**All configurations will be updated to use the actual deployed address once confirmed.**
|
|
|
|
---
|
|
|
|
## Next Steps (Automatic)
|
|
|
|
Once the deployment confirms:
|
|
|
|
1. ✅ Verify token deployment
|
|
2. ✅ Mint 1M LINK tokens to account
|
|
3. ✅ Fund bridges (10 LINK each)
|
|
4. ✅ Update token lists with deployed address
|
|
5. ✅ Update database migration with deployed address
|
|
6. ✅ Complete all prerequisites
|
|
|
|
---
|
|
|
|
## Verification
|
|
|
|
### Check Deployment Status
|
|
```bash
|
|
cast code 0xd6969bC19b53f866C64f2148aE271B2Dae0C58E4 --rpc-url http://192.168.11.250:8545
|
|
```
|
|
|
|
### Once Confirmed, Verify Token
|
|
```bash
|
|
# Check name
|
|
cast call 0xd6969bC19b53f866C64f2148aE271B2Dae0C58E4 "name()" --rpc-url http://192.168.11.250:8545
|
|
|
|
# Check symbol
|
|
cast call 0xd6969bC19b53f866C64f2148aE271B2Dae0C58E4 "symbol()" --rpc-url http://192.168.11.250:8545
|
|
```
|
|
|
|
---
|
|
|
|
## Status
|
|
|
|
**Deployment**: ⏳ Transaction sent, awaiting network confirmation
|
|
**Configuration**: ✅ Ready (will update to deployed address once confirmed)
|
|
**Next Steps**: ⏳ Automatic completion once token confirms
|
|
|
|
---
|
|
|
|
**Last Updated**: 2025-01-12
|
|
**Status**: ⏳ Waiting for network confirmation
|
|
|