d-bis/proxmox

Fork 0

Files

defiQUG b8613905bd

Deploy to Phoenix / validate (push) Failing after 15s

Details

Deploy to Phoenix / deploy (push) Has been skipped

Details

chore: sync workspace — configs, docs, scripts, CI, pnpm, submodules

- Submodule pins: dbis_core, cross-chain-pmm-lps, mcp-proxmox (local, push may be pending), metamask-integration, smom-dbis-138
- Atomic swap + cross-chain-pmm-lops-publish, deploy-portal workflow, phoenix deploy-targets, routing/aggregator matrices
- Docs, token-lists, forge proxy, phoenix API, runbooks, verify scripts

Made-with: Cursor

2026-04-21 22:01:33 -07:00

3.8 KiB

Raw Blame History

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:

Fork https://github.com/ethereum-lists/chains
Copy eip155-138.json to _data/chains/eip155-138.json in your fork
Commit, push, open PR. In the PR description paste the "Chain 138 spec" from ADD_CHAIN138_TO_TRUST_WALLET.md
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:

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).
Assets / token logos Use the Assets App: https://assets.trustwallet.com Action: submit token logos and metadata for supported chains.
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:

Clone trustwallet/wallet-core and follow Trust – New EVM chain
Add the JSON entry from trust-wallet-registry-chain138.json to the registry file (path may be registry.json or under registry/; check repo)
Run codegen: ./tools/new-evmchain dfiometa (use registry id, not chainId 138; requires Rust/cargo)
Extend derivation tests if required
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.

3.8 KiB Raw Blame History Unescape Escape