Add Chain 138 / DeFi Oracle Meta Mainnet support to DODO Widget and SDK config

[defiQUG]

Request

Please add Chain 138 / DeFi Oracle Meta Mainnet as a supported network in the DODO Widget / SDK chain configuration and related docs.

This is an upstream DODOEX integration request so DODO's own UI, widget, SDK/API config, and documentation can recognize Chain 138. A separate DefiLlama adapter PR is already open for TVL indexing: DefiLlama/DefiLlama-Adapters#19198

Chain metadata

• Network name: DeFi Oracle Meta Mainnet
• Common name: Chain 138
• Chain ID: 138
• Hex chain ID: 0x8a
• Native currency: ETH, 18 decimals
• Explorer: https://explorer.d-bis.org
• Secondary Blockscout explorer: https://blockscout.defi-oracle.io
• Public RPCs:
  • https://rpc-http-pub.d-bis.org
  • https://rpc.d-bis.org
  • https://rpc2.d-bis.org
  • https://rpc.defi-oracle.io

Relevant DODO / PMM deployment info

• DefiLlama chain slug being used: dfio_meta_main
• DODO/PMM DVM factory submitted for DefiLlama tracking:
  • 0xc93870594C7f83A0aE076c2e30b494Efc526b68E
• DefiLlama adapter start block:
  • 3510162
• Current Chain 138 indexed liquidity visible through DBIS reports:
  • 20,209,573.45973584 USD
• Indexed pools:
  • 7
• Positive indexed pools:
  • 2
• GRU V2 PMM registry rows:
  • 32
• GRU V2 route-visible pools:
  • 32

Initial token metadata

USDT:

{
  "chainId": 138,
  "address": "0x93e66202a11b1772e55407b32b44e5cd8eda7f22",
  "symbol": "USDT",
  "decimals": 6,
  "coingeckoId": "tether"
}

USDC:

{
  "chainId": 138,
  "address": "0xf22258f57794cc8e06237084b353ab30fffa640b",
  "symbol": "USDC",
  "decimals": 6,
  "coingeckoId": "usd-coin"
}

Suggested code surfaces in this repo

From the current DODOEX/widgets layout, Chain 138 likely needs entries or maintainers' confirmation in:

• packages/dodoex-api/src/chainConfig/chain.ts
• packages/dodoex-api/src/chainConfig/platform.ts
• packages/dodoex-api/src/chainConfig/basicToken.ts
• packages/dodoex-api/src/chainConfig/contractConfig.ts
• Widget docs / supported-chain docs

contractConfig.ts requires DODO-specific helper/proxy addresses such as MULTI_CALL, DODO_APPROVE, ERC20_HELPER, ROUTE_V2_DATA_FETCH, route helpers, and proxy contracts. If DODO Labs needs DBIS to deploy or provide any missing helper contracts for Chain 138, please specify the required contract set and expected versions.

Live verification endpoints

Core explorer / network metadata:

• Explorer UI: https://explorer.d-bis.org/
• Liquidity UI: https://explorer.d-bis.org/liquidity
• Pool UI: https://explorer.d-bis.org/pools
• Stats API: https://explorer.d-bis.org/api/v2/stats
• Network metadata: https://explorer.d-bis.org/api/config/networks
• Token list config: https://explorer.d-bis.org/api/config/token-list

Tracker/report APIs:

• External indexer readiness: https://explorer.d-bis.org/api/v1/report/external-indexer-readiness?chainId=138
• Unified liquidity report: https://explorer.d-bis.org/api/v1/report/all?chainId=138
• CoinGecko format: https://explorer.d-bis.org/api/v1/report/coingecko?chainId=138
• CoinMarketCap format: https://explorer.d-bis.org/api/v1/report/cmc?chainId=138
• Token list format: https://explorer.d-bis.org/api/v1/report/token-list?chainId=138
• GRU V2 PMM pool registry: https://explorer.d-bis.org/api/v1/report/gru-v2-pmm-pools?chainId=138
• Adoption/listing readiness: https://explorer.d-bis.org/api/v1/report/adoption-readiness

Route / liquidity infrastructure:

• Route matrix: https://blockscout.defi-oracle.io/token-aggregation/api/v1/routes/matrix?includeNonLive=true
• Provider capabilities: https://blockscout.defi-oracle.io/token-aggregation/api/v2/providers/capabilities?chainId=138
• Bridge status: https://explorer.d-bis.org/explorer-api/v1/track1/bridge/status
• Example mission-control token pools endpoint: https://explorer.d-bis.org/explorer-api/v1/mission-control/liquidity/token/0x004b63A7B5b0E06f6bB6adb4a5F9f590BF3182D1/pools

Current readiness JSON summary

GET https://explorer.d-bis.org/api/v1/report/external-indexer-readiness?chainId=138 currently reports:

{
  "tokenCount": 31,
  "indexedPoolCount": 7,
  "positiveIndexedPoolCount": 2,
  "tokenPoolRows": 78,
  "positiveTokenPoolRows": 60,
  "totalLiquidityUsd": 20209573.45973584,
  "gruV2PoolCount": 32,
  "gruV2RoutingEnabledPoolCount": 32
}

Requested outcome

Please confirm whether DODO Labs is willing to recognize Chain 138 in the DODO Widget / SDK / docs, and what additional DODO-side contract deployments, indexing requirements, or allowlist changes are required for official support.

[defiQUG]

Add chainId 138 to @dodoex/widgets (update)

Network: DeFi Oracle Meta Mainnet (chainId 138, DefiLlama dfio_meta_main)

Please enable @dodoex/widgets / SwapWidget for chain 138 once backend routing is live.

On-chain (deployed 2026-05-19)

Contract	Address
DVMFactory	0xc93870594C7f83A0aE076c2e30b494Efc526b68E
DODOApprove	0xEA5Be91d0A1EdA6a2efc80f7211c30584508D56D
DODOV2Proxy02	0xEF6E6F41A522896a9EE1C580C87C05E409193F8d
WETH	0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2

Blockers (DODO backend)

1. Merge contract-request#30 + npm publish @dodoex/dodo-contract-request
2. Enable api.dodoex.io/route-service for chainId=138
3. Add chain 138 to tokenlist API (config-center/user/tokenlist/v2)

Explorer

https://explorer.d-bis.org

Note: DBIS PMM integration 0x86ADA6Ef… is a project wrapper — widgets should use native DODO proxies above.