6c5fdcfd62
- Refresh pnpm-lock.yaml / workspace after prior merge - Add Chain 138 info hub SPA (info-defi-oracle-138) - Token list and validation script tweaks; path_b report; Hyperledger proxmox install notes - HYBX implementation roadmap and routing graph data model Note: transaction-composer is a nested git repo — convert to submodule before tracking. Made-with: Cursor
info.defi-oracle.io — Chain 138 public hub
Static SPA (Vite + React) for https://info.defi-oracle.io: compliant c* tokens, cW* registry (from cross-chain-pmm-lps/config/deployment-status.json), live pools and quotes from the token-aggregation API, CCIP routing tables, and wallet swapExactIn on DODOPMMIntegration.
Develop
cd /path/to/proxmox
pnpm install
pnpm --filter info-defi-oracle-138 dev
Environment (optional)
| Variable | Purpose |
|---|---|
VITE_TOKEN_AGGREGATION_API_BASE |
Token-aggregation origin (default https://dbis-api.d-bis.org). The client also tries the same host with /token-aggregation prefix and https://explorer.d-bis.org variants until one returns HTTP 200. |
VITE_RPC_URL_138 |
Chain 138 RPC for wallet / reads (default https://rpc.defi-oracle.io) |
Example:
export VITE_TOKEN_AGGREGATION_API_BASE=https://dbis-api.d-bis.org
export VITE_RPC_URL_138=https://rpc.defi-oracle.io
pnpm --filter info-defi-oracle-138 build
Build
pnpm --filter info-defi-oracle-138 build
Output: info-defi-oracle-138/dist/ — deploy as static files (any CDN, Nginx, object storage, or LXC).
Deploy info.defi-oracle.io
- DNS: Point
info.defi-oracle.io(A/AAAA or CNAME) to your edge (Cloudflare, NPMplus host, etc.). - TLS: Issue certificate for
info.defi-oracle.io(same pattern asrpc.defi-oracle.io). - NPMplus (or Nginx): Proxy host → upstream serving
dist/withtry_files $uri $uri/ /index.htmlfor SPA routes. - API: Ensure
VITE_TOKEN_AGGREGATION_API_BASEat build time points to a public token-aggregation URL that allows browser CORS (service already usescors()).
See also: docs/04-configuration/E2E_ENDPOINTS_LIST.md (dbis-api hosts), docs/04-configuration/ALL_VMIDS_ENDPOINTS.md (VMID targets).
Refreshing cW* addresses
cW* tables are bundled at build from cross-chain-pmm-lps/config/deployment-status.json. Rebuild and redeploy after registry changes.
Canonical on-chain addresses
Built-in constants follow docs/11-references/CONTRACT_ADDRESSES_REFERENCE.md (e.g. DODOPMMIntegration, cUSDT/cUSDC on 138).