Add Chain 138 (Defi Oracle Meta Mainnet)#4738
Conversation
|
Cross-link: support question in #4744 (“do derivation addresses need exchanging?”) — answered there: no. Chain 138 uses standard EVM derivation ( Rebased onto current |
|
Assets PR opened for canonical Chain 138 tokens (16) + chain info: trustwallet/assets#36922 — pairs with this wallet-core change (dfiometa / coin_type 10000138). |
|
Merge request — assets PRs blocked on this Chain 138 assets submissions are waiting on wallet-core registration (
Branch is rebased on Kindly review and merge when ready. Thank you. |
c7a6d51 to
00249af
Compare
|
Refresh: rebased onto latest master (2026-06-10) — resolved TWCoinType / derivation test conflicts with SeiEVM + HyperEVM upstream additions. |
|
What is erc20 wallet I am added in this coin |
What changed
This PR adds basic Wallet Core support for
Defi Oracle Meta Mainnet(chainId 138,id: dfiometa) as an EVM-compatible chain.Included changes:
registry.jsonTWCoinTypeDefiOracleMetaMainnetTWCoinTypeconfiguration testChain details
Defi Oracle Meta Mainnet138dfiometaETHhttps://explorer.d-bis.orghttps://rpc-http-pub.d-bis.orgWhy
Chain 138 is an EVM-compatible network and should be handled as a standard Ethereum-family chain in Wallet Core so users can derive addresses and resolve chain metadata without manual workarounds.
Scope note
This PR is for chain support only.
It does not add ERC-20 asset metadata such as:
Those belong to separate token-asset / assets-app submission flows rather than the Wallet Core chain-registry change itself.
Validation
jq empty registry.jsoncd rust && cargo test -p tw_tests --test coin_address_derivation_testReferences