# Repositories and Pull Requests — Chain 138 (Forms Submitted, Awaiting Feedback) **Last Updated:** 2026-02-28 **Purpose:** Single reference for all repositories you can add, connect, or submit PRs to for Chain 138 support — including wallets, explorers, on-ramps/off-ramps. **Forms have been submitted where applicable; we are awaiting feedback.** Use this doc to open or connect PRs when partners respond or when you are ready to contribute. --- ## Status: Forms submitted, awaiting feedback | Integration | Form / submission | Status | |-------------|-------------------|--------| | **Ledger Live** | [Tally form](https://tally.so/r/mORpv8) — submitted 2026-02-13 | Awaiting Ledger response; do not start code without signed agreement | | **Trust Wallet** | PR to wallet-core (materials ready) | Can open PR anytime; [ADD_CHAIN138_TO_TRUST_WALLET](../04-configuration/ADD_CHAIN138_TO_TRUST_WALLET.md) | | **Consensys / MetaMask** | Outreach (contact form, business@consensys.io) | Awaiting response; no public “add chain” PR repo for Swaps/Bridge | | **CoinGecko / CMC** | Submission via platform forms (chain/token listing) | Manual submit when ready; [CMC_COINGECKO_SUBMISSION_RUNBOOK](../04-configuration/coingecko/CMC_COINGECKO_SUBMISSION_RUNBOOK.md) | --- ## 1. Ledger (form submitted — await response) **Form:** https://tally.so/r/mORpv8 (submitted 2026-02-13) **Repositories (for after Ledger confirms):** | Repo | Purpose | PR / connect | |------|--------|--------------| | **LedgerHQ/ledger-live** | Ledger Live desktop/mobile; chain list, RPC, explorer | Add Chain 138 entry per their contribution guide after agreement | | **LedgerHQ/app-ethereum** | Device app (chain IDs, signing) | Add chain 138 to `network.c` / chain list if they request | | **LedgerHQ/wallet-api** | Wallet API (Ethereum family, chainId) | Extend for chainId 138 when Ledger specifies | | **bis-innovations/LedgerLive** | Your public repo for Ledger team review | Push Chain 138 materials (cryptoassets, config, patches); share with Ledger when they ask for code | **Docs:** [ADD_CHAIN138_TO_LEDGER_LIVE.md](../04-configuration/ADD_CHAIN138_TO_LEDGER_LIVE.md), [LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE.md](../11-references/LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE.md) **Do not** open PRs to LedgerHQ repos until Ledger has accepted the request and signed agreement. --- ## 2. Trust Wallet (PR when ready) **Repository:** https://github.com/trustwallet/wallet-core | Action | Details | |--------|---------| | **Add chain** | Add Chain 138 to `registry.json` (or current registry path); use `id`, `chainId`, `explorer`, `info.rpc` etc. | | **Codegen** | `./tools/new-evmchain dfiometa` (use registry id; requires Rust) | | **Tests** | Extend derivation tests for Chain 138 | | **PR** | Open PR with registry change + generated files + test updates | **Sample PRs:** [wallet-core #2307](https://github.com/trustwallet/wallet-core/pull/2307), [wallet-core #2157](https://github.com/trustwallet/wallet-core/pull/2157) **Optional — token/chain logos:** https://github.com/trustwallet/assets — submit via [assets.trustwallet.com](https://assets.trustwallet.com) for Chain 138 native tokens. **PR-ready file:** [docs/04-configuration/pr-ready/trust-wallet-registry-chain138.json](../04-configuration/pr-ready/trust-wallet-registry-chain138.json) — add to registry in wallet-core. See [pr-ready/README.md](../04-configuration/pr-ready/README.md). **Doc:** [ADD_CHAIN138_TO_TRUST_WALLET.md](../04-configuration/ADD_CHAIN138_TO_TRUST_WALLET.md) --- ## 3. Chainlist / Ethereum Lists (chain metadata) **Repository:** https://github.com/ethereum-lists/chains **PR-ready file:** [docs/04-configuration/pr-ready/eip155-138.json](../04-configuration/pr-ready/eip155-138.json) — copy to `_data/chains/eip155-138.json` in your fork. See [pr-ready/README.md](../04-configuration/pr-ready/README.md). Chain 138 may already be listed (see chainlist.org/chain/138). If you need to add or update: | Action | Details | |--------|--------| | **Add/update chain** | Add or edit `_data/chains/eip155-138.json` with name, chainId, rpc, explorers, nativeCurrency, etc. | | **PR** | Fork ethereum-lists/chains, add/update file, open PR; follow their CONTRIBUTING.md | **Local spec:** `pr-workspace/chains/_data/chains/eip155-138.json` in this repo (use as source for PR content). --- ## 4. Consensys / MetaMask (outreach — no public “add chain” PR) **Contact:** https://consensys.io/contact/ , business@consensys.io; MetaMask: https://support.metamask.io , https://developers.metamask.io **Repositories (reference only; Swaps/Bridge/on-ramp are Consensys-controlled):** | Repo | Purpose | |------|--------| | **MetaMask Snaps** | Your Snap can already support Chain 138; no PR to “add chain” to native Swaps/Bridge | | **Consensys** | Native Swaps, Bridge, Buy/Sell for Chain 138 require partnership/outreach; no public PR repo for “add network” to those products | **Outreach package:** [metamask-integration/docs/CONSENSYS_OUTREACH_PACKAGE.md](../../metamask-integration/docs/CONSENSYS_OUTREACH_PACKAGE.md) — use for email/contact form. Await response before expecting technical PR steps. --- ## 5. Price Feed — MetaMask and All Wallets **Master doc:** [PRICE_FEED_CHAIN138_METAMASK_AND_WALLETS.md](../04-configuration/PRICE_FEED_CHAIN138_METAMASK_AND_WALLETS.md) — single reference for adding Chain 138 USD prices to MetaMask and wallets. --- ## 6. CoinGecko / CoinMarketCap (submission, not PR) **Submission (not GitHub PR):** | Platform | URL / process | |----------|----------------| | **CoinGecko** | https://www.coingecko.com/en/coins/new — chain and token listing request | | **CoinMarketCap** | Use CMC listing/submission process (DEX or token form) | **Runbook:** [CMC_COINGECKO_SUBMISSION_RUNBOOK.md](../04-configuration/coingecko/CMC_COINGECKO_SUBMISSION_RUNBOOK.md) — export from report API (`/api/v1/report/coingecko`, `/api/v1/report/cmc`), then submit via platform forms. Chains 138 and 651940 may need to be supported by the platform first. --- ## 7. On-ramps and off-ramps (connect / add network) Most on-ramp/off-ramp providers do not accept public PRs to “add a chain”; they use partner/API or internal chain lists. Use this list to **request** or **connect** Chain 138. | Provider | How to add / connect Chain 138 | Repo / link (if any) | |----------|--------------------------------|----------------------| | **MoonPay** | Partner/API; request network support | https://www.moonpay.com/contact — no public chain-list PR repo | | **Ramp Network** | Partner integration; request network | https://ramp.network/ — developer/partner contact | | **Transak** | Partner; add network via dashboard or partner API | https://transak.com/ — partner/listing request | | **Onramper** | API; check if they support custom RPC/chainId | https://onramper.com/ | | **Banxa** | Partner integration | https://banxa.com/ | | **Coinbase Pay / Onramp** | Partner; add supported networks via Coinbase | https://docs.cdp.coinbase.com/ | | **MetaMask Buy (Consensys)** | Covered by Consensys outreach above | Same as §4 | **Current path (no native 138):** Users buy on a supported chain (e.g. mainnet) via ramp → then bridge to Chain 138. Off-ramp: bridge 138→mainnet → sell on mainnet. See [MAINNET_LIQUIDITY_AND_RAMPS_PRIORITY.md](MAINNET_LIQUIDITY_AND_RAMPS_PRIORITY.md), [MAINNET_RAMP_USER_FLOWS.md](../04-configuration/MAINNET_RAMP_USER_FLOWS.md). **Ramp API in repo:** `metamask-integration/src/ramps/` — `POST /ramps/on-ramp/session`, `POST /ramps/off-ramp/session`; set API keys (MOONPAY_API_KEY, RAMP_NETWORK_API_KEY, etc.) in .env. --- ## 8. Summary — what you can do now | Item | Action | |------|--------| | **Ledger** | Wait for response; then use LedgerHQ repos + bis-innovations/LedgerLive as instructed | | **Trust Wallet** | Open PR to [trustwallet/wallet-core](https://github.com/trustwallet/wallet-core) with registry + codegen + tests | | **Chainlist** | If 138 missing or outdated, open PR to [ethereum-lists/chains](https://github.com/ethereum-lists/chains) with `eip155-138.json` | | **Consensys** | Use [CONSENSYS_OUTREACH_PACKAGE](../../metamask-integration/docs/CONSENSYS_OUTREACH_PACKAGE.md); await response | | **Price Feed (MetaMask/wallets)** | See [PRICE_FEED_CHAIN138_METAMASK_AND_WALLETS.md](../04-configuration/PRICE_FEED_CHAIN138_METAMASK_AND_WALLETS.md); CoinGecko, CMC, Consensys | | **CoinGecko/CMC** | Export from report API; submit via platform forms per runbook | | **On-ramps/off-ramps** | Contact each provider (MoonPay, Ramp, Transak, etc.) to request Chain 138; no public PR repos | --- ## See also - [ADD_CHAIN138_TO_LEDGER_LIVE.md](../04-configuration/ADD_CHAIN138_TO_LEDGER_LIVE.md) - [ADD_CHAIN138_TO_TRUST_WALLET.md](../04-configuration/ADD_CHAIN138_TO_TRUST_WALLET.md) - [WHATS_LEFT_OPERATOR_AND_EXTERNAL.md](WHATS_LEFT_OPERATOR_AND_EXTERNAL.md) - [MAINNET_LIQUIDITY_AND_RAMPS_PRIORITY.md](MAINNET_LIQUIDITY_AND_RAMPS_PRIORITY.md)