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

Align Chain 138 public RPC URLs for wallets and token-aggregation API.
Some checks failed
CI/CD Pipeline / Solidity Contracts (push) Failing after 1m45s
Details
CI/CD Pipeline / Security Scanning (push) Successful in 2m41s
Details
CI/CD Pipeline / Lint and Format (push) Failing after 52s
Details
CI/CD Pipeline / Terraform Validation (push) Failing after 30s
Details
CI/CD Pipeline / Kubernetes Validation (push) Successful in 28s
Details
HYBX OMNL TypeScript & anchor / token-aggregation build + reconcile artifact (push) Failing after 32s
Details
Validation / validate-genesis (push) Successful in 29s
Details
Validation / validate-terraform (push) Failing after 31s
Details
Validation / validate-kubernetes (push) Failing after 14s
Details
Validation / validate-smart-contracts (push) Failing after 12s
Details
Validation / validate-security (push) Failing after 1m28s
Details
Validation / validate-documentation (push) Failing after 20s
Details

Browse Source 
Use rpc.public-0138.defi-oracle.io as canonical MetaMask addEthereumChain RPC; expand tokenDetection tokenListUrls; update tests.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
defiQUG
2026-06-27 19:13:03 -07:00
parent 6cda9be1a0
commit 304b3b4377
22 changed files with 169 additions and 181 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
services/token-aggregation/docs/REST_API_REFERENCE.md
View File

@@ -42,7 +42,7 @@ Oracles (and config) per chain. Used by the Snap for USD price feeds (e.g. ETH/U
## Token list (report)
**GET /api/v1/report/token-list** returns a Uniswap-style token list with **logoURI** per token and a list-level **logoURI**. Each token has: `chainId`, `address`, `symbol`, `name`, `decimals`, `type`, `logoURI`. Chain 138 also exposes staged GRU x402 deployments such as `cUSDT_V2` and `cUSDC_V2` explicitly, with optional metadata fields like `familySymbol`, `deploymentVersion`, and `preferredForX402`. Use for MetaMask token list URL or Snap `get_token_list`. Optional query `?chainId=138` filters by chain. If **TOKEN_LIST_JSON_URL** is set (e.g. GitHub raw URL), the service fetches that JSON and returns it (with optional chainId filter); otherwise uses the built-in canonical token list.
**GET /api/v1/report/token-list** returns a Uniswap-style token list with **logoURI** per token and a list-level **logoURI**. Each token has: `chainId`, `address`, `symbol`, `name`, `decimals`, `type`, `logoURI`. Chain 138 also exposes staged GRU x402 deployments such as `cUSDT_V2` and `cUSDC_V2` explicitly, with optional metadata fields like `familySymbol`, `deploymentVersion`, and `preferredForX402`. Use for MetaMask token list URL or Snap `get_token_list`. Optional query `?chainId=138` filters by chain. The current hosted DBIS list is `https://tokens.d-bis.org/lists/dbis-138.tokenlist.json`; other chains use the built-in canonical token list.
**GET /api/v1/report/cw-registry** returns the public-chain `cW*` registry grouped by chain. When `DEPLOYMENT_STATUS_JSON_PATH` / `CW_REGISTRY_JSON_PATH` points to `cross-chain-pmm-lps/config/deployment-status.json`, the endpoint reads that file at request time so explorer surfaces do not need a rebuild after registry edits. If the file is unavailable, it falls back to the built-in canonical `cW*` subset.
@@ -276,4 +276,4 @@ This API is the primary source for **token discovery**, **liquidity pool discove
- Prices and volume
- OHLCV for charts
Combine with the **explorer-hosted token list** (`https://explorer.d-bis.org/api/config/token-list`) for MetaMask token list URL discovery. For dynamic Snap integration, use **GET /api/v1/networks** and **GET /api/v1/config** (see "Networks and config (Snap)" above); the Snap can return the token list URL as `{apiBaseUrl}/api/v1/report/token-list` for MetaMask Settings.
Combine with the **hosted DBIS token list** (`https://tokens.d-bis.org/lists/dbis-138.tokenlist.json`) for MetaMask token list URL discovery. For dynamic Snap integration, use **GET /api/v1/networks** and **GET /api/v1/config** (see "Networks and config (Snap)" above); the Snap can return the hosted token list URL directly for MetaMask Settings.