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

feat: bridges, PMM, flash workflow, token-aggregation, and deployment docs

Browse Source 
- CCIP/trustless bridge contracts, GRU tokens, DEX/PMM tests, reserve vault.
- Token-aggregation service routes, planner, chain config, relay env templates.
- Config snapshots and multi-chain deployment markdown updates.
- gitignore services/btc-intake/dist/ (tsc output); do not track dist.

Run forge build && forge test before deploy (large solc graph).

Made-with: Cursor
This commit is contained in:
defiQUG
2026-04-07 23:40:52 -07:00
parent 0fb7bba07b
commit 76aa419320
289 changed files with 28367 additions and 824 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docs/deployment/MULTI_CHAIN_DEPLOYMENT_GUIDE.md
View File

@@ -197,17 +197,17 @@ chainRegistry.registerEVMChain(
---
### **Hyperledger Firefly**
### **Hyperledger FireFly**
**Status**: ✅ Adapter + Service Client Created
**Infrastructure**: ✅ VMIDs 6202, 6203 deployed
**Infrastructure**: `6200` is the only validated FireFly runtime, `6201` is retired / standby, and `6202` / `6203` are not deployed in the current cluster.
**Deployment Steps**:
1. Initialize Firefly on VMID 6202:
1. Initialize FireFly only after confirming `6200` is healthy and intentionally in scope:
```bash
ssh root@192.168.11.175
ssh root@192.168.11.35
ff init alltra-bridge --multiparty
```
@@ -237,21 +237,26 @@ namespaces:
- erc20_erc721
```
For current runtime truth, prefer [docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md](../../../docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md).
---
## 🔧 **Hyperledger Integration**
### **Cacti (VMID 5201)**
### **Cacti (VMIDs 5200 / 5201 / 5202)**
**Status**: ⚠️ Needs Adapter
**Infrastructure**: `5200` is the primary Cacti / Besu connector node. `5201` and `5202` are the live Alltra/HYBX public Cacti surfaces and each also exposes a local Hyperledger Cacti API on `:4000`.
**Deployment Steps**:
1. Install Cacti API server on VMID 5201
2. Configure Besu connector plugin
3. Configure Fabric connector plugin (if needed)
4. Deploy CactiAdapter contract
5. Create Cacti client service
1. Maintain the core connector deployment on VMID `5200`.
2. Keep VMIDs `5201` and `5202` healthy for the public Alltra/HYBX Cacti surfaces and local `:4000` APIs.
3. Configure the Besu connector plugin.
4. Configure the Fabric connector plugin if needed.
5. Deploy the `CactiAdapter` contract.
6. Create the Cacti client service.
**Cacti Configuration**:
```json