Files
explorer-monorepo/docs/METAMASK_AND_PROVIDER_INTEGRATION.md
defiQUG bdae5a9f6e feat: explorer API, wallet, CCIP scripts, and config refresh
- Backend REST/gateway/track routes, analytics, Blockscout proxy paths.
- Frontend wallet and liquidity surfaces; MetaMask token list alignment.
- Deployment docs, verification scripts, address inventory updates.

Check: go build ./... under backend/ (pass).
Made-with: Cursor
2026-04-07 23:22:12 -07:00

4.1 KiB

MetaMask and Dual-Chain Provider Integration

The explorer (SolaceScanScout) provides add-to-MetaMask and token list discovery for Chain 138 (DeFi Oracle Meta Mainnet), Ethereum Mainnet, and ALL Mainnet (651940).

Explorer as discovery source

  • Add to MetaMask: Use the Wallet page to add Chain 138, Ethereum Mainnet, or ALL Mainnet to your wallet via wallet_addEthereumChain.
  • Token list URL: The explorer API serves the dual-chain token list at:
    • Path: /api/config/token-list
    • Full URL: {EXPLORER_API_BASE}/api/config/token-list (e.g. https://explorer.d-bis.org/api/config/token-list if the API is on the same origin). Add this URL in MetaMask Settings → Token lists so tokens for Chain 138 and Mainnet appear automatically. As of April 3, 2026, the public explorer token list exposes 190 entries, including the full Mainnet cW* suite.
  • Networks config: /api/config/networks returns the same chain params (Chain 138 + Ethereum Mainnet) in JSON for programmatic use.
  • GRU v2 public rollout status: the explorer also publishes static status surfaces at /config/GRU_V2_PUBLIC_DEPLOYMENT_STATUS.json and /config/GRU_V2_DEPLOYMENT_QUEUE.json. Together they summarize the public EVM cW* mesh, Wave 1 transport posture, the current public-protocol truth for Uniswap v3, Balancer, Curve 3, DODO PMM, and 1inch, and the remaining operator queue by asset/chain/protocol.

Provider and feature parity

Discovery without CMC/CoinGecko

Discovery is via token list (hosted at the explorer token list URL above), liquidity pools (token-aggregation service), and pricing APIs (token-aggregation REST API and on-chain oracles). See the feature parity doc for details.

Token-aggregation REST API: For tokens, pools, prices, volume, and OHLCV (Chain 138 and ALL Mainnet), see smom-dbis-138/services/token-aggregation/docs/REST_API_REFERENCE.md.

Optional next steps

Live explorer (https://explorer.d-bis.org)

For backend deployment and integration tests, see EXPLORER_D_BIS_ORG_INTEGRATION.md. For token-list publishing, use explorer-monorepo/scripts/deploy-explorer-config-to-vmid5000.sh; it now falls back through the Proxmox host automatically when local pct is not installed.