- 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
1.5 KiB
1.5 KiB
DBIS Data API — implementation notes
OpenAPI contract: openapi.yaml.
Lineage
| Value | Meaning |
|---|---|
on_chain |
Derived from Chain 138 indexer, RPC, or token-aggregation inputs |
policy |
Published by policy officers; not implied as ledger truth |
modelled |
Simulation or internal model |
Suggested PostgreSQL / Timescale layout
Relational (PostgreSQL)
api_clients— id, name, key_hash, rate_limit_tier, created_atdatasets— id, slug, title, description, lineage_defaultdataset_versions— dataset_id, version, published_at, document_url
Hypertables (TimescaleDB)
metric_gru_supply— time TIMESTAMPTZ, value NUMERIC, metadata JSONBmetric_settlement_volume— time, window, chain_id, value, tx_countmetric_reserve_snapshot— time, asset, amount, source
Ingest jobs read from existing token-aggregation and explorer-compatible sources; separate ETL for policy-published series.
Frontend (DBIS portal)
Set NEXT_PUBLIC_DATA_API_BASE in the Gov Web Portals DBIS app (see DBIS/.env.example) so the homepage and /dashboard monetary panels call this API. When the service is down, the UI shows placeholders and an “unreachable” status.
Deployment path
- Provision CT/VM or service user on LAN.
- NPMplus proxy host
data.d-bis.org→ upstream. - Enable API keys (optional) for high-volume consumers; public tier remains read-only GET.
- Add host to E2E_ENDPOINTS_LIST.md when live.