Wallet & MetaMask
Connect Chain 138 (DeFi Oracle Meta Mainnet) and Ethereum Mainnet to MetaMask and other Web3 wallets. Use the token list URL so tokens and oracles are discoverable.
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: add the token list URL below under Settings → Security & privacy → Token lists so tokens and icons load automatically when you are on this chain.
Optional MetaMask Snap that 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", use MetaMask Flask for development or apply for allowlisting. It adds in-wallet weekly reminders, Chain 138 transaction/signature hints, and the token list URL on the Snap home page. 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: using frontend fallback values
Chain 138 token entries: 0
Networks source: unknown
Token list source: unknown
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: using published explorer fallback
Capabilities source: unknown
HTTP methods: metadata unavailable
Missing wallet-facing methods: none listed
Trace methods: metadata unavailable
These tokens come from the explorer token list and use `wallet_watchAsset` so the wallet gets the same symbol, decimals, image, and optional token metadata that the explorer publishes.
Featured token metadata is not available right now.