- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains - Omit embedded publish git dirs and empty placeholders from index Made-with: Cursor
50 lines
2.9 KiB
Markdown
50 lines
2.9 KiB
Markdown
# PR-Ready Submissions — Chain 138
|
||
|
||
**Purpose:** Drop-in content to open pull requests or submit listings for Defi Oracle Meta Mainnet (Chain ID 138). Use when you are ready to submit; forms are already submitted where applicable (see [REPOSITORIES_AND_PRS_CHAIN138](../../00-meta/REPOSITORIES_AND_PRS_CHAIN138.md)).
|
||
|
||
---
|
||
|
||
## 1. Chainlist (ethereum-lists/chains)
|
||
|
||
**Repo:** https://github.com/ethereum-lists/chains
|
||
**Upstream status:** [ethereum-lists/chains#8124](https://github.com/ethereum-lists/chains/pull/8124) merged ([cb4c47b](https://github.com/ethereum-lists/chains/commit/cb4c47b0345fa8688dbc0133e0aa1cd3fb211a80)). This repo’s [eip155-138.json](./eip155-138.json) mirrors [upstream `master`](https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-138.json) for local PRs and reviews.
|
||
|
||
**File:** [eip155-138.json](./eip155-138.json) — **public** RPC endpoints only (Besu Core / JWT private RPC hostnames are not listed here).
|
||
|
||
**When proposing a change:**
|
||
1. Edit this file (and `pr-workspace/chains/_data/chains/eip155-138.json`) to match the intended upstream diff.
|
||
2. Fork https://github.com/ethereum-lists/chains, copy to `_data/chains/eip155-138.json`, run their checks / Prettier per [CONTRIBUTING.md](https://github.com/ethereum-lists/chains/blob/master/CONTRIBUTING.md).
|
||
3. In the PR description you can paste the “Chain 138 spec” from [ADD_CHAIN138_TO_TRUST_WALLET.md](../ADD_CHAIN138_TO_TRUST_WALLET.md#chain-138-spec-for-forms--pr-description).
|
||
|
||
**Live listing:** https://chainlist.org/chain/138
|
||
|
||
---
|
||
|
||
## 2. Trust Wallet (trustwallet/wallet-core)
|
||
|
||
**Repo:** https://github.com/trustwallet/wallet-core
|
||
**Action:** Add Chain 138 to the chain registry (e.g. `registry.json` or current path per their docs).
|
||
|
||
**File:** [trust-wallet-registry-chain138.json](./trust-wallet-registry-chain138.json)
|
||
|
||
**Steps:**
|
||
1. Clone trustwallet/wallet-core and follow [Trust – New EVM chain](https://developer.trustwallet.com/developer/wallet-core/newblockchain/newevmchain)
|
||
2. Add the JSON entry from `trust-wallet-registry-chain138.json` to the registry file (path may be `registry.json` or under `registry/`; check repo)
|
||
3. Run codegen: `./tools/new-evmchain dfiometa` (use registry **id**, not chainId 138; requires Rust/cargo)
|
||
4. Extend derivation tests if required
|
||
5. Build and test, then open PR with registry change + generated files
|
||
|
||
**Full guide:** [ADD_CHAIN138_TO_TRUST_WALLET.md](../ADD_CHAIN138_TO_TRUST_WALLET.md)
|
||
|
||
---
|
||
|
||
## 3. Ledger (after they respond)
|
||
|
||
When Ledger confirms the request, use [ADD_CHAIN138_TO_LEDGER_LIVE.md](../ADD_CHAIN138_TO_LEDGER_LIVE.md) and push materials to **bis-innovations/LedgerLive** for their review. No PR-ready file here; follow Ledger’s instructions.
|
||
|
||
---
|
||
|
||
## 4. CoinGecko / CMC
|
||
|
||
No GitHub PR. Use [CMC_COINGECKO_SUBMISSION_RUNBOOK.md](../coingecko/CMC_COINGECKO_SUBMISSION_RUNBOOK.md) and export from the report API, then submit via platform forms.
|