Wallet Tools
Use the explorer-served network catalog, token list, and capability metadata to connect Chain 138 (DeFi Oracle Meta Mainnet) and Ethereum Mainnet to MetaMask and other Web3 wallets.
Connect a browser wallet to make this page useful beyond setup: copy your address, open your on-explorer address page, and continue into the access console with the same session.
Add to MetaMask
The wallet tools now read the same explorer-served network catalog and token list that MetaMask can consume. That keeps chain metadata, token metadata, and optional extensions aligned with the live explorer API instead of relying on stale frontend-only defaults. MetaMask does not run built-in token detection on custom networks such as Chain 138, so this page uses EIP-747 wallet_watchAsset prompts from the live MetaMask payload to add token metadata directly to the wallet.
This is not required for the production wallet flow above. The normal production path is to add Chain 138, then add tokens through EIP-747 wallet_watchAsset prompts. The optional Snap uses only open Snap permissions (minimal privileged APIs in the Snap itself). Stable MetaMask still only installs npm Snaps that appear on MetaMask's install allowlist; if install fails with "not on the allowlist", that is an external MetaMask review gate rather than an explorer/network failure. Use MetaMask Flask for development or apply for allowlisting before using this with Stable MetaMask. The package on npm is npm:chain138-open-snap— publish from the repo with scripts/deployment/publish-chain138-open-snap.sh after npm login.
Networks catalog: 13 chains
Chain 138 token entries: 18
EIP-747 watchAsset entries: 18
Networks source: explorer-api
Token list source: explorer-api
MetaMask payload source: unknown
Keywords: chain138, defi-oracle-meta, multichain, metamask, wallet
This capability matrix documents what public RPC methods wallets can rely on today, what tracing the explorer can use, and where MetaMask will still fall back because the public node does not expose every optional fee method.
RPC endpoint: https://rpc-http-pub.d-bis.org
Capabilities source: explorer-api
HTTP methods: web3_clientVersion, net_version, eth_chainId, eth_blockNumber, eth_syncing, eth_gasPrice, eth_maxPriorityFeePerGas, eth_feeHistory, eth_estimateGas, eth_getCode
Missing wallet-facing methods: none listed
Trace methods: trace_block, trace_replayBlockTransactions
MetaMask primarily relies on JSON-RPC correctness for balances, gas estimation, calls, and transaction submission.
Explorer-served network metadata and token list metadata complement wallet UX but do not replace RPC method support.
eth_feeHistory is available for wallet fee estimation.
eth_maxPriorityFeePerGas is exposed on the public RPC for wallet-grade fee suggestion compatibility.
Last modified: 2026-05-09T21:01:45.000Z
These tokens come from the explorer MetaMask payload and use wallet_watchAsset so the wallet gets the same symbol, decimals, image, and optional token metadata that the explorer publishes. MetaMask requires a user approval for each token, so the bulk actions below run as a guided sequence of wallet prompts.
This refreshes the Mainnet cWUSDC custom asset metadata with the DBIS-hosted image URL. MetaMask fiat price display still depends on MetaMask and upstream asset/price providers accepting the Mainnet listing.