Files

defiQUG 7ac74f432b chore: sync docs, config schemas, scripts, and meta task alignment

- Institutional / JVMTM / reserve-provenance / GRU transport + standards JSON
- Validation and verify scripts (Blockscout labels, x402, GRU preflight, P1 local path)
- Wormhole wiring in AGENTS, MCP_SETUP, MASTER_INDEX, 04-configuration README
- Meta docs, integration gaps, live verification log, architecture updates
- CI validate-config workflow updates

Operator/LAN items, submodule working trees, and public token-aggregation edge
routes remain follow-up (see TODOS_CONSOLIDATED P1).

Made-with: Cursor

2026-03-31 22:31:39 -07:00

.gitignore

chore: sync docs, config schemas, scripts, and meta task alignment

2026-03-31 22:31:39 -07:00

README.md

chore: sync docs, config schemas, scripts, and meta task alignment

2026-03-31 22:31:39 -07:00

README.md

Address registry drop-in (operator / CI)

Place non-example address-registry-entry JSON files here (one object per file, or one array in a single file). These files may contain LEI, IBAN, and live 0x addresses — treat as confidential; prefer .gitignore or a secrets store in production.

Sync labels to Blockscout

From repo root (plan only):

bash scripts/verify/sync-blockscout-address-labels-from-registry.sh --from-dir config/dbis-institutional/registry

Or a single JSON array file (see ../examples/address-registry-entries-batch.example.json):

bash scripts/verify/sync-blockscout-address-labels-from-registry.sh path/to/registry-array.json

Apply (LAN or VPN to explorer; set API key if required):

export BLOCKSCOUT_API_KEY=...   # if your Blockscout instance requires it
bash scripts/verify/sync-blockscout-address-labels-from-registry.sh --apply --from-dir config/dbis-institutional/registry

For the self-hosted Chain 138 explorer, prefer direct DB sync:

bash scripts/verify/sync-blockscout-address-labels-from-registry.sh --apply --mode=db --from-dir config/dbis-institutional/registry

That path writes Blockscout primary labels into public.address_names through the explorer CT (5000) because explorer.d-bis.org/api/v1/* is token-aggregation, not a native Blockscout label-write surface. Use HTTP mode only if you have separately enabled and confirmed a compatible label endpoint (default probe target: /api/v1/labels).

Token contract staging

This directory is also the right place for live token-contract label rows that should not be committed, for example:

staged cUSDT V2 / cUSDC V2 token contract labels on Chain 138
bridge-side cW* contracts before public cutover
temporary explorer labels used during GRU V1/V2 coexistence

Keep versioned token contracts clearly labeled in blockscout.label, for example Chain 138 cUSDT V2 (staged), so explorer operators can distinguish them from the active V1 liquidity contracts.