- Changed CCIP Router address from `0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5e` to `0x42DAb7b888Dd382bD5Adcf9E038dBF1fD03b4817` across multiple documentation files. - Updated WETH9 Bridge address from `0x89dd12025bfCD38A168455A44B400e913ED33BE2` to `0xcacfd227A040002e49e2e01626363071324f820a`. - Ensured all references to the new addresses are consistent throughout the documentation. This update reflects the latest deployment configurations and ensures accurate contract references for ChainID 138.
3.9 KiB
3.9 KiB
Deployment Status Update
Date: 2025-12-24
Status: In Progress - Critical and High Priority Tasks
✅ Completed Tasks
Critical Priority
-
✅ CCIPReceiver Verification
- Address:
0x6C4BEE679d37629330daeF141BEd5b4eD2Ec14f6 - Status: Verified on-chain
- Code Size: 6,749 bytes
- Router:
0x42DAb7b888Dd382bD5Adcf9E038dBF1fD03b4817 - Oracle:
0x99b3511a2d315a497c8112c1fdd8d508d4b1e506
- Address:
-
✅ OpenZeppelin Contracts Installation
- Status: Installed and updated
- Location:
smom-dbis-138/lib/openzeppelin-contracts - Remappings: Verified
High Priority - Deployed
-
✅ MultiSig Deployment
- Address:
0x39A9550a7c4ec6aa9dac43D7eC9fd67BaF570AAA - Status: Deployed and verified
- Method: Direct deployment via
cast send - Transaction:
0x57526db7cde104c4053ea65c95140cadf7f04854a67fb4562bee66db07ff9c2b
- Address:
-
✅ Voting Deployment
- Address:
0x83CcE6938FfE5F95FAd3043038C9b94Fdf666495 - Status: Deployed and verified
- Method: Direct deployment via
cast send - Transaction:
0x883ab08f88b95ca1a66079945ca8943154f057b7cb20ec76b872c86b505ae1f0
- Address:
-
✅ ReserveSystem Deployment
- Address:
0x9062656Ef121068CfCeB89FA3178432944903428 - Status: Deployed and verified
- Method: Direct deployment via
cast send - Transaction:
0x84a4672fcb25f5b558ec0fa715b0912a57e55b04cc00ec9c89749a492974865a
- Address:
⏳ In Progress
High Priority - Deploying
- ⏳ TokenFactory138 Deployment
- Status: Deploying...
- Method: Direct deployment via
cast sendwith--via-ir - Note: Requires
--via-irdue to stack too deep issues
❌ Blocked / Needs Attention
Missing Contracts
-
❌ CompliantUSDT
- Status: Contract file not found
- Issue: Contract doesn't exist in
contracts/tokens/directory - Action: Need to create contract file first
-
❌ CompliantUSDC
- Status: Contract file not found
- Issue: Contract doesn't exist in
contracts/tokens/directory - Action: Need to create contract file first
-
❌ ComplianceRegistry (LegallyCompliantBase)
- Status: Contract file not found
- Issue: Contract doesn't exist in
contracts/compliance/directory - Action: Need to create contract file first
eMoney System Contracts
- ⏳ eMoney System Contracts
- Status: Deployment script ran but contracts not on-chain
- Issue: Script reported success but code size only 3 bytes
- Addresses Reported:
- ComplianceRegistry:
0x013AF3A3958388a9DE9Cd15D3E2D29769D909787 - DebtRegistry:
0x39A9550a7c4ec6aa9dac43D7eC9fd67BaF570AAA - PolicyManager:
0x83CcE6938FfE5F95FAd3043038C9b94Fdf666495 - eMoneyToken Implementation:
0x41ec240D46c7217D57BdD02663Cb97078917A9d5 - TokenFactory138:
0x9062656Ef121068CfCeB89FA3178432944903428 - BridgeVault138:
0x6DEA30284A279b76E175effE91843A414a5603e8
- ComplianceRegistry:
- Action: Need to deploy individually via
cast sendwith proper gas limits
🔧 Deployment Method
All successful deployments used direct deployment via cast send --create due to gas limit issues with forge script.
Command Pattern:
cast send --private-key $PRIVATE_KEY \
--rpc-url $RPC_URL \
--legacy \
--gas-price 20000000000 \
--gas-limit 10000000 \
--create "$BYTECODE$CONSTRUCTOR_ARGS"
📊 Summary
- Critical Tasks: 2/2 ✅ Complete
- High Priority Deployed: 3/12 ✅
- High Priority In Progress: 1/12 ⏳
- High Priority Blocked: 3/12 ❌
- High Priority Pending: 5/12 ⏳
🎯 Next Steps
- Continue deploying TokenFactory138
- Deploy remaining eMoney system contracts individually
- Create missing CompliantUSDT, CompliantUSDC, ComplianceRegistry contracts
- Continue with medium priority tasks
Last Updated: 2025-12-24