d-bis/proxmox
4
0
Fork 0
Code Issues 2 Pull Requests 13 Actions Packages Projects Releases Wiki Activity
Files
7aa5162c5bbaba4168a215636ea7c59a00bd82c2
proxmox/docs/04-configuration/pr-ready
History
Devin AI 7aa5162c5b
Some checks failed
AI Code Review / claude-review (pull_request) Failing after 31s
Details
docs(chain-138): normalize chain name to DeFi Oracle Meta Mainnet across docs + pr-ready assets 
Per maintainer decision, the canonical chain-name spelling is `DeFi Oracle Meta Mainnet`
(capital F) — matching what the live SDK + token-aggregation service emit on
`https://explorer.d-bis.org/api/config/networks`. Docs + `pr-ready/` JSONs had drifted
to `Defi Oracle Meta Mainnet`; this PR realigns them.

Scope:
- `docs/04-configuration/pr-ready/*.json` (eip155-138 + trust-wallet registry + packaged copies + manifests)
- `docs/04-configuration/pr-ready/**/README.md`
- `docs/04-configuration/metamask/METAMASK_NETWORK_CONFIG.json`
- 10+ narrative docs under `docs/04-configuration/`, `docs/11-references/`, `docs/01-getting-started/`, `docs/00-meta/`, `docs/09-troubleshooting/`, `docs/archive/`
- `docs/04-configuration/coingecko/COINGECKO_SUBMISSION_{GUIDE,CUSDT,CUSDC}.md`, `COINGECKO_API_NO_PUSH_LIQUIDITY.md`
- `reports/DEFI_ORACLE_MAINNET_CONNECTION_GUIDE.md`
- `scripts/test-thirdweb-bridge-widget.js`

45 files; 92 lines changed. Submodules untouched.

Verification:
- `grep -rln 'Defi Oracle Meta Mainnet' docs/ reports/ scripts/` returns 0 hits post-change.
- JSON files pass `python3 -m json.tool` lint.
- Services (`smom-dbis-138/sdk`, `services/token-aggregation`) already use the capital-F form and are not touched.

Remaining drift (not in scope):
- PR #7's `COINGECKO_CHAIN138_SUBMISSION_ATTACHMENT.md` still uses `Defi`; will be fixed on that branch separately.
- User's local normalized versions of 5 CoinGecko docs are still pending attachment; companion PR will pick up this rename naturally since it's already applied on master.

No submodule pointers changed. No secrets touched.
2026-04-19 19:52:47 +00:00
..
chain138-asset-package
docs(chain-138): normalize chain name to DeFi Oracle Meta Mainnet across docs + pr-ready assets
2026-04-19 19:52:47 +00:00
eip155-138-package
docs(chain-138): normalize chain name to DeFi Oracle Meta Mainnet across docs + pr-ready assets
2026-04-19 19:52:47 +00:00
eip155-138.json
docs(chain-138): normalize chain name to DeFi Oracle Meta Mainnet across docs + pr-ready assets
2026-04-19 19:52:47 +00:00
README.md
docs(chain-138): normalize chain name to DeFi Oracle Meta Mainnet across docs + pr-ready assets
2026-04-19 19:52:47 +00:00
trust-wallet-registry-chain138.json
docs(chain-138): normalize chain name to DeFi Oracle Meta Mainnet across docs + pr-ready assets
2026-04-19 19:52:47 +00:00

README.md

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).

1. Chainlist (ethereum-lists/chains)

Repo: https://github.com/ethereum-lists/chains
Action: Add or update _data/chains/eip155-138.json.

File: eip155-138.json — lists only public RPC nodes (Core and Private RPC nodes are excluded). Packaged copy: eip155-138-package/eip155-138.chainlist.json

Steps:

  1. Fork https://github.com/ethereum-lists/chains
  2. Copy eip155-138.json to _data/chains/eip155-138.json in your fork
  3. Commit, push, open PR. In the PR description paste the "Chain 138 spec" from ADD_CHAIN138_TO_TRUST_WALLET.md
  4. Follow their CONTRIBUTING.md and respond to review

Note: Chain 138 may already be listed (see https://chainlist.org/chain/138). If so, use this file only to propose updates.

2. Trust Wallet

There are two different Trust Wallet paths:

  1. Wallet Core / built-in chain support 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).
  2. Assets / token logos Use the Assets App: https://assets.trustwallet.com Action: submit token logos and metadata for supported chains.
  3. New chain business workflow Trust’s current assets docs say new chain requests should go through their Business Development contact path, even when Wallet Core technical work is also needed.

Wallet Core file: trust-wallet-registry-chain138.json Packaged copy: eip155-138-package/trust-wallet-registry-chain138.json

Wallet Core steps:

  1. Clone trustwallet/wallet-core and follow Trust – New EVM chain
  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

Assets / logo path: Use assets.trustwallet.com for token/logo submissions on supported networks. Full guide: ADD_CHAIN138_TO_TRUST_WALLET.md

2a. Packaged Submission Directory

Directory: eip155-138-package/

This folder is the operator-friendly handoff bundle for DeFi Oracle Meta Mainnet (eip155-138). It contains:

  • a Chainlist-ready JSON copy
  • a Trust Wallet Wallet Core registry entry copy
  • a manifest with canonical source paths

The canonical editable files remain:

Rebuild the package after updates with:

bash scripts/verify/build-chain138-pr-ready-package.sh

3. Ledger (after they respond)

When Ledger confirms the request, use 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 and export from the report API, then submit via platform forms.

Reference in New Issue View Git Blame Copy Permalink