Add DBIS RTGS and Hyperledger integration TODOs
All checks were successful
Deploy to Phoenix / deploy (push) Successful in 7s

This commit is contained in:
defiQUG
2026-03-28 23:33:25 -07:00
parent d6aebf3c43
commit fba855ec9e
2 changed files with 147 additions and 1 deletions

View File

@@ -175,7 +175,146 @@
---
## 12. Maintenance (135139)
## 12. DBIS RTGS / HYBX / Hyperledger E2E stack
**Purpose:** Track everything required for a true end-to-end RTGS stack across DBIS Chain 138, HYBX sidecars, OMNL / Fineract, and the external banking / interoperability integrations we currently have access to.
### 12.1 Participant / treasury / GL model
- [ ] Finalize participant model for RTGS and settlement:
- central bank / RTGS operator
- HYBX participant
- Bank Kanaya and other offices / institutions
- [ ] Finalize treasury account model:
- settlement
- reserve
- nostro
- vostro
- liquidity / prefunding accounts
- [ ] Finalize GL mappings and JE flows for RTGS settlement in OMNL / Fineract.
- [ ] Freeze the canonical ID resolution flow using:
- `scripts/omnl/resolve_ids.sh`
- `scripts/omnl/omnl-office-create-*.sh`
- `scripts/omnl/omnl-pvp-post-clearing-bank-kanaya.sh`
### 12.2 Mifos / Fineract / OMNL banking rail
- [ ] Confirm production-grade Mifos/Fineract tenancy, credentials, API reachability, and operator runbook completeness for the current OMNL environment.
- [ ] Complete the full operator rail using:
- `scripts/omnl/omnl-operator-rail.sh`
- `scripts/omnl/omnl-reconciliation-office20.sh`
- `scripts/omnl/omnl-audit-packet-office20.sh`
- [ ] Complete the Indonesia / HYBX evidence path:
- `scripts/omnl/build-transaction-package-zip.sh`
- `scripts/omnl/verify-transaction-package-commitment.py`
- `scripts/omnl/check-transaction-package-4995-readiness.sh --strict`
- [ ] Freeze the source-of-truth API contract from `docs/11-references/API_DOCUMENTATION.md` and the OMNL OpenAPI snapshot.
### 12.3 Mojaloop integration
- [ ] Identify the exact Mojaloop deployment / switch endpoints currently available to HYBX.
- [ ] Document the live Mojaloop API contract and auth model:
- quote
- transfer
- callback / status
- settlement window / liquidity behavior
- [ ] Define the canonical mapping between Mojaloop events and:
- Fineract postings
- sidecar events
- on-chain settlement events
- [ ] Add a repo-backed Mojaloop integration runbook once endpoint details are confirmed.
### 12.4 HYBX sidecar integration
- [ ] Audit and document the currently accessible HYBX sidecars:
- `mifos-fineract-sidecar`
- `mt103-hardcopy-sidecar`
- `off-ledger-2-on-ledger-sidecar`
- `securitization-engine-sidecar`
- `card-networks-sidecar`
- `server-funds-sidecar`
- `securities-sidecar` (if in scope)
- `flash-loan-xau-sidecar` (if in scope)
- [ ] Define system boundaries and ownership for each sidecar:
- system-of-record
- message ingress / egress
- retry semantics
- auth and credential handling
- [ ] Create a canonical end-to-end sidecar matrix linked from the RTGS runbook.
### 12.5 Chain 138 settlement rail
- [ ] Freeze the canonical on-chain settlement path for RTGS:
- DBIS / compliant settlement tokens
- MerchantSettlementRegistry
- WithdrawalEscrow
- reserve / oracle dependencies where applicable
- [ ] Define the exact mapping from off-ledger settlement events to on-chain settlement confirmations.
- [ ] Decide when `alltra-lifi-settlement` is in the critical RTGS path versus optional cross-chain / liquidity extension.
- [ ] Produce a repo-backed RTGS settlement sequence diagram spanning Fineract ↔ sidecars ↔ Chain 138.
### 12.6 Workflow and orchestration
- [ ] Keep FireFly `6200` as the active primary workflow layer and preserve its config/image path.
- [ ] Decide whether to rebuild `6201` as a real secondary FireFly node for HA or leave it permanently retired.
- [ ] Define the event catalog and correlation model across:
- Fineract
- Mojaloop
- HYBX sidecars
- FireFly
- Chain 138
- regulatory package generation
- [ ] Add compensating-action / retry design for cross-system failures.
### 12.7 Additional Hyperledger layers needed
- [ ] Decide whether **Hyperledger Aries** is required as an actual deployed identity / agent layer for DBIS RTGS.
- [ ] If Aries is in scope, define:
- agent placement
- wallet / DID model
- protocol flows
- relationship to Indy and credential verification
- [ ] Decide whether **Hyperledger AnonCreds** is required as part of the verifiable credential stack.
- [ ] If AnonCreds is in scope, define the issuer / holder / verifier model and where credential registries live.
- [ ] Decide whether **Hyperledger Ursa** is required as an explicit cryptographic dependency versus an indirect library/runtime concern.
- [ ] If Ursa is in scope, document where it is used in the identity / VC pipeline and what operational control it requires.
- [ ] Decide whether **Hyperledger Cacti** is actually needed in the RTGS interoperability path or remains optional / future-state.
- [ ] Keep **Hyperledger Caliper** in the program for RTGS performance validation and benchmark the final path when the stack is complete.
### 12.8 Fabric / Indy runtime decision
- [ ] If Fabric is required for the RTGS target architecture, deploy real workloads onto `6000-6002` and validate peer / orderer health.
- [ ] If Fabric is not required now, keep `6000-6002` classified as reserved placeholders and remove them from any “active stack” claims.
- [ ] If Indy is required for the RTGS target architecture, deploy real workloads onto `6400-6402` and validate validator / listener health.
- [ ] If Indy is not required now, keep `6400-6402` classified as reserved placeholders and remove them from any “active stack” claims.
### 12.9 Regulatory / audit / ISO package
- [ ] Finalize the institutional attestation and evidentiary package path for HYBX submissions.
- [ ] Finalize ISO 20022 vault manifest generation and hash anchoring policy.
- [ ] Finalize AML / sanctions / legal-finality memo workflow for production submissions.
- [ ] Ensure the RTGS path has a reproducible audit packet per settlement batch.
### 12.10 Production gate
- [ ] Create a dedicated RTGS E2E requirements matrix covering:
- component
- current status
- repo / API source
- blocker
- owner
- production gate criteria
- [ ] Add a single “full RTGS E2E” production gate that only turns green when:
- Fineract / OMNL is complete
- HYBX sidecars are integrated
- Mojaloop integration is real and validated
- Chain 138 settlement path is validated
- required Hyperledger identity/workflow layers are deployed
- regulatory package generation passes
---
## 13. Maintenance (135139)
- [x] **Runbook and script:** [OPERATIONAL_RUNBOOKS.md](../03-deployment/OPERATIONAL_RUNBOOKS.md) § Maintenance; `scripts/maintenance/daily-weekly-checks.sh [daily|weekly|all]` for 135137. Schedule via cron (e.g. daily 08:00).
- [x] **Script tested:** daily-weekly-checks.sh daily (explorer SKIP off-LAN, RPC OK).

View File

@@ -5,6 +5,13 @@
## Repository-wide TODO
- **[00-meta/TODO_TASK_LIST_MASTER.md](00-meta/TODO_TASK_LIST_MASTER.md)** — Consolidated fixes, enhancements, gas steps, known issues, and recommendations for the Proxmox/Chain138 deployment and related repos.
- Includes the DBIS RTGS / HYBX / Hyperledger E2E stack tasks:
- Mifos / Fineract / OMNL
- Mojaloop integration
- HYBX sidecars
- Chain 138 settlement rail
- FireFly / Fabric / Indy runtime decisions
- additional Hyperledger layers such as Aries, AnonCreds, Ursa, Cacti, and Caliper
## Subproject TODOs