Files
smom-dbis-138/docs/deployment/CHAIN138_DEPLOYMENT_COMPLETE.md
defiQUG 1fb7266469 Add Oracle Aggregator and CCIP Integration
- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control.
- Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities.
- Created .gitmodules to include OpenZeppelin contracts as a submodule.
- Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment.
- Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks.
- Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring.
- Created scripts for resource import and usage validation across non-US regions.
- Added tests for CCIP error handling and integration to ensure robust functionality.
- Included various new files and directories for the orchestration portal and deployment scripts.
2025-12-12 14:57:48 -08:00

86 lines
2.2 KiB
Markdown

# Chain-138 Deployment Complete Guide
## ✅ Completed Steps
### 1. Environment Configuration
- ✅ Added `CHAIN138_RPC_URL` to `.env`
- ✅ Added `CHAIN138_SELECTOR` to `.env`
- ✅ Added placeholder for `CCIP_CHAIN138_ROUTER`
- ✅ Added placeholder for `CHAIN138_CCIP_REPORTER`
### 2. Genesis File
- ✅ Checked for `genesis.json`
- ✅ Verified WETH9/WETH10 predeployment configuration
### 3. Infrastructure Verification
- ✅ Created verification scripts
- ✅ RPC connectivity testing
- ✅ Chain ID verification
### 4. Contract Deployment Preparation
- ✅ CCIPTxReporter deployment script ready
- ✅ Hardhat configuration for Chain-138
## 📋 Remaining Steps
### Infrastructure Deployment (if not already deployed)
```bash
# Deploy Kubernetes resources
kubectl apply -k k8s/base
# Deploy Besu validators
helm install besu-validators ./helm/besu-network -f helm/besu-network/values-validators.yaml -n besu-network
# Deploy Besu sentries
helm install besu-sentries ./helm/besu-network -f helm/besu-network/values-sentries.yaml -n besu-network
# Deploy Besu RPC nodes
helm install besu-rpc ./helm/besu-network -f helm/besu-network/values-rpc.yaml -n besu-network
```
### Contract Deployment
```bash
# Deploy CCIPTxReporter to Chain-138
npm run deploy:reporter:chain138
# Or manually:
npx hardhat run scripts/ccip-deployment/deploy-ccip-reporter.js --network chain138
```
### Verification
```bash
# Run complete verification
./scripts/deployment/verify-chain138-complete.sh
# Or individual checks:
./scripts/deployment/verify-chain138-full-deployment.sh
./scripts/deployment/verify-chain138-services.sh
./scripts/deployment/cross-check-chain138.sh
```
## 🔧 Configuration Files
### .env Updates Needed
After deployment, update `.env` with:
- `CHAIN138_CCIP_REPORTER=<deployed_address>`
- `CCIP_CHAIN138_ROUTER=<router_address>` (if using custom router)
## 📊 Status Check
Run the deployment script to check current status:
```bash
./scripts/deployment/deploy-chain138-complete.sh
```
## ✅ Verification Checklist
- [ ] RPC endpoint accessible
- [ ] Chain ID correct (138)
- [ ] Blocks being produced
- [ ] WETH9 predeployed
- [ ] WETH10 predeployed
- [ ] CCIPTxReporter deployed
- [ ] CCIP Router configured
- [ ] Services running
- [ ] Monitoring active