Files
proxmox/docs/11-references/CHAIN138_TOKEN_ADDRESSES.md
defiQUG bea1903ac9
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Sync all local changes: docs, config, scripts, submodule refs, verification evidence
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-21 15:46:06 -08:00

4.3 KiB

Token Contract Addresses - ChainID 138

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation


Network: ChainID 138 (SMOM-DBIS-138)
RPC Endpoint (admin/deployment): Set RPC_URL_138 (e.g. http://192.168.11.211:8545 or https://rpc-core.d-bis.org)
Explorer: https://explorer.d-bis.org
Last Updated: 2025-12-24


📋 ERC20 Token Contracts

Standard Tokens

Token Symbol Address Decimals Status Notes
Wrapped Ether WETH 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 18 Pre-deployed Pre-deployed in Genesis
Wrapped Ether v10 WETH10 0xf4BB2e28688e89fCcE3c0580D37d36A7672E8A9f 18 Pre-deployed Pre-deployed in Genesis
Chainlink Token LINK 0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03 18 Deployed Used for CCIP fees

Compliant Stablecoins

Token Symbol Address Decimals Status Notes
Tether USD (Compliant) cUSDT 0x93E66202A11B1772E55407B32B44e5Cd8eda7f22 6 Deployed Compliant USDT token
USD Coin (Compliant) cUSDC 0xf22258f57794CC8E06237084b353Ab30fFfa640b 6 Deployed Compliant USDC token

🔗 Token Registry

The tokens can be tracked through the TokenRegistry contract:

Contract Address Purpose
TokenRegistry 0x91Efe92229dbf7C5B38D422621300956B55870Fa Centralized registry for all tokens on ChainID 138

📊 Summary

Total Token Contracts: 5

  1. WETH - 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
  2. WETH10 - 0xf4BB2e28688e89fCcE3c0580D37d36A7672E8A9f
  3. LINK - 0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03
  4. CompliantUSDT (cUSDT) - 0x93E66202A11B1772E55407B32B44e5Cd8eda7f22
  5. CompliantUSDC (cUSDC) - 0xf22258f57794CC8E06237084b353Ab30fFfa640b

🌉 Cross-chain (Chain 138 → Ethereum Mainnet)

Not all Chain 138 tokens have a Mainnet bridged/wrapped address. The relay bridge on Mainnet is WETH9-only.

Token Relay-supported (138→Mainnet) Mainnet address (if any)
WETH9 Yes 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 (same)
LINK No (bridge WETH9-only) Canonical: 0x514910771AF9Ca656af840dff83E8264EcF986CA
WETH10, cUSDT, cUSDC, Tether_Chain138 No No Mainnet wrapped contract in current design

Source of truth: TOKEN_MAPPING_AND_MAINNET_ADDRESSES.md and config/token-mapping.json. Use these for token lists and UIs so integrators do not assume a Mainnet address exists for unsupported tokens.


📝 Notes

  1. WETH9 and WETH10 were pre-deployed in the genesis block
  2. LINK token is used for CCIP (Cross-Chain Interoperability Protocol) fees
  3. Compliant stablecoins (cUSDT, cUSDC) include regulatory compliance features
  4. All addresses are checksummed and verified on-chain
  5. Token list maintained at: token-lists/lists/dbis-138.tokenlist.json

🔍 Verification

To verify a token contract on-chain:

# Check contract code
cast code <TOKEN_ADDRESS> --rpc-url $RPC_URL_138

# Check token details (name, symbol, decimals)
cast call <TOKEN_ADDRESS> "name()" --rpc-url $RPC_URL_138
cast call <TOKEN_ADDRESS> "symbol()" --rpc-url $RPC_URL_138
cast call <TOKEN_ADDRESS> "decimals()" --rpc-url $RPC_URL_138

Token alignment

Source File
Token list token-lists/lists/dbis-138.tokenlist.json
Canonical smom-dbis-138/services/token-aggregation/src/config/canonical-tokens.ts (FALLBACK_ADDRESSES)
Allowlist dbis_core/src/core/defi/tezos-usdtz/allowlist.config.ts (ALLOWED_CHAIN138_TOKENS)

References: