smom-dbis-138/docs/deployment/DETAILED_TASK_LIST_COMPREHENSIVE.md

Detailed Task List - Complete Deployment and Testing

Date: 2025-01-18
Status: TASK LIST COMPLETE
Purpose: Comprehensive list of all tasks to complete gaps, missing components, and placeholders

Task Categories

• 🔴 Critical - Required for core functionality
• 🟡 Medium - Important for full operation
• 🟢 Low - Enhancements and optional items

---

🔴 CRITICAL PRIORITY TASKS

Task 1: Verify ChainID 138 Contracts

Priority: 🔴 Critical
Status: ⏳ Pending RPC Access
Estimated Time: 30 minutes

Description: Verify on-chain status of CCIPWETH9Bridge and CCIPWETH10Bridge on ChainID 138.

Steps:

1. Set up ChainID 138 RPC access:

   • Option A: Use public RPC: https://rpc-http-pub.d-bis.org
   • Option B: Use permissioned RPC: https://rpc-http-prv.d-bis.org
   • Option C: Configure network access to http://192.168.11.250:8545

2. Verify CCIPWETH9Bridge on ChainID 138:

   cast code 0x89dd12025bfCD38A168455A44B400e913ED33BE2 --rpc-url $RPC_URL_138
   cast call 0x89dd12025bfCD38A168455A44B400e913ED33BE2 "admin()" --rpc-url $RPC_URL_138
   cast call 0x89dd12025bfCD38A168455A44B400e913ED33BE2 "weth9()" --rpc-url $RPC_URL_138
   

3. Verify CCIPWETH10Bridge on ChainID 138:

   cast code 0xe0E93247376aa097dB308B92e6Ba36bA015535D0 --rpc-url $RPC_URL_138
   cast call 0xe0E93247376aa097dB308B92e6Ba36bA015535D0 "admin()" --rpc-url $RPC_URL_138
   cast call 0xe0E93247376aa097dB308B92e6Ba36bA015535D0 "weth10()" --rpc-url $RPC_URL_138
   

4. Verify bridge destination configurations:

   cast call $BRIDGE_ADDRESS "destinations(uint64)" $DEST_SELECTOR --rpc-url $RPC_URL_138
   

5. Document verification results in CHAIN138_VERIFICATION_RESULTS.md

Dependencies: ChainID 138 RPC access
Output: Verification report confirming contract status

---

Task 2: Develop Off-Chain State Anchoring Service

Priority: 🔴 Critical
Status: ⏳ Not Started
Estimated Time: 2-4 days

Description: Create service to collect state proofs from ChainID 138 validators and submit them to MainnetTether contract.

Requirements:

• Connect to ChainID 138 RPC to monitor blocks
• Collect validator signatures for state proofs
• Aggregate signatures according to MainnetTether requirements
• Submit anchorStateProof() calls to MainnetTether contract
• Handle replay protection (check if state proof already exists)
• Monitor submission success/failure
• Retry logic for failed submissions
• Logging and alerting

Implementation Options:

1. Node.js/TypeScript service with ethers.js
2. Python service with web3.py
3. Go service with go-ethereum

Steps:

1. Design service architecture and data flow
2. Create service repository/structure
3. Implement ChainID 138 block monitoring
4. Implement validator signature collection
5. Implement state proof aggregation
6. Implement MainnetTether contract interaction
7. Implement replay protection checking
8. Add error handling and retry logic
9. Add logging and monitoring
10. Create deployment configuration
11. Test with testnet/mainnet
12. Deploy service

Contract Interaction:

• MainnetTether: 0x15DF1D5BFDD8Aa4b380445D4e3E9B38d34283619
• Function: anchorStateProof(uint256, bytes32, bytes32, bytes32, uint256, bytes, uint256)

Dependencies: ChainID 138 RPC access, Mainnet RPC access, MainnetTether contract deployed
Output: Deployed state anchoring service

---

Task 3: Develop Off-Chain Transaction Mirroring Service

Priority: 🔴 Critical
Status: ⏳ Not Started
Estimated Time: 2-3 days

Description: Create service to monitor ChainID 138 transactions and mirror them to TransactionMirror contract on Mainnet.

Requirements:

• Connect to ChainID 138 RPC to monitor transactions
• Extract transaction data (hash, from, to, value, block, gas, success, data)
• Batch transactions (up to 100 per call)
• Submit mirrorTransaction() or mirrorTransactionsBatch() to TransactionMirror
• Handle batch size limits
• Monitor submission success/failure
• Retry logic for failed submissions
• Logging and alerting

Implementation Options:

1. Node.js/TypeScript service with ethers.js
2. Python service with web3.py
3. Go service with go-ethereum

Steps:

1. Design service architecture and data flow
2. Create service repository/structure
3. Implement ChainID 138 transaction monitoring
4. Implement transaction data extraction
5. Implement transaction batching (respect MAX_BATCH_SIZE = 100)
6. Implement TransactionMirror contract interaction
7. Add error handling and retry logic
8. Add logging and monitoring
9. Create deployment configuration
10. Test with testnet/mainnet
11. Deploy service

Contract Interaction:

• TransactionMirror: 0x4CF42c4F1dBa748601b8938be3E7ABD732E87cE9
• Functions: mirrorTransaction(...), mirrorTransactionsBatch(...)

Dependencies: ChainID 138 RPC access, Mainnet RPC access, TransactionMirror contract deployed
Output: Deployed transaction mirroring service

---

Task 4: Perform Cross-Chain Integration Testing

Priority: 🔴 Critical
Status: ⏳ Pending RPC Access
Estimated Time: 4-8 hours

Description: Test complete end-to-end cross-chain bridge flow between ChainID 138 and Ethereum Mainnet.

Steps:

1. Set up ChainID 138 RPC access

2. Fund test wallet on both chains

3. Test wrap ETH to WETH9 on ChainID 138:

   cast send $WETH9_ADDRESS "deposit()" --value 0.1ether --rpc-url $RPC_URL_138 --private-key $PRIVATE_KEY
   

4. Test approve bridge to spend WETH9:

   cast send $WETH9_ADDRESS "approve(address,uint256)" $BRIDGE_ADDRESS $(cast --to-uint256 0.1ether) --rpc-url $RPC_URL_138 --private-key $PRIVATE_KEY
   

5. Test bridge WETH9 from ChainID 138 to Mainnet:

   cast send $BRIDGE_ADDRESS "bridgeTokens(uint256,uint64,bytes)" $(cast --to-uint256 0.1ether) $MAINNET_SELECTOR $RECIPIENT_BYTES --rpc-url $RPC_URL_138 --private-key $PRIVATE_KEY --value $CCIP_FEE
   

6. Verify tokens received on Mainnet

7. Test bridge back from Mainnet to ChainID 138

8. Verify tokens received on ChainID 138

9. Test multiple destinations (if configured)

10. Document test results

Test Script Available: explorer-monorepo/scripts/test-end-to-end-bridge.sh

Dependencies: ChainID 138 RPC access, Mainnet RPC access, funded wallets
Output: Cross-chain test report

---

🟡 MEDIUM PRIORITY TASKS

Task 5: Host Token List Publicly

Priority: 🟡 Medium
Status: ⏳ Not Started
Estimated Time: 1-2 hours

Description: Host MetaMask token list publicly for automatic token discovery.

Steps:

1. Review token list: metamask-integration/docs/METAMASK_TOKEN_LIST.json

2. Validate token list format and contents

3. Choose hosting option:

   • Option A: GitHub Pages (free, easy)
   • Option B: IPFS (decentralized)
   • Option C: CDN (fast, reliable)
   • Option D: Project website

4. Host token list at public URL

5. Verify token list is accessible

6. Test token list import in MetaMask

7. Register token list with MetaMask (optional, for automatic discovery)

8. Update documentation with token list URL

Token List Contents:

• WETH9 with decimals: 18
• WETH10 with decimals: 18
• Oracle price feed token

Dependencies: None
Output: Public URL for token list

---

Task 6: Verify TransactionMirror on Etherscan

Priority: 🟡 Medium
Status: ⏳ Pending Verification
Estimated Time: 15 minutes

Description: Manually verify TransactionMirror contract on Etherscan if auto-verification failed.

Steps:

1. Check Etherscan for TransactionMirror verification status:

   • URL: https://etherscan.io/address/0x4CF42c4F1dBa748601b8938be3E7ABD732E87cE9

2. If not verified, run manual verification:

   forge verify-contract --chain-id 1 \
     --num-of-optimizations 200 --via-ir \
     0x4CF42c4F1dBa748601b8938be3E7ABD732E87cE9 \
     contracts/mirror/TransactionMirror.sol:TransactionMirror \
     $ETHERSCAN_API_KEY \
     --constructor-args $(cast abi-encode "constructor(address)" 0x4A666F96fC8764181194447A7dFdb7d471b301C8)
   

3. Verify verification succeeded on Etherscan

4. Update documentation with verification status

Dependencies: Etherscan API key, contract source code
Output: Verified contract on Etherscan

---

Task 7: Verify Bridge Destination Configurations

Priority: 🟡 Medium
Status: ⏳ Pending RPC Access
Estimated Time: 1-2 hours

Description: Verify bridge contracts are configured with correct destination chain selectors and receiver addresses.

Steps:

1. Set up ChainID 138 RPC access

2. Get destination chain selectors:

   • Ethereum Mainnet: 5009297550715157269 (from networks.json)

3. Verify CCIPWETH9Bridge destinations on ChainID 138:

   cast call $WETH9_BRIDGE_138 "destinations(uint64)" $MAINNET_SELECTOR --rpc-url $RPC_URL_138
   

4. Verify CCIPWETH9Bridge destinations on Mainnet:

   cast call $WETH9_BRIDGE_MAINNET "destinations(uint64)" $CHAIN138_SELECTOR --rpc-url $MAINNET_RPC
   

5. Verify CCIPWETH10Bridge destinations on both chains

6. Verify destination addresses match expected bridge addresses

7. Test fee calculation for each destination

8. Document configuration results

Expected Configurations:

• ChainID 138 → Ethereum Mainnet
• Ethereum Mainnet → ChainID 138
• Potentially: BSC, Polygon, Avalanche, Base, Arbitrum, Optimism

Dependencies: ChainID 138 RPC access, Mainnet RPC access
Output: Bridge configuration verification report

---

Task 8: Verify Environment Variables

Priority: 🟡 Medium
Status: ⏳ Pending .env Access
Estimated Time: 30 minutes

Description: Verify all required environment variables are set in .env file.

Required Variables:

Mainnet Configuration

• ETHEREUM_MAINNET_RPC - Mainnet RPC URL
• PRIVATE_KEY - Deployment private key
• ETHERSCAN_API_KEY - Etherscan API key for verification
• WETH9_MAINNET - Should be 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
• WETH10_MAINNET - Should be 0xf4BB2e28688e89fCcE3c0580D37d36A7672E8A9f
• CCIP_ROUTER_MAINNET - Should be 0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D
• LINK_TOKEN_MAINNET - Should be 0x514910771AF9Ca656af840dff83E8264EcF986CA

ChainID 138 Configuration

• RPC_URL_138 or equivalent - ChainID 138 RPC URL
• CCIP_ROUTER_138 - CCIP Router address on ChainID 138
• LINK_TOKEN_138 - LINK token address on ChainID 138

Optional Deployment Admin

• TETHER_ADMIN - Optional (defaults to deployer)
• MIRROR_ADMIN - Optional (defaults to deployer)
• BRIDGE_L1_TOKEN - Required for TwoWayBridge deployment
• BRIDGE_L2_TOKEN - Required for TwoWayBridge deployment

Steps:

1. Check .env file exists
2. Verify all required variables are set (no placeholders)
3. Verify no TBD, TODO, YOUR_KEY placeholders
4. Verify addresses match expected values
5. Verify RPC URLs are correct and accessible
6. Document any missing variables
7. Create .env.example template if missing

Dependencies: Access to .env file
Output: Environment variable verification report

---

Task 9: Verify Ledger App-Ethereum RPC Endpoints

Priority: 🟡 Medium
Status: ⏳ Pending Verification
Estimated Time: 30 minutes

Description: Verify RPC endpoints in Ledger app-ethereum configuration match current infrastructure.

Current Configuration:

• File: pr-workspace/app-ethereum/src/network.c (line 42)
• Chain ID: 138 ✅
• Name: "Defi Oracle Meta" ✅
• Ticker: "ETH" ✅

Steps:

1. Check pr-workspace/app-ethereum/src/network.c for RPC endpoint configuration
2. Search for RPC URL settings in app-ethereum configuration files
3. Verify RPC endpoints match:
   • Public: https://rpc-http-pub.d-bis.org
   • Permissioned: https://rpc-http-prv.d-bis.org
4. Update RPC endpoints if needed
5. Verify configuration compilation if app needs rebuild
6. Document RPC endpoint configuration

Dependencies: Access to app-ethereum repository
Output: Ledger app RPC configuration verification report

---

🟢 LOW PRIORITY / OPTIONAL TASKS

Task 10: Determine TwoWayTokenBridge Deployment Status

Priority: 🟢 Low
Status: ⏳ Decision Needed
Estimated Time: 1 hour

Description: Determine if TwoWayTokenBridge contracts are required or if MainnetTether/TransactionMirror provide sufficient functionality.

Analysis Required:

1. Review TwoWayTokenBridge contract functionality
2. Compare with MainnetTether/TransactionMirror functionality
3. Determine use cases for each
4. Decide if TwoWayTokenBridge deployment is needed

Options:

• Option A: Deploy TwoWayTokenBridge if different functionality needed
• Option B: Skip deployment if MainnetTether/TransactionMirror sufficient

Steps:

1. Review contracts/bridge/TwoWayTokenBridgeL1.sol
2. Review contracts/bridge/TwoWayTokenBridgeL2.sol
3. Compare with MainnetTether and TransactionMirror functionality
4. Document decision with rationale
5. If deploying:
   • Set BRIDGE_L1_TOKEN and BRIDGE_L2_TOKEN in .env
   • Deploy TwoWayTokenBridge contracts
6. If not deploying:
   • Document why MainnetTether/TransactionMirror are sufficient

Dependencies: None
Output: Decision document and deployment status

---

Task 11: Determine MirrorManager Deployment Status

Priority: 🟢 Low
Status: ⏳ Decision Needed
Estimated Time: 1 hour

Description: Determine if MirrorManager contract is required for the system.

Analysis Required:

1. Review MirrorManager contract functionality
2. Determine if cross-chain address registry is needed
3. Compare with direct address mapping approach
4. Decide if MirrorManager deployment is needed

Steps:

1. Review contracts/mirror/MirrorManager.sol
2. Determine use cases for address mirroring
3. Evaluate if direct address mapping is sufficient
4. Document decision with rationale
5. If deploying:
   • Set MIRROR_ADMIN in .env (multisig recommended)
   • Deploy MirrorManager contract
6. If not deploying:
   • Document why not needed

Dependencies: None
Output: Decision document and deployment status

---

Task 12: Check CCIPLogger Deployment Status

Priority: 🟢 Low
Status: ⏳ Status Unknown
Estimated Time: 30 minutes

Description: Check if CCIPLogger is deployed and document status.

Steps:

1. Check .env file for CCIP_LOGGER_MAINNET or similar
2. Check deployment logs for CCIPLogger deployment
3. Check Etherscan for deployer address contract creation events
4. If deployed, document address and verification status
5. If not deployed, document why (optional vs required)
6. Update deployment status documentation

Dependencies: Access to .env and deployment logs
Output: CCIPLogger deployment status document

---

Task 13: Fix Compilation Issue (If Needed)

Priority: 🟢 Low
Status: ⏳ Optional
Estimated Time: 1-2 hours

Description: Fix identifier conflict in script/bridge/trustless/InitializeBridgeSystem.s.sol if full project compilation is needed.

Issue: Identifier conflict preventing full forge build and forge test.

Note: Does not affect deployed contracts. Previous tests show 215-350+ tests passing.

Steps:

1. Review error in script/bridge/trustless/InitializeBridgeSystem.s.sol
2. Identify conflicting identifiers
3. Fix conflicts (use aliases, remove duplicates, fix namespaces)
4. Test compilation: forge build --via-ir
5. Run tests: forge test --via-ir
6. Document fix

Dependencies: None (if not needed)
Output: Fixed compilation issue (if addressed)

---

Task 14: Perform Performance and Load Testing

Priority: 🟢 Low
Status: ⏳ Not Started
Estimated Time: 4-8 hours

Description: Perform performance and load testing on deployed contracts.

Tests Required:

1. Multiple simultaneous bridge transactions
2. Batch operations performance
3. Gas cost analysis
4. Contract response times
5. State synchronization performance

Steps:

1. Set up test environment
2. Fund test wallets
3. Execute multiple simultaneous bridge transactions
4. Measure gas costs and response times
5. Test batch operations (TransactionMirror batching)
6. Test state anchoring performance
7. Document performance metrics
8. Identify bottlenecks if any

Dependencies: ChainID 138 RPC access, Mainnet RPC access, funded wallets
Output: Performance test report

---

Task Summary

By Priority

Priority	Count	Status
🔴 Critical	4	0 Complete, 4 Pending
🟡 Medium	5	0 Complete, 5 Pending
🟢 Low	5	0 Complete, 5 Pending
Total	14	0 Complete, 14 Pending

By Dependency

Dependency	Tasks	Status
RPC Access Required	Tasks 1, 4, 7	Pending RPC access
Service Development	Tasks 2, 3	Not started
No Dependencies	Tasks 5, 6, 8, 9, 10, 11, 12, 13, 14	Can start immediately

---

Execution Order

Phase 1: No Dependencies (Can Start Immediately)

1. Task 5: Host token list publicly
2. Task 6: Verify TransactionMirror on Etherscan
3. Task 8: Verify environment variables
4. Task 9: Verify Ledger app RPC endpoints
5. Task 10: Determine TwoWayTokenBridge status
6. Task 11: Determine MirrorManager status
7. Task 12: Check CCIPLogger status

Phase 2: Requires RPC Access

8. Task 1: Verify ChainID 138 contracts
9. Task 4: Perform cross-chain integration testing
10. Task 7: Verify bridge destination configurations

Phase 3: Service Development (Critical)

11. Task 2: Develop off-chain state anchoring service
12. Task 3: Develop off-chain transaction mirroring service

Phase 4: Enhancements (Optional)

13. Task 13: Fix compilation issue (if needed)
14. Task 14: Perform performance and load testing

---

Documentation Requirements

Each task should produce:

• Implementation/execution documentation
• Verification results
• Test results (if applicable)
• Updated status in main deployment documentation

---

Completion Criteria

Critical Tasks

• ChainID 138 contracts verified
• Off-chain state anchoring service deployed and operational
• Off-chain transaction mirroring service deployed and operational
• Cross-chain integration testing completed

Medium Priority Tasks

• Token list hosted publicly
• TransactionMirror verified on Etherscan
• Bridge destinations verified
• Environment variables verified
• Ledger app RPC endpoints verified

Low Priority Tasks

• TwoWayTokenBridge deployment decision documented
• MirrorManager deployment decision documented
• CCIPLogger status documented
• Compilation issue resolved (if needed)
• Performance testing completed (if needed)

---

Last Updated: 2025-01-18
Status: Task list complete, awaiting execution