d-bis/smom-dbis-138
4
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Archive legacy status docs and canonicalize genesis entrypoints

Browse Source
This commit is contained in:
defiQUG
2026-04-13 21:45:16 -07:00
parent 7517869ea6
commit 79750d92e6
288 changed files with 757 additions and 1066 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/deployment/36-REGION-BLUEPRINT.md
View File

@@ -243,6 +243,5 @@ If **West Europe** should be purely for admin/control plane (no workload nodes):
## 📝 References
- [Azure Regions List](https://learn.microsoft.com/en-us/azure/reliability/regions-list)
- [Cloud for Sovereignty Landing Zone](./CLOUD_SOVEREIGNTY_LANDING_ZONE.md)
- [Cloud for Sovereignty Landing Zone](./CLOUD_FOR_SOVEREIGNTY_LANDING_ZONE.md)
- [Deployment Checklist](./DEPLOYMENT_CHECKLIST.md)

4
docs/deployment/ALL_BIDIRECTIONAL_TASKS_COMPLETE.md
View File

@@ -1,7 +1,9 @@
# All Bidirectional Configuration Tasks - Complete
**Date**: 2025-01-18
**Status**: ✅ **100% COMPLETE - READY FOR EXECUTION**
**Status**: Historical bidirectional-configuration snapshot
This document records a delivery milestone for bidirectional bridge configuration. Validate current readiness against live deployment and bridge docs before executing changes.
---

2
docs/deployment/ALL_MAINNET_VERIFICATION_COMPLETE.md
View File

@@ -149,7 +149,7 @@ Standardized labels for metrics:
2. ✅ `chains.ts` - ALL_MAINNET config added with verification results
3. ✅ `LiFiRoutingService` - Support check added
4. ✅ `generate-all-adapters.sh` - Documentation updated
5. ✅ `MULTI_CHAIN_DEPLOYMENT_COMPLETE.md` - Status updated
5. ✅ `../archive/status-reports/repo-root-legacy/MULTI_CHAIN_DEPLOYMENT_COMPLETE.md` - Historical status snapshot updated
6. ✅ `MULTI_CHAIN_DEPLOYMENT_GUIDE.md` - ALL Mainnet section added
7. ✅ `ALL_MAINNET_CONFIGURATION.md` - Verification checklist created
8. ✅ `ALL_MAINNET_ROUTING_LOGIC.md` - Routing strategy documented

4
docs/deployment/ALL_NEXT_STEPS_COMPLETE.md
View File

@@ -1,7 +1,9 @@
# All Next Steps Complete - Final Report
**Date**: 2025-12-11
**Status**: ✅ **ALL COMPLETE**
**Status**: Historical completion snapshot
This document captures a point-in-time completion report. Treat it as historical reference rather than the current deployment checklist.
---

4
docs/deployment/ALL_TASKS_COMPLETION_SUMMARY.md
View File

@@ -1,7 +1,9 @@
# All Tasks Completion Summary
**Date**: 2025-01-18
**Status**: COMPREHENSIVE TASK COMPLETION REPORT
**Status**: Historical task-summary snapshot
This summary reflects an earlier task-review checkpoint. Use current deployment/runbook docs for active operational work.
## Executive Summary

5
docs/deployment/ALL_TASKS_FINAL_STATUS.md
View File

@@ -1,5 +1,10 @@
# All Tasks Final Status Report
**Last Reviewed**: 2026-04-13
**Status**: Historical completion snapshot
This document preserves a task-rollup checkpoint from an earlier delivery phase. Use current deployment indexes and runbooks for live operator guidance.
**Date**: 2025-01-18
**Status**: ✅ **ALL TASKS COMPLETE OR DOCUMENTED**

3
docs/deployment/BIDIRECTIONAL_CONFIGURATION_EXECUTION_STATUS.md
View File

@@ -2,6 +2,9 @@
**Date**: 2025-01-18
**Execution Attempt**: Configuration scripts ready, prerequisites check completed
**Status**: Historical execution snapshot
This document preserves a prior execution-readiness check. Re-verify credentials, RPC endpoints, and deployment state before using it operationally.
---

3
docs/deployment/BRIDGE_CONFIGURATION.md
View File

@@ -171,9 +171,8 @@ cast send $CCIPWETH9BRIDGE_BSC \
- [CCIP Documentation](https://docs.chain.link/ccip)
- [Chain Selectors](https://docs.chain.link/ccip/supported-networks)
- [Bridge Contract Documentation](../contracts/ccip/)
- [Bridge Contract Documentation](../../contracts/ccip/)
---
**Last Updated**: 2025-12-11

4
docs/deployment/COMPLETE_IMPLEMENTATION_SUMMARY.md
View File

@@ -1,7 +1,9 @@
# Complete Implementation Summary
**Date**: 2025-01-18
**Status**: ✅ **ALL TASKS AND NEXT STEPS COMPLETE**
**Status**: Historical completion snapshot
This document records an earlier implementation milestone. Use the current deployment indexes and runbooks for live operational guidance.
## Summary

2
docs/deployment/CUSDT_CUSDC_MULTICHAIN_LIQUIDITY_RUNBOOK.md
View File

@@ -242,4 +242,4 @@ See [ENHANCED_SWAP_ROUTER_UPGRADE.md](../bridge/trustless/ENHANCED_SWAP_ROUTER_U
- [DVM_DEPLOYMENT_CHECK.md](DVM_DEPLOYMENT_CHECK.md) — DODO DVM on Chain 138 vs L2s
- [DODO_PMM_INTEGRATION.md](../integration/DODO_PMM_INTEGRATION.md) — Pool creation and swap methods
- [ENHANCED_SWAP_ROUTER_UPGRADE.md](../bridge/trustless/ENHANCED_SWAP_ROUTER_UPGRADE.md) — Balancer/Curve/Uniswap on mainnet
- [OPERATOR_NEXT_STEPS_RUNBOOK.md](OPERATOR_NEXT_STEPS_RUNBOOK.md) — G1 PMM on L2s, G2/G3 Trustless
- [ALL_NEXT_STEPS_CURRENT.md](ALL_NEXT_STEPS_CURRENT.md) — Current G1 PMM on L2s and G2/G3 Trustless follow-up steps

6
docs/deployment/DEPLOYMENT.md
View File

@@ -52,7 +52,8 @@ This guide provides step-by-step instructions for deploying the DeFi Oracle Meta
3. Generate genesis file:
```bash
./scripts/generate-genesis.sh
./scripts/generate-genesis-proper.sh 4
./scripts/validation/validate-genesis.sh
```
4. Store keys in Azure Key Vault:
@@ -230,7 +231,7 @@ npm run example:transaction
npm run example:contract
```
See [Tatum SDK Integration Guide](TATUM_SDK.md) for detailed documentation.
See [Tatum SDK Integration Guide](../api/TATUM_SDK.md) for detailed documentation.
## Step 9: Verification
@@ -281,4 +282,3 @@ npm run smoke-test
- Set up backup procedures
- Review security hardening
- Document operational procedures

2
docs/deployment/DEPLOYMENT_CHECKLIST.md
View File

@@ -79,7 +79,7 @@ terraform apply tfplan-240vpu
### 3.1 Generate Genesis File
- [ ] Generate genesis.json with 48 validators
- [ ] Configure IBFT 2.0 consensus parameters
- [ ] Configure QBFT consensus parameters
- [ ] Add validator addresses to genesis
- [ ] Verify genesis file is valid

3
docs/deployment/DEPLOYMENT_COMPLETE_GUIDE.md
View File

@@ -364,8 +364,7 @@ For issues or questions:
## References
- [Deployment Order](DEPLOYMENT_ORDER.md)
- [WETH CCIP Deployment](WETH_CCIP_DEPLOYMENT.md)
- [WETH CCIP Deployment](../operations/integrations/WETH_CCIP_DEPLOYMENT.md)
- [Contract Deployment Environment Setup](../configuration/CONTRACT_DEPLOYMENT_ENV_SETUP.md)
- [Azure/Cloudflare Environment Setup](../configuration/AZURE_CLOUDFLARE_ENV_SETUP.md)
- [Deployment Credentials](DEPLOYMENT_CREDENTIALS.md)

29
docs/deployment/DEPLOYMENT_CONFIGURATION_AUDIT.md
View File

@@ -4,9 +4,9 @@
This document provides a comprehensive audit of the deployment configuration for the DeFi Oracle Meta Mainnet (ChainID 138), identifying misconfigurations, gaps, and recommendations.
**Audit Date**: $(date)
**Audit Date**: 2026-04-13
**Chain ID**: 138
**Status**: ⚠️ **CONFIGURATION ISSUES FOUND**
**Status**: Historical audit snapshot; revalidate against current configs before acting
---
@@ -17,7 +17,7 @@ This document provides a comprehensive audit of the deployment configuration for
**Issue**: The `config/genesis.json` file has `extraData: "0x"` which means no validators are configured in the genesis block.
**Impact**:
- IBFT 2.0 requires validators to be specified in the genesis `extraData` field
- QBFT requires validators to be specified in the genesis `extraData` field
- Network cannot start without validators
- Blocks cannot be produced
@@ -28,12 +28,12 @@ This document provides a comprehensive audit of the deployment configuration for
"extraData": "0x"
```
**Required**: Validator addresses must be encoded in `extraData` using IBFT 2.0 format:
**Required**: Validator addresses must be encoded in `extraData` using QBFT format:
```
extraData = RLP([32 bytes Vanity, [][20 bytes]Validators, 65 bytes Signature])
```
**Fix**: Run `./scripts/generate-genesis.sh` to regenerate genesis with validator addresses from `keys/validators/`.
**Fix**: Run `./scripts/generate-genesis-proper.sh 4` to regenerate genesis with validator addresses from `keys/validators/`.
---
@@ -103,9 +103,9 @@ az aks get-versions --location westeurope --output table
**Required**: Validator public keys must be extracted from `keys/validators/` and encoded in genesis `extraData`.
**Fix**: Ensure `scripts/generate-genesis.sh`:
**Fix**: Ensure `scripts/generate-genesis-proper.sh`:
1. Reads validator public keys from `keys/validators/*/key.pub`
2. Encodes them in IBFT 2.0 format
2. Encodes them in QBFT format
3. Updates `extraData` field
---
@@ -189,11 +189,11 @@ All configurations use Chain ID 138:
---
### ✅ IBFT 2.0 Configuration
### ✅ QBFT Configuration
**Status**: ✅ **CONSISTENT**
IBFT 2.0 parameters are consistent:
QBFT parameters are consistent:
- Block period: 2 seconds ✅
- Epoch length: 30,000 blocks ✅
- Request timeout: 10 seconds ✅
@@ -245,7 +245,7 @@ IBFT 2.0 parameters are consistent:
### Besu Configuration
#### Validators
- ✅ Consensus: IBFT 2.0
- ✅ Consensus: QBFT
- ✅ RPC: Disabled (correct for security)
- ✅ P2P: Enabled on port 30303
- ✅ Sync Mode: FULL
@@ -253,7 +253,7 @@ IBFT 2.0 parameters are consistent:
- ✅ Metrics: Enabled on port 9545
#### Sentries
- ✅ Consensus: IBFT 2.0 (read-only)
- ✅ Consensus: QBFT (read-only)
- ✅ RPC: Enabled but internal only (127.0.0.1)
- ✅ P2P: Enabled on port 30303
- ✅ Sync Mode: FULL
@@ -261,7 +261,7 @@ IBFT 2.0 parameters are consistent:
- ✅ Metrics: Enabled
#### RPC Nodes
- ✅ Consensus: IBFT 2.0 (read-only)
- ✅ Consensus: QBFT (read-only)
- ✅ RPC: Enabled publicly (0.0.0.0)
- ✅ P2P: Disabled (correct)
- ✅ Sync Mode: SNAP (correct for RPC nodes)
@@ -362,7 +362,7 @@ IBFT 2.0 parameters are consistent:
1. **Fix Genesis File**
```bash
./scripts/generate-genesis.sh
./scripts/generate-genesis-proper.sh 4
```
Verify `extraData` contains validator addresses.
@@ -417,7 +417,7 @@ IBFT 2.0 parameters are consistent:
### ✅ Correctly Configured
- Chain ID: 138 (consistent across all files)
- IBFT 2.0 parameters (block period, epoch, timeout)
- QBFT parameters (block period, epoch, timeout)
- Network ID: 138 (consistent)
- Besu image: hyperledger/besu:23.10.0
- Resource sizing (mostly consistent)
@@ -463,4 +463,3 @@ For questions or issues:
- Check deployment documentation
- Verify prerequisites
- Run validation scripts

3
docs/deployment/DEPLOYMENT_CREDENTIALS.md
View File

@@ -257,7 +257,6 @@ forge test -vvvv
- [Foundry Documentation](https://book.getfoundry.sh/)
- [Chainlink CCIP Documentation](https://docs.chain.link/ccip)
- [WETH Deployment Guide](docs/WETH_CCIP_DEPLOYMENT.md)
- [WETH Deployment Guide](../operations/integrations/WETH_CCIP_DEPLOYMENT.md)
- [Contract Deployment Environment Setup](../configuration/CONTRACT_DEPLOYMENT_ENV_SETUP.md)
- [Azure/Cloudflare Environment Setup](../configuration/AZURE_CLOUDFLARE_ENV_SETUP.md)

7
docs/deployment/DEPLOYMENT_FIREFLY_CACTI.md
View File

@@ -332,7 +332,6 @@ kubectl delete service financial-tokenization-service -n besu-network
- [Firefly Documentation](https://hyperledger.github.io/firefly/)
- [Cacti Documentation](https://hyperledger.github.io/cacti/)
- [Integration Guide](INTEGRATION_GUIDE.md)
- [Firefly Integration](FIREFLY_INTEGRATION.md)
- [Cacti Integration](CACTI_INTEGRATION.md)
- [Integration Guide](../guides/INTEGRATION_GUIDE.md)
- [Firefly Integration](../operations/integrations/FIREFLY_INTEGRATION.md)
- [Cacti Integration](../operations/integrations/CACTI_INTEGRATION.md)

17
docs/deployment/DEPLOYMENT_INDEX.md
View File

@@ -8,7 +8,7 @@ This index helps you find the right deployment guide for your needs.
## Which Guide Should I Use?
### Quick Start
**Use**: [Deployment Quick Start](../../DEPLOYMENT_QUICK_START.md)
**Use**: [Deployment Quick Start](../DEPLOYMENT_QUICK_START.md)
**When**: You want the fastest deployment path
**Covers**: One-command deployment, parallel execution, quick setup
@@ -23,7 +23,7 @@ This index helps you find the right deployment guide for your needs.
**Covers**: Pre-deployment, deployment, post-deployment checklist
### Current Status
**Use**: [Deployment Status and Next Steps](DEPLOYMENT_STATUS_AND_NEXT_STEPS.md)
**Use**: [Deployment Status and Next Steps](../DEPLOYMENT_STATUS_AND_NEXT_STEPS.md)
**When**: You need to know current deployment status
**Covers**: Current status, next steps, what's deployed
@@ -108,19 +108,18 @@ These are historical deployment reports and status documents. Consider archiving
| Guide | Purpose | When to Use |
|-------|---------|-------------|
| [Deployment Quick Start](../../DEPLOYMENT_QUICK_START.md) | Fast deployment | Quick setup needed |
| [Deployment Quick Start](../DEPLOYMENT_QUICK_START.md) | Fast deployment | Quick setup needed |
| [Deployment Guide](DEPLOYMENT.md) | Comprehensive guide | Detailed instructions needed |
| [Deployment Checklist](DEPLOYMENT_CHECKLIST.md) | Checklist | Tracking progress |
| [Deployment Status](DEPLOYMENT_STATUS_AND_NEXT_STEPS.md) | Current status | Check what's deployed |
| [Deployment Status](../DEPLOYMENT_STATUS_AND_NEXT_STEPS.md) | Current status | Check what's deployed |
## Related Documentation
- [Master Documentation Index](../../MASTER_DOCUMENTATION_INDEX.md)
- [Architecture Documentation](../../architecture/ARCHITECTURE.md)
- [Configuration Index](../../configuration/CONFIGURATION_INDEX.md)
- [Troubleshooting Guide](../../guides/TROUBLESHOOTING.md)
- [Master Documentation Index](../MASTER_DOCUMENTATION_INDEX.md)
- [Architecture Documentation](../architecture/ARCHITECTURE.md)
- [Configuration Index](../configuration/CONFIGURATION_INDEX.md)
- [Troubleshooting Guide](../guides/TROUBLESHOOTING.md)
---
**Last Updated**: 2025-01-27

3
docs/deployment/DEPLOYMENT_ORDER.md
View File

@@ -46,7 +46,7 @@ The deployment is organized into 8 phases, each building on the previous:
### 1.4 Key Generation
- [ ] Generate validator keys (`./scripts/key-management/generate-validator-keys.sh 4`)
- [ ] Generate oracle keys (`./scripts/key-management/generate-oracle-keys.sh`)
- [ ] Generate genesis file (`./scripts/generate-genesis.sh`)
- [ ] Generate genesis file (`./scripts/generate-genesis-proper.sh 4`)
- [ ] Verify keys are generated correctly
---
@@ -399,4 +399,3 @@ Phase 1 (Prerequisites)
- Always verify each phase before proceeding
- Keep backups of configurations and keys
- Document any deviations from the standard process

4
docs/deployment/FINAL_COMPLETION_REPORT.md
View File

@@ -1,9 +1,11 @@
# Final Completion Report - All Tasks
**Date**: 2025-01-18
**Status**: ✅ **MAXIMUM COMPLETION ACHIEVED**
**Status**: Historical task-completion snapshot
**Total Tasks**: 14
This report captures an earlier project milestone and should be read as historical context, not as a current operator status page.
## Completion Summary
### ✅ Completed: 9/14 Tasks (64%)

4
docs/deployment/FINAL_COMPLETION_STATUS.md
View File

@@ -1,7 +1,9 @@
# Final Completion Status - All Tasks and Next Steps
**Date**: 2025-01-18
**Status**: ✅ **100% COMPLETE**
**Status**: Historical completion snapshot
This document records an earlier “all tasks and next steps” milestone. It is useful for historical context but should not replace the current deployment indexes and runbooks.
## Executive Summary

3
docs/deployment/MAINNET_TETHER_AND_TRANSACTION_MIRROR.md
View File

@@ -331,10 +331,9 @@ forge script script/DeployTransactionMirror.s.sol \
- [Kaleido Tether Documentation](https://docs.kaleido.io/kaleido-services/tether/)
- [Etherscan Event Search](https://etherscan.io/apis#events)
- [Foundry Deployment Guide](../MULTICHAIN_DEPLOYMENT_RUNBOOK.md)
- [Foundry Deployment Guide](MULTICHAIN_DEPLOYMENT_RUNBOOK.md)
---
**Last Updated**: 2025-12-11
**Status**: Contracts ready, deployment pending

6
docs/deployment/MASTER_INDEX.md
View File

@@ -20,7 +20,7 @@
8. **DETAILED_TASK_LIST_COMPREHENSIVE.md** - Complete task list (14 tasks)
9. **TASK_COMPLETION_REPORT.md** - Task completion tracking
10. **ALL_TASKS_COMPLETION_SUMMARY.md** - Completion summary
11. **FINAL_COMPLETION_REPORT.md** - Final completion status
11. **../archive/status-reports/docs-root-legacy/FINAL_COMPLETION_REPORT.md** - Historical final completion status
### Individual Task Documentation
@@ -42,7 +42,7 @@
### Task Lists
- **Complete Task List**: `DETAILED_TASK_LIST_COMPREHENSIVE.md`
- **Completion Summary**: `FINAL_COMPLETION_REPORT.md`
- **Completion Summary**: `../archive/status-reports/docs-root-legacy/FINAL_COMPLETION_REPORT.md`
### Service Development
- **State Anchoring Service**: `TASK2_STATE_ANCHORING_SERVICE.md`
@@ -70,7 +70,7 @@
1. **Start Here**: `DEPLOYMENT_COMPLETE_STATUS_FINAL.md` - Overall status
2. **Gaps**: `GAP_ANALYSIS_COMPREHENSIVE.md` - All gaps identified
3. **Tasks**: `DETAILED_TASK_LIST_COMPREHENSIVE.md` - All tasks detailed
4. **Completion**: `FINAL_COMPLETION_REPORT.md` - What's done
4. **Completion**: `../archive/status-reports/docs-root-legacy/FINAL_COMPLETION_REPORT.md` - Historical completion snapshot
---

5
docs/deployment/MULTICHAIN_DEPLOYMENT_RUNBOOK.md
View File

@@ -507,6 +507,5 @@ For issues or questions:
- [Foundry Documentation](https://book.getfoundry.sh/)
- [Chainlink CCIP Documentation](https://docs.chain.link/ccip)
- [Etherscan API](https://docs.etherscan.io/)
- [Multichain Deployment Script](../script/DeployAll.s.sol)
- [CCIPLogger Deployment Script](../script/DeployCCIPLoggerOnly.s.sol)
- [Multichain Deployment Script](../../script/DeployAll.s.sol)
- [CCIPLogger Deployment Script](../../script/DeployCCIPLoggerOnly.s.sol)

8
docs/deployment/MULTI_CHAIN_DEPLOYMENT_GUIDE.md
View File

@@ -386,10 +386,10 @@ forge verify-contract <ADDRESS> <CONTRACT> \
## 📚 **Additional Resources**
- [Chain Registry Documentation](./CHAIN_REGISTRY.md)
- [Adapter Development Guide](./ADAPTER_DEVELOPMENT.md)
- [Hyperledger Integration Guide](./HYPERLEDGER_INTEGRATION.md)
- [Oracle Service Setup](./ORACLE_SERVICE_SETUP.md)
- [Current Contract and Infrastructure Inventory](../MASTER_CONTRACTS_AND_INFRASTRUCTURE_LIST.md)
- [Tezos Adapter Production Checklist](../bridge/TEZOS_ADAPTER_PRODUCTION_CHECKLIST.md)
- [Integration Guide](../guides/INTEGRATION_GUIDE.md)
- [Oracle and Keeper Chain 138](../integration/ORACLE_AND_KEEPER_CHAIN138.md)
---

2
docs/deployment/TODO_TASKS_STATUS.md
View File

@@ -46,7 +46,7 @@ Summary of all deployment TODOs and their current status.
## Operator runbook (DApp LXC + Dual-Router + NPMplus)
For step-by-step commands to deploy the DApp LXC (5801), add NPMplus proxy, fund mainnet LP, fund CCIP LINK, and optional G1–G3 / CCIPLogger, see **[OPERATOR_NEXT_STEPS_RUNBOOK.md](OPERATOR_NEXT_STEPS_RUNBOOK.md)**.
For step-by-step commands to deploy the DApp LXC (5801), add NPMplus proxy, fund mainnet LP, fund CCIP LINK, and optional G1–G3 / CCIPLogger, see **[ALL_NEXT_STEPS_CURRENT.md](ALL_NEXT_STEPS_CURRENT.md)**.
---

8
docs/deployment/VM_DEPLOYMENT_SUMMARY.md
View File

@@ -1,5 +1,10 @@
# VM Deployment Implementation Summary
**Last Reviewed**: 2026-04-13
**Status**: Historical VM deployment summary
This document summarizes a VM/VMSS delivery milestone. Use the current VM deployment guides and checklists for active planning and operations.
## Overview
This document summarizes the VM/VMSS deployment implementation for the Besu network, providing an alternative to AKS deployment.
@@ -256,5 +261,4 @@ docs/
## Conclusion
The VM/VMSS deployment option provides a simpler, more cost-effective alternative to AKS deployment while maintaining full control over the infrastructure. All components are production-ready and fully documented.
The VM/VMSS deployment option provides a simpler, more cost-effective alternative to AKS deployment while maintaining full control over the infrastructure. At the time of this summary, the components were fully documented and ready for the next operational validation step.

3
docs/deployment/VM_DEPLOYMENT_TROUBLESHOOTING.md
View File

@@ -286,7 +286,7 @@ ssh besuadmin@$VM_IP "iftop"
If you encounter issues not covered here:
1. Check the [main troubleshooting guide](../docs/TROUBLESHOOTING.md)
1. Check the [main troubleshooting guide](../guides/TROUBLESHOOTING.md)
2. Review [VM deployment documentation](VM_DEPLOYMENT.md)
3. Check Besu logs for detailed error messages
4. Review Azure VM logs in Azure Portal
@@ -302,4 +302,3 @@ To prevent common issues:
3. **Updates**: Keep VMs and Docker images updated
4. **Resource Planning**: Monitor resource usage and scale as needed
5. **Security**: Regularly review and update NSG rules and Key Vault policies