d-bis/proxmox
4
0
Fork 0
Code Issues 2 Pull Requests 13 Actions Packages Projects Releases Wiki Activity

docs(chain-138): normalize chain name to DeFi Oracle Meta Mainnet across docs + pr-ready assets
Some checks failed
AI Code Review / claude-review (pull_request) Failing after 31s
Details

Browse Source 
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.
This commit is contained in:
Devin AI
2026-04-19 19:52:47 +00:00
parent 4fab998e51
commit 7aa5162c5b
45 changed files with 92 additions and 92 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/00-meta/NEXT_STEPS_FOR_YOU.md
View File

@@ -27,7 +27,7 @@
## 1. Submit Ledger Live request — ✅ Done
The Ledger Live integration request for **Chain 138 (Defi Oracle Meta Mainnet)** has been submitted (Tally form). Await Ledger’s response and follow their process (agreement + integration steps).
The Ledger Live integration request for **Chain 138 (DeFi Oracle Meta Mainnet)** has been submitted (Tally form). Await Ledger’s response and follow their process (agreement + integration steps).
**Full guide:** [docs/04-configuration/ADD_CHAIN138_TO_LEDGER_LIVE.md](../04-configuration/ADD_CHAIN138_TO_LEDGER_LIVE.md)

2
docs/00-meta/REMAINING_WORK_BREAKDOWN_AND_ANSWERS.md
View File

@@ -24,7 +24,7 @@
| Question | Answer |
|----------|--------|
| **What is it?** | Chain 138 (Defi Oracle Meta Mainnet) added to Ledger Live’s supported networks so users see balances and send/receive on 138 in the app. |
| **What is it?** | Chain 138 (DeFi Oracle Meta Mainnet) added to Ledger Live’s supported networks so users see balances and send/receive on 138 in the app. |
| **Prerequisites** | Form already submitted (Tally). Nothing else you can do until Ledger replies. |
| **Who** | You (point of contact). After Ledger responds, you or dev follow their 8-step process. |
| **Steps to complete** | 1. **Now:** Wait for Ledger’s reply to the Tally form. 2. **When they reply:** Sign any agreement they send; follow their “Adding your blockchain to Ledger Wallet” steps (currency registration, device app, explorer, etc.). 3. **If they ask for PR/code:** Push materials from `~/projects/LedgerLive`, share link. 4. **After chain is live in Ledger Live:** Run Step 8 manual test plan (sync, receive, balance, broadcast) from `~/projects/LedgerLive/step-08-manual-tests/test-plan.md`. |

2
docs/01-getting-started/METAMASK_QUICK_START_GUIDE.md
View File

@@ -22,7 +22,7 @@
2. Click network dropdown (top of MetaMask)
3. Click "Add Network" → "Add a network manually"
4. Enter the following:
- **Network Name**: `Defi Oracle Meta Mainnet` or `SMOM-DBIS-138`
- **Network Name**: `DeFi Oracle Meta Mainnet` or `SMOM-DBIS-138`
- **RPC URL**: `https://rpc-http-pub.d-bis.org` ⚠️ **Important: Must be public endpoint**
- **Chain ID**: `138` (must be decimal, not hex)
- **Currency Symbol**: `ETH`

16
docs/04-configuration/ADD_CHAIN138_TO_LEDGER_LIVE.md
View File

@@ -1,4 +1,4 @@
# Add Chain 138 (Defi Oracle Meta Mainnet) to Ledger Live
# Add Chain 138 (DeFi Oracle Meta Mainnet) to Ledger Live
**Last Updated:** 2026-02-13
**Status:** Action plan and submission guide
@@ -16,9 +16,9 @@ The form has been submitted. Next: await Ledger’s response and follow their pr
**Copy-paste block:**
```
We would like to add Defi Oracle Meta Mainnet (Chain ID 138) to Ledger Live so users can manage ETH and tokens on this EVM chain natively in Ledger Wallet.
We would like to add DeFi Oracle Meta Mainnet (Chain ID 138) to Ledger Live so users can manage ETH and tokens on this EVM chain natively in Ledger Wallet.
- Chain name: Defi Oracle Meta Mainnet
- Chain name: DeFi Oracle Meta Mainnet
- Chain ID: 138 (0x8a)
- EVM-compatible (EIP-155, EIP-1559), standard derivation 44'/60'
- Public RPCs and block explorer are live; chain is listed on Chainlist (chainlist.org/chain/138).
@@ -37,7 +37,7 @@ Preferred contact: [your email/Telegram]
## Overview
Ledger Live does not support user-added custom EVM networks. To have **Defi Oracle Meta Mainnet (Chain ID 138)** appear and work in Ledger Live (desktop/mobile), the chain must be added to Ledger’s supported list via their **official blockchain integration process**.
Ledger Live does not support user-added custom EVM networks. To have **DeFi Oracle Meta Mainnet (Chain ID 138)** appear and work in Ledger Live (desktop/mobile), the chain must be added to Ledger’s supported list via their **official blockchain integration process**.
This doc gives the steps and materials to request and support that integration.
@@ -52,12 +52,12 @@ This doc gives the steps and materials to request and support that integration.
1. **Open the Ledger blockchain integration request form:**
**https://tally.so/r/mORpv8**
2. **Fill in the form** (e.g. “What are you looking from Ledger?”) with a short request to add **Defi Oracle Meta Mainnet (Chain ID 138)** to Ledger Live. Suggested text:
2. **Fill in the form** (e.g. “What are you looking from Ledger?”) with a short request to add **DeFi Oracle Meta Mainnet (Chain ID 138)** to Ledger Live. Suggested text:
```
We would like to add Defi Oracle Meta Mainnet (Chain ID 138) to Ledger Live so users can manage ETH and tokens on this EVM chain natively in Ledger Wallet.
We would like to add DeFi Oracle Meta Mainnet (Chain ID 138) to Ledger Live so users can manage ETH and tokens on this EVM chain natively in Ledger Wallet.
- Chain name: Defi Oracle Meta Mainnet
- Chain name: DeFi Oracle Meta Mainnet
- Chain ID: 138 (0x8a)
- EVM-compatible (EIP-155, EIP-1559), standard derivation 44'/60'
- Public RPCs and block explorer are live; chain is listed on Chainlist (chainlist.org/chain/138).
@@ -103,7 +103,7 @@ Our canonical chain spec is in this repo at `pr-workspace/chains/_data/chains/ei
| Field | Value |
|-------|--------|
| **name** | Defi Oracle Meta Mainnet |
| **name** | DeFi Oracle Meta Mainnet |
| **chainId** | 138 |
| **networkId** | 1 |
| **shortName** | dfio-meta-main |

12
docs/04-configuration/ADD_CHAIN138_TO_TRUST_WALLET.md
View File

@@ -1,4 +1,4 @@
# Add Chain 138 (Defi Oracle Meta Mainnet) to Trust Wallet
# Add Chain 138 (DeFi Oracle Meta Mainnet) to Trust Wallet
**Last Updated:** 2026-04-17
**Status:** User workaround available; official support via Wallet Core PR; token/logo submissions use Assets App; new chain business workflow may still require Trust review outside the repo path
@@ -23,14 +23,14 @@
## Option 1: Users add Chain 138 manually (available now)
Trust Wallet allows adding custom EVM networks in the app. Because **Chain 138 is listed on Chainlist**, users can add Defi Oracle Meta Mainnet without waiting for official support.
Trust Wallet allows adding custom EVM networks in the app. Because **Chain 138 is listed on Chainlist**, users can add DeFi Oracle Meta Mainnet without waiting for official support.
### Steps for users
1. **Get network info:** Open [chainlist.org/chain/138](https://chainlist.org/chain/138) and pick an RPC with a green status.
2. **In Trust Wallet:** Tap the **manage assets** icon → **+** → switch to the **Network** tab.
3. **Enter network details:** Choose **EVM**, then fill in (or paste from Chainlist):
- **Network name:** Defi Oracle Meta Mainnet
- **Network name:** DeFi Oracle Meta Mainnet
- **RPC URL:** e.g. `https://rpc-http-pub.d-bis.org` or `https://rpc.d-bis.org`
- **Chain ID:** 138
- **Symbol:** ETH
@@ -65,7 +65,7 @@ Important: Trust’s current asset-listing docs separate **new token/logo submis
```json
{
"id": "dfiometa",
"name": "Defi Oracle Meta Mainnet",
"name": "DeFi Oracle Meta Mainnet",
"coinId": 10000138,
"symbol": "ETH",
"decimals": 18,
@@ -113,9 +113,9 @@ When contacting Trust or writing the PR description, you can use:
**Copy-paste block:**
```
Defi Oracle Meta Mainnet (Chain ID 138) — EVM-compatible chain for Trust Wallet support.
DeFi Oracle Meta Mainnet (Chain ID 138) — EVM-compatible chain for Trust Wallet support.
- Chain name: Defi Oracle Meta Mainnet
- Chain name: DeFi Oracle Meta Mainnet
- Chain ID: 138 (0x8a)
- Derivation: m/44'/60'/0'/0/0 (standard EVM)
- Native currency: ETH, 18 decimals

8
docs/04-configuration/CHAIN138_WALLET_CONFIG_VALIDATION.md
View File

@@ -6,7 +6,7 @@
---
**Purpose**: Validated configs for MetaMask, ethers.js, and Ledger (Chain 138 – Defi Oracle Meta Mainnet).
**Purpose**: Validated configs for MetaMask, ethers.js, and Ledger (Chain 138 – DeFi Oracle Meta Mainnet).
**RPC**: `https://rpc-http-pub.d-bis.org`, `https://rpc.d-bis.org`, `https://rpc2.d-bis.org`, `https://rpc.defi-oracle.io`
**WS**: `wss://rpc-ws-pub.d-bis.org`, `wss://rpc.d-bis.org`, `wss://ws.rpc.d-bis.org`, `wss://ws.rpc2.d-bis.org`, `wss://wss.defi-oracle.io`
**Chain ID**: 138 (`0x8a`)
@@ -19,7 +19,7 @@ Use **Settings → Networks → Add network** (or “Add a network manually”)
| Field | Value |
|-------|--------|
| **Network name** | Defi Oracle Meta Mainnet |
| **Network name** | DeFi Oracle Meta Mainnet |
| **RPC URL** | `https://rpc-http-pub.d-bis.org`, `https://rpc.d-bis.org`, `https://rpc2.d-bis.org`, or `https://rpc.defi-oracle.io` |
| **Chain ID** | `138` |
| **Currency symbol** | ETH |
@@ -34,10 +34,10 @@ Validated: chainId `0x8a`, RPC URLs return `eth_chainId` → `0x8a`.
## 2. ethers.js (v5 / v6)
```javascript
// Chain 138 – Defi Oracle Meta Mainnet
// Chain 138 – DeFi Oracle Meta Mainnet
const chain138 = {
chainId: 138,
name: "Defi Oracle Meta Mainnet",
name: "DeFi Oracle Meta Mainnet",
nativeCurrency: { name: "Ether", symbol: "ETH", decimals: 18 },
rpcUrls: {
default: { http: ["https://rpc-http-pub.d-bis.org", "https://rpc.d-bis.org", "https://rpc2.d-bis.org", "https://rpc.defi-oracle.io"] },

2
docs/04-configuration/CHAIN138_WALLET_ECOSYSTEM_AND_RATIONALE.md
View File

@@ -7,7 +7,7 @@
## Purpose
This document ties together **all** wallet-related work for **Defi Oracle Meta Mainnet (Chain ID 138)** and answers:
This document ties together **all** wallet-related work for **DeFi Oracle Meta Mainnet (Chain ID 138)** and answers:
1. **Why we created the MetaMask Snap** when basic Chain 138 connectivity already works in MetaMask.
2. **Why we need Ledger Live** when we already use Ledger’s App-Ethereum (and have Chain 138 in our app-ethereum fork).

12
docs/04-configuration/LEDGER_CHAIN138_ISSUES_AND_WORKAROUNDS.md
View File

@@ -1,4 +1,4 @@
# Ledger Ethereum App & Ledger Live — Defi Oracle Meta Mainnet (Chain ID 138) Issues and Workarounds
# Ledger Ethereum App & Ledger Live — DeFi Oracle Meta Mainnet (Chain ID 138) Issues and Workarounds
**Last Updated:** 2026-02-12
**Status:** Active reference for support and integration
@@ -12,7 +12,7 @@
| **Ledger Ethereum App (device)** | ⚠️ Depends on build | Chain 138 is in **this repo’s** app-ethereum config; official Ledger app may not include it. |
| **Ledger Live (desktop/mobile)** | ❌ No native support | Cannot add custom EVM networks; Chain 138 not in Ledger Live’s list. |
| **Workaround** | ✅ Supported | Use **Ledger device + MetaMask** (or other wallet); add Chain 138 in the wallet via Chainlist or manually. |
| **Chainlist** | ✅ Listed | Defi Oracle Meta Mainnet (138) is on chainlist.org; RPCs and explorer configured. |
| **Chainlist** | ✅ Listed | DeFi Oracle Meta Mainnet (138) is on chainlist.org; RPCs and explorer configured. |
---
@@ -60,7 +60,7 @@ So **any build produced from this repo’s app-ethereum** can show “Defi Oracl
### 2.1 No custom EVM network support
- Ledger Live only supports a **fixed list** of networks (Ethereum, Polygon, Arbitrum, Base, etc.).
- **Defi Oracle Meta Mainnet (Chain ID 138) is not in that list.**
- **DeFi Oracle Meta Mainnet (Chain ID 138) is not in that list.**
- There is **no in-app “Add custom network”** for arbitrary EVM chains in Ledger Live.
### 2.2 What users cannot do in Ledger Live
@@ -84,7 +84,7 @@ Official Ledger support also recommends using [Chainlist to connect MetaMask to
### 3.1 Add Chain 138 via Chainlist
1. Go to [chainlist.org](https://chainlist.org) and connect **MetaMask** (with Ledger connected and selected as account).
2. Search for **“Defi Oracle Meta Mainnet”** or **Chain ID 138**.
2. Search for **“DeFi Oracle Meta Mainnet”** or **Chain ID 138**.
3. Click **“Add to MetaMask”** (or equivalent) and approve in MetaMask.
Chain 138 is listed with RPCs and explorer; Chainlist will inject the correct RPC URL and chain ID.
@@ -95,7 +95,7 @@ If not using Chainlist, use **Settings → Networks → Add network** with:
| Field | Value |
|-------|--------|
| Network name | Defi Oracle Meta Mainnet |
| Network name | DeFi Oracle Meta Mainnet |
| RPC URL | `https://rpc-http-pub.d-bis.org` or `https://rpc.d-bis.org` or `https://rpc.defi-oracle.io` |
| Chain ID | `138` |
| Currency symbol | ETH |
@@ -113,7 +113,7 @@ See also: [CHAIN138_WALLET_CONFIG_VALIDATION.md](./CHAIN138_WALLET_CONFIG_VALIDA
## 4. Chainlist and discovery
- **Chain 138** is registered as **Defi Oracle Meta Mainnet** on Chainlist (e.g. `https://chainlist.org/chain/138`).
- **Chain 138** is registered as **DeFi Oracle Meta Mainnet** on Chainlist (e.g. `https://chainlist.org/chain/138`).
- This repo’s chain data: **`pr-workspace/chains/_data/chains/eip155-138.json`** includes:
- RPCs: `rpc-http-pub.d-bis.org`, `rpc.d-bis.org`, `rpc2.d-bis.org`, `rpc.public-0138.defi-oracle.io`, `rpc.defi-oracle.io`, thirdweb (with API key placeholder), and matching WSS URLs.
- Explorer: `https://explorer.d-bis.org`.

2
docs/04-configuration/NEXT_STEPS_CHAIN138_RPC.md
View File

@@ -1,4 +1,4 @@
# Next Steps: Chain 138 RPC (Defi Oracle Meta Mainnet) – Complete with .env
# Next Steps: Chain 138 RPC (DeFi Oracle Meta Mainnet) – Complete with .env
**Last Updated:** 2026-01-31
**Document Version:** 1.0

4
docs/04-configuration/PR_ADDITIONS_VALIDATION_REPORT.md
View File

@@ -43,7 +43,7 @@ cd /home/intlc/projects/token-lists && npm install && npx ajv validate -s src/to
| Field | Required | Our value | Status |
|-------|----------|-----------|--------|
| **name** | ✅ | "Defi Oracle Meta Mainnet" | ✅ |
| **name** | ✅ | "DeFi Oracle Meta Mainnet" | ✅ |
| **shortName** | ✅ | "dfio-meta-main" — pattern `^[A-Za-z0-9-_]{1,64}$` | ✅ |
| **chain** | ✅ | "dfiometa" | ✅ |
| **chainId** | ✅ | 138 | ✅ |
@@ -83,7 +83,7 @@ npx prettier --write _data/chains/eip155-138.json
| Field | Requirement | Our value | Status |
|-------|--------------|-----------|--------|
| **id** | lowercase, never change | "dfiometa" | ✅ |
| **name** | readable | "Defi Oracle Meta Mainnet" | ✅ |
| **name** | readable | "DeFi Oracle Meta Mainnet" | ✅ |
| **coinId** | 10000000 + chainId for EVM clones | 10000138 | ✅ |
| **symbol** | native coin | "ETH" | ✅ |
| **decimals** | 18 | 18 | ✅ |

2
docs/04-configuration/README.md
View File

@@ -66,7 +66,7 @@ This directory contains setup and configuration guides.
**Chain 138 / Wallets (overview first; all repos in ~/projects/):**
- **[CHAIN138_WALLET_REPOSITORIES.md](CHAIN138_WALLET_REPOSITORIES.md)** ⭐⭐⭐ - **Canonical layout:** metamask-integration, LedgerLive, app-ethereum, TrustWallet-Integration each in `~/projects/`. All items **Yes / Completed.**
- **[CHAIN138_WALLET_ECOSYSTEM_AND_RATIONALE.md](CHAIN138_WALLET_ECOSYSTEM_AND_RATIONALE.md)** ⭐⭐⭐ - **Why** we have the MetaMask Snap, **why** we need Ledger Live when we already use App-Ethereum, Trust Wallet support; links to all wallet docs.
- **[ADD_CHAIN138_TO_LEDGER_LIVE.md](ADD_CHAIN138_TO_LEDGER_LIVE.md)** ⭐⭐ - Add Defi Oracle Meta Mainnet (Chain 138) to Ledger Live (request + materials).
- **[ADD_CHAIN138_TO_LEDGER_LIVE.md](ADD_CHAIN138_TO_LEDGER_LIVE.md)** ⭐⭐ - Add DeFi Oracle Meta Mainnet (Chain 138) to Ledger Live (request + materials).
- **[ADD_CHAIN138_TO_TRUST_WALLET.md](ADD_CHAIN138_TO_TRUST_WALLET.md)** ⭐⭐ - Add Chain 138 to Trust Wallet (user manual add via Chainlist; official Wallet Core PR steps; materials in ~/projects/TrustWallet-Integration).
- **[CHAIN138_WALLET_PROJECTS_COMPLETION_REVIEW.md](CHAIN138_WALLET_PROJECTS_COMPLETION_REVIEW.md)** ⭐⭐ - **Completion and test review:** all four projects verified; MetaMask E2E 7/7 + Snap unit tests pass; Ledger/app-ethereum/Trust status.

2
docs/04-configuration/RPC_CHAIN138_VERIFICATION.md
View File

@@ -25,7 +25,7 @@ Full stack has been proven correct:
| **Proxy** | NPMplus (192.168.11.167:443) routes by Host header correctly |
| **Upstream** | Besu RPC (192.168.11.221:8545 / :8546) reachable |
| **RPC response** | `eth_chainId` → **0x8a** |
| **Chain ID** | **0x8a = 138** (Defi Oracle Meta Mainnet) |
| **Chain ID** | **0x8a = 138** (DeFi Oracle Meta Mainnet) |
Validation command (bypasses public IP; connects directly to NPMplus on LAN):

4
docs/04-configuration/RPC_VERIFICATION_MEMO.md
View File

@@ -1,4 +1,4 @@
# RPC Verification Memo – Chain 138 (Defi Oracle Meta Mainnet)
# RPC Verification Memo – Chain 138 (DeFi Oracle Meta Mainnet)
**Last Updated:** 2026-01-31
**Document Version:** 1.0
@@ -44,7 +44,7 @@ Response: eth_chainId → 0x8a (Chain ID 138)
| **Proxy** | NPMplus routes by Host to VMID 2201 |
| **Upstream** | Besu RPC (192.168.11.221:8545 / :8546) reachable and responsive |
| **RPC** | `eth_chainId` returns `0x8a` (138) |
| **Chain** | Defi Oracle Meta Mainnet – sovereign EVM, no mainnet/testnet collision |
| **Chain** | DeFi Oracle Meta Mainnet – sovereign EVM, no mainnet/testnet collision |
**Validation command** (from a host that can reach NPMplus, e.g. LAN with Split DNS or `--resolve`):

2
docs/04-configuration/coingecko/COINGECKO_API_NO_PUSH_LIQUIDITY.md
View File

@@ -35,7 +35,7 @@ So:
2. **Create liquidity pools** on DEXes that GeckoTerminal indexes (e.g. Uniswap, SushiSwap, etc.) on that chain.
3. CoinGecko/GeckoTerminal will **automatically** pick up those pools from on-chain data. No API push.
### For Chain 138 (Defi Oracle Meta Mainnet)
### For Chain 138 (DeFi Oracle Meta Mainnet)
1. **Submit** the chain and tokens via CoinGecko’s listing process.
2. **Provide your report API URL** (e.g. `https://<your-api>/api/v1/report/coingecko?chainId=138`) so CoinGecko can **pull** token and liquidity data from your Token Aggregation Service.

4
docs/04-configuration/coingecko/COINGECKO_SUBMISSION_CUSDC.md
View File

@@ -8,7 +8,7 @@
**Date:** 2026-01-27
**Token:** cUSDC (Compliant USD Coin)
**ChainID:** 138 (DBIS Chain / Defi Oracle Meta Mainnet)
**ChainID:** 138 (DBIS Chain / DeFi Oracle Meta Mainnet)
---
@@ -22,7 +22,7 @@
| **Token Symbol** | cUSDC |
| **Contract Address** | `0xf22258f57794CC8E06237084b353Ab30fFfa640b` |
| **Chain ID** | 138 |
| **Chain Name** | DBIS Chain (Defi Oracle Meta Mainnet) |
| **Chain Name** | DBIS Chain (DeFi Oracle Meta Mainnet) |
| **Decimals** | 6 |
| **Token Type** | ERC-20 Stablecoin |
| **Peg** | USD (1:1) |

4
docs/04-configuration/coingecko/COINGECKO_SUBMISSION_CUSDT.md
View File

@@ -8,7 +8,7 @@
**Date:** 2026-01-27
**Token:** cUSDT (Compliant Tether USD)
**ChainID:** 138 (DBIS Chain / Defi Oracle Meta Mainnet)
**ChainID:** 138 (DBIS Chain / DeFi Oracle Meta Mainnet)
---
@@ -22,7 +22,7 @@
| **Token Symbol** | cUSDT |
| **Contract Address** | `0x93E66202A11B1772E55407B32B44e5Cd8eda7f22` |
| **Chain ID** | 138 |
| **Chain Name** | DBIS Chain (Defi Oracle Meta Mainnet) |
| **Chain Name** | DBIS Chain (DeFi Oracle Meta Mainnet) |
| **Decimals** | 6 |
| **Token Type** | ERC-20 Stablecoin |
| **Peg** | USD (1:1) |

2
docs/04-configuration/coingecko/COINGECKO_SUBMISSION_GUIDE.md
View File

@@ -108,7 +108,7 @@ This guide provides step-by-step instructions for submitting cUSDT and cUSDC tok
- Decimals: 6
**Network Information:**
- Network Name: "DBIS Chain" or "Defi Oracle Meta Mainnet"
- Network Name: "DBIS Chain" or "DeFi Oracle Meta Mainnet"
- RPC URL: `https://rpc-http-pub.d-bis.org`
- Block Explorer: `https://explorer.d-bis.org`

2
docs/04-configuration/metamask/METAMASK_NETWORK_CONFIG.json
View File

@@ -1,7 +1,7 @@
{
"chainId": "0x8a",
"chainIdDecimal": 138,
"chainName": "Defi Oracle Meta Mainnet",
"chainName": "DeFi Oracle Meta Mainnet",
"rpcUrls": [
"https://rpc-http-pub.d-bis.org",
"https://rpc.d-bis.org",

4
docs/04-configuration/pr-ready/README.md
View File

@@ -1,6 +1,6 @@
# 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)).
**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)).
---
@@ -52,7 +52,7 @@ There are two different Trust Wallet paths:
**Directory:** [eip155-138-package/](./eip155-138-package/)
This folder is the operator-friendly handoff bundle for Defi Oracle Meta Mainnet (`eip155-138`). It contains:
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

2
docs/04-configuration/pr-ready/chain138-asset-package/README.md
View File

@@ -1,6 +1,6 @@
# Chain 138 Asset Submission Package
**Chain:** Defi Oracle Meta Mainnet
**Chain:** DeFi Oracle Meta Mainnet
**Chain ID:** 138
**CAIP-2:** `eip155:138`

2
docs/04-configuration/pr-ready/chain138-asset-package/listing-token-submissions.chain138.json
View File

@@ -1,6 +1,6 @@
{
"chainId": 138,
"chainName": "Defi Oracle Meta Mainnet",
"chainName": "DeFi Oracle Meta Mainnet",
"submissionType": "listing_surfaces",
"surfaceNotes": {
"walletCore": "Chain metadata only. No token assets, bridge listings, or pool listings.",

2
docs/04-configuration/pr-ready/chain138-asset-package/manifest.json
View File

@@ -1,6 +1,6 @@
{
"name": "Chain 138 Asset Submission Package",
"chainName": "Defi Oracle Meta Mainnet",
"chainName": "DeFi Oracle Meta Mainnet",
"chainId": 138,
"caip2": "eip155:138",
"purpose": "Submission bundle for Chain 138 token assets across wallet and listing surfaces.",

2
docs/04-configuration/pr-ready/chain138-asset-package/wallet-token-submissions.chain138.json
View File

@@ -1,6 +1,6 @@
{
"chainId": 138,
"chainName": "Defi Oracle Meta Mainnet",
"chainName": "DeFi Oracle Meta Mainnet",
"submissionType": "wallet_assets",
"notes": [
"This file is for wallet-facing token asset metadata, not Wallet Core chain support.",

4
docs/04-configuration/pr-ready/eip155-138-package/README.md
View File

@@ -1,6 +1,6 @@
# Defi Oracle Meta Mainnet PR-Ready Package
# DeFi Oracle Meta Mainnet PR-Ready Package
**Chain:** Defi Oracle Meta Mainnet
**Chain:** DeFi Oracle Meta Mainnet
**Chain ID:** 138
**CAIP-2:** `eip155:138`

2
docs/04-configuration/pr-ready/eip155-138-package/eip155-138.chainlist.json
View File

@@ -1,5 +1,5 @@
{
"name": "Defi Oracle Meta Mainnet",
"name": "DeFi Oracle Meta Mainnet",
"chain": "dfiometa",
"rpc": [
"https://rpc-http-pub.d-bis.org",

2
docs/04-configuration/pr-ready/eip155-138-package/manifest.json
View File

@@ -1,5 +1,5 @@
{
"name": "Defi Oracle Meta Mainnet PR-Ready Package",
"name": "DeFi Oracle Meta Mainnet PR-Ready Package",
"chainId": 138,
"caip2": "eip155:138",
"generatedBy": "scripts/verify/build-chain138-pr-ready-package.sh",

2
docs/04-configuration/pr-ready/eip155-138-package/trust-wallet-registry-chain138.json
View File

@@ -1,6 +1,6 @@
{
"id": "dfiometa",
"name": "Defi Oracle Meta Mainnet",
"name": "DeFi Oracle Meta Mainnet",
"coinId": 10000138,
"symbol": "ETH",
"decimals": 18,

2
docs/04-configuration/pr-ready/eip155-138.json
View File

@@ -1,5 +1,5 @@
{
"name": "Defi Oracle Meta Mainnet",
"name": "DeFi Oracle Meta Mainnet",
"chain": "dfiometa",
"rpc": [
"https://rpc-http-pub.d-bis.org",

2
docs/04-configuration/pr-ready/trust-wallet-registry-chain138.json
View File

@@ -1,6 +1,6 @@
{
"id": "dfiometa",
"name": "Defi Oracle Meta Mainnet",
"name": "DeFi Oracle Meta Mainnet",
"coinId": 10000138,
"symbol": "ETH",
"decimals": 18,

6
docs/09-troubleshooting/METAMASK_TROUBLESHOOTING_GUIDE.md
View File

@@ -25,11 +25,11 @@
1. **Remove and Re-add Network with Correct RPC URL**
- MetaMask → Settings → Networks
- Find "Defi Oracle Meta Mainnet" or "SMOM-DBIS-138"
- Find "DeFi Oracle Meta Mainnet" or "SMOM-DBIS-138"
- Click "Delete" or "Remove"
- Click "Add Network" → "Add a network manually"
- Enter these exact values:
- **Network Name**: `Defi Oracle Meta Mainnet`
- **Network Name**: `DeFi Oracle Meta Mainnet`
- **RPC URL**: `https://rpc-http-pub.d-bis.org`
- **Chain ID**: `138` (must be decimal, not hex)
- **Currency Symbol**: `ETH`
@@ -477,7 +477,7 @@ curl -X POST https://rpc-http-pub.d-bis.org \
Run through this checklist when troubleshooting:
- [ ] Network is "Defi Oracle Meta Mainnet" or "SMOM-DBIS-138" (ChainID 138)
- [ ] Network is "DeFi Oracle Meta Mainnet" or "SMOM-DBIS-138" (ChainID 138)
- [ ] RPC URL is `https://rpc-http-pub.d-bis.org` (public endpoint, no auth)
- [ ] Chain ID is `138` (decimal, not hex)
- [ ] RPC endpoint does NOT require JWT authentication

4
docs/11-references/CHAINS_AND_PROTOCOLS_BRIDGE_INTEGRATION.md
View File

@@ -116,7 +116,7 @@ To move Gnosis (100), Celo (42220), and Wemix (1111) from **Config ready** to **
- **Entry:** `pr-workspace/chains/_data/chains/eip155-138.json`
- **Public URL:** https://chainlist.org/chain/138
- **Chain name:** Defi Oracle Meta Mainnet
- **Chain name:** DeFi Oracle Meta Mainnet
- **RPCs:** d-bis.org, defi-oracle.io, thirdweb
- **Explorer:** https://explorer.d-bis.org (Blockscout)
@@ -128,7 +128,7 @@ Ledger Live and other clients can discover ChainID 138 RPCs via Chainlist.
**Status:** ✅ **Accepted and supported**
- **Chainlist:** Listed as "Defi Oracle Meta Mainnet" (Chain ID 138)
- **Chainlist:** Listed as "DeFi Oracle Meta Mainnet" (Chain ID 138)
- **Bridge:** Supports bridging to and from Defi Oracle Meta
- **RPC:** `https://138.rpc.thirdweb.com`, `https://defi-oracle-meta.rpc.thirdweb.com`
- **Explorer:** https://blockscout.defi-oracle.io

8
docs/11-references/DEFI_ORACLE_META_MAINNET_PROJECT_DESCRIPTION.md
View File

@@ -1,4 +1,4 @@
# Defi Oracle Meta Mainnet (Chain ID 138) — Project Description
# DeFi Oracle Meta Mainnet (Chain ID 138) — Project Description
**Last Updated:** 2026-02-12
**Purpose:** Reusable project descriptions for listings, Ledger, Chainlist, CoinGecko, outreach, and documentation.
@@ -10,10 +10,10 @@
**For:** Forms, badges, meta tags, character-limited fields.
**Option A (technical):**
Defi Oracle Meta Mainnet (Chain ID 138) is an EVM-compatible blockchain built on Hyperledger Besu with QBFT consensus, offering ~2s block time, native oracle integration, and CCIP cross-chain bridges.
DeFi Oracle Meta Mainnet (Chain ID 138) is an EVM-compatible blockchain built on Hyperledger Besu with QBFT consensus, offering ~2s block time, native oracle integration, and CCIP cross-chain bridges.
**Option B (use-case):**
Defi Oracle Meta Mainnet is an enterprise-grade EVM chain (Chain ID 138) with compliant stablecoins, cross-chain bridges (CCIP), and native oracle support for institutional DeFi.
DeFi Oracle Meta Mainnet is an enterprise-grade EVM chain (Chain ID 138) with compliant stablecoins, cross-chain bridges (CCIP), and native oracle support for institutional DeFi.
**Option C (minimal):**
Production EVM chain (Chain ID 138) on Hyperledger Besu with QBFT, CCIP bridges, and Blockscout explorer.
@@ -52,7 +52,7 @@ Use for forms, tables, or “About” sections:
| Item | Value |
|------|--------|
| **Name** | Defi Oracle Meta Mainnet |
| **Name** | DeFi Oracle Meta Mainnet |
| **Chain ID** | 138 (0x8a) |
| **Network ID** | 1 |
| **Consensus** | QBFT (Hyperledger Besu) |

6
docs/11-references/LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE.md
View File

@@ -1,7 +1,7 @@
# Ledger Blockchain Integration — Complete Reference (All Steps)
**Last Updated:** 2026-02-13
**Purpose:** Full 8-step Ledger Wallet blockchain integration with gaps filled. Use for Defi Oracle Meta Mainnet (Chain ID 138) or any EVM chain.
**Purpose:** Full 8-step Ledger Wallet blockchain integration with gaps filled. Use for DeFi Oracle Meta Mainnet (Chain ID 138) or any EVM chain.
**Public code review for Ledger team:** [**bis-innovations/LedgerLive**](https://github.com/bis-innovations/LedgerLive) — use this repo for all Chain 138 integration code, specs, and patches intended for Ledger Live team review.
@@ -35,7 +35,7 @@ defi_oracle_meta_mainnet: {
type: "CryptoCurrency",
id: "defi_oracle_meta_mainnet",
coinType: 60, // SLIP-44 Ethereum
name: "Defi Oracle Meta Mainnet",
name: "DeFi Oracle Meta Mainnet",
managerAppName: "Ethereum",
ticker: "ETH",
countervalueTicker: "ETH",
@@ -215,7 +215,7 @@ Example PRs: [Ethereum adapter](https://github.com/LedgerHQ/ledger-live/pull/318
| Item | Value |
|------|--------|
| Chain name | Defi Oracle Meta Mainnet |
| Chain name | DeFi Oracle Meta Mainnet |
| Chain ID | 138 (0x8a) |
| SLIP-44 | 60 (Ethereum) |
| Derivation | 44'/60'/0'/0/0 |

2
docs/11-references/LINK_TOKEN_ADDRESSES_REFERENCE.md
View File

@@ -4,7 +4,7 @@
---
## Chain 138 (Defi Oracle Meta Mainnet)
## Chain 138 (DeFi Oracle Meta Mainnet)
| Variable | Address | Notes |
|----------|---------|------|

2
docs/GALATIC_SUMMARY.md
View File

@@ -11,7 +11,7 @@
### 1.1 Core Network: Chain 138 (DeFi Oracle Meta Mainnet)
- **Chain ID:** 138
- **Name:** Defi Oracle Meta Mainnet (D-BIS)
- **Name:** DeFi Oracle Meta Mainnet (D-BIS)
- **Consensus:** Besu (EVM); validator set and RPC nodes on Proxmox/LAN.
- **Public RPCs:**
- `https://rpc-http-pub.d-bis.org`, `https://rpc.d-bis.org`, `https://rpc2.d-bis.org`

2
docs/archive/completion/CLOUDFLARED_UPDATE_COMPLETE.md
View File

@@ -70,7 +70,7 @@ curl -X POST https://rpc-http-pub.d-bis.org \
1. **Remove existing network** in MetaMask (if previously added)
2. **Add network manually**:
- Network Name: `Defi Oracle Meta Mainnet`
- Network Name: `DeFi Oracle Meta Mainnet`
- RPC URL: `https://rpc-http-pub.d-bis.org`
- Chain ID: `138`
- Currency Symbol: `ETH`

2
docs/archive/completion/FINAL_BRIDGE_VERIFICATION_COMPLETE.md
View File

@@ -15,7 +15,7 @@
**Source**: [thirdweb Chainlist](https://thirdweb.com/chainlist?query=138)
**Chain Details**:
- Name: Defi Oracle Meta Mainnet
- Name: DeFi Oracle Meta Mainnet
- Chain ID: 138
- Native Token: ETH
- Bridge Service: ✅ Available

6
docs/archive/completion/THIRDWEB_BRIDGE_FINAL_SUMMARY.md
View File

@@ -11,7 +11,7 @@
### ChainID 138 IS Supported by thirdweb Bridge!
**Verified Sources**:
- ✅ [thirdweb Chainlist](https://thirdweb.com/chainlist?query=138) - ChainID 138 listed as "Defi Oracle Meta Mainnet"
- ✅ [thirdweb Chainlist](https://thirdweb.com/chainlist?query=138) - ChainID 138 listed as "DeFi Oracle Meta Mainnet"
- ✅ [Defi Oracle Meta Page](https://thirdweb.com/defi-oracle-meta) - Bridge service confirmed
- ✅ Credentials configured and working
@@ -68,7 +68,7 @@ npm install @thirdweb-dev/react @thirdweb-dev/sdk
1. Go to Bridge tab in project dashboard
2. Settings → "Don't see your token listed?"
3. Submit:
- Chain: Defi Oracle Meta Mainnet (138)
- Chain: DeFi Oracle Meta Mainnet (138)
- Token: `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`
4. Wait 20-40 minutes for route discovery
@@ -92,7 +92,7 @@ npm install @thirdweb-dev/react @thirdweb-dev/sdk
## References
- [thirdweb Chainlist - ChainID 138](https://thirdweb.com/chainlist?query=138)
- [Defi Oracle Meta Mainnet](https://thirdweb.com/defi-oracle-meta)
- [DeFi Oracle Meta Mainnet](https://thirdweb.com/defi-oracle-meta)
- [Bridge FAQ](https://portal.thirdweb.com/bridge/faq)
- [Bridge Widget Documentation](https://portal.thirdweb.com/bridge/widget)

4
docs/archive/fixes/METAMASK_RPC_CHAIN_ID_ERROR_FIX.md
View File

@@ -37,7 +37,7 @@ The most common cause is that the RPC endpoint is requiring **JWT authentication
1. Open MetaMask
2. Click the network dropdown (top center)
3. Click "Settings" (gear icon) or go to Settings → Networks
4. Find "Defi Oracle Meta Mainnet" or "SMOM-DBIS-138"
4. Find "DeFi Oracle Meta Mainnet" or "SMOM-DBIS-138"
5. Click "Delete" or "Remove" to remove the network
### Step 2: Add Network with Correct RPC URL
@@ -46,7 +46,7 @@ The most common cause is that the RPC endpoint is requiring **JWT authentication
2. Enter these **exact** values:
```
Network Name: Defi Oracle Meta Mainnet
Network Name: DeFi Oracle Meta Mainnet
RPC URL: https://rpc-http-pub.d-bis.org
Chain ID: 138
Currency Symbol: ETH

2
docs/archive/fixes/METAMASK_WETH9_FIX_INSTRUCTIONS.md
View File

@@ -27,7 +27,7 @@ Since the contract's `decimals()` function is incorrect, you need to manually sp
### Step-by-Step Instructions
1. **Open MetaMask**
- Make sure you're connected to "Defi Oracle Meta Mainnet" (ChainID 138)
- Make sure you're connected to "DeFi Oracle Meta Mainnet" (ChainID 138)
2. **Go to Import Tokens**
- Click on the token list (where you see "Wrapped Ether")

10
docs/archive/fixes/THIRDWEB_BRIDGE_CORRECTED_ANALYSIS.md
View File

@@ -25,7 +25,7 @@
### ChainID 138 on thirdweb
**Chain Details**:
- **Name**: Defi Oracle Meta Mainnet
- **Name**: DeFi Oracle Meta Mainnet
- **Chain ID**: 138
- **Native Token**: ETH
- **Available Services**: 1
@@ -108,7 +108,7 @@ According to [Bridge FAQ](https://portal.thirdweb.com/bridge/faq):
1. Go to Bridge tab in project dashboard
2. Settings → "Don't see your token listed?"
3. Submit:
- **Chain**: Defi Oracle Meta Mainnet (138)
- **Chain**: DeFi Oracle Meta Mainnet (138)
- **Token Address**: `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`
4. Wait 20-40 minutes for route discovery
@@ -127,7 +127,7 @@ According to [Bridge FAQ](https://portal.thirdweb.com/bridge/faq):
**What Works**:
- ✅ ChainID 138 is supported by thirdweb Bridge
- ✅ Bridge service available for Defi Oracle Meta Mainnet
- ✅ Bridge service available for DeFi Oracle Meta Mainnet
- ✅ Credentials configured and working
- ✅ RPC endpoint available
@@ -185,7 +185,7 @@ If WETH not recognized:
### ✅ Corrected Understanding
1. **ChainID 138 IS Supported**: ✅ Listed as "Defi Oracle Meta Mainnet"
1. **ChainID 138 IS Supported**: ✅ Listed as "DeFi Oracle Meta Mainnet"
2. **Bridge Service Available**: ✅ Confirmed on thirdweb website
3. **Use Bridge Widget**: ✅ Recommended approach
4. **Credentials Ready**: ✅ Already configured
@@ -201,7 +201,7 @@ If WETH not recognized:
## References
- [thirdweb Chainlist - ChainID 138](https://thirdweb.com/chainlist?query=138)
- [Defi Oracle Meta Mainnet](https://thirdweb.com/defi-oracle-meta)
- [DeFi Oracle Meta Mainnet](https://thirdweb.com/defi-oracle-meta)
- [Bridge FAQ](https://portal.thirdweb.com/bridge/faq)
- [Bridge Widget Docs](https://portal.thirdweb.com/bridge/widget)

4
docs/archive/historical/METAMASK_WETH9_DISPLAY_BUG.md
View File

@@ -3,7 +3,7 @@
**Date**: $(date)
**Issue**: MetaMask displaying "6,000,000,000.0T WETH" instead of "6 WETH"
**Contract**: WETH9 (`0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`)
**Network**: Defi Oracle Meta Mainnet (ChainID 138)
**Network**: DeFi Oracle Meta Mainnet (ChainID 138)
---
@@ -147,7 +147,7 @@ If WETH9 cannot be fixed, consider:
- Should verify actual ETH balance
- May be another display formatting issue
2. **Network Name**: "Defi Oracle Meta Mainnet"
2. **Network Name**: "DeFi Oracle Meta Mainnet"
- This is ChainID 138
- Network configuration appears correct

12
docs/archive/historical/THIRDWEB_BRIDGE_CHAIN138_SUPPORTED.md
View File

@@ -13,7 +13,7 @@
**Source**: [thirdweb Chainlist](https://thirdweb.com/chainlist?query=138)
**Chain Details**:
- **Name**: Defi Oracle Meta Mainnet
- **Name**: DeFi Oracle Meta Mainnet
- **Chain ID**: 138
- **Native Token**: ETH
- **Available Services**: 1
@@ -33,7 +33,7 @@
**Previous Test**: Used `/v1/bridge/chains` endpoint which may not include all chains
**Actual Support**: ChainID 138 is supported via thirdweb Bridge service, but may be:
1. Listed under "Defi Oracle Meta Mainnet" name
1. Listed under "DeFi Oracle Meta Mainnet" name
2. Available through Bridge widget/UI rather than direct API
3. Using different API endpoint structure
@@ -70,7 +70,7 @@
### ✅ What's Actually True
1. **ChainID 138 IS Supported**: ✅ Listed as "Defi Oracle Meta Mainnet"
1. **ChainID 138 IS Supported**: ✅ Listed as "DeFi Oracle Meta Mainnet"
2. **Bridge Service Available**: ✅ "Bridge assets to and from Defi Oracle Meta"
3. **RPC Endpoint**: ✅ `https://138.rpc.thirdweb.com`
4. **Credentials Configured**: ✅ Working
@@ -101,7 +101,7 @@
2. Bridge → Settings
3. "Don't see your token listed?"
4. Submit:
- Chain: Defi Oracle Meta Mainnet (138)
- Chain: DeFi Oracle Meta Mainnet (138)
- Token: `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`
- Wait 20-40 minutes
@@ -132,7 +132,7 @@ import { Bridge } from "@thirdweb-dev/react";
**What Changed**:
- ✅ ChainID 138 is listed in thirdweb chainlist
- ✅ Bridge service available for Defi Oracle Meta Mainnet
- ✅ Bridge service available for DeFi Oracle Meta Mainnet
- ✅ RPC endpoint available: `https://138.rpc.thirdweb.com`
**Remaining Questions**:
@@ -167,7 +167,7 @@ import { Bridge } from "@thirdweb-dev/react";
## References
- [thirdweb Chainlist - ChainID 138](https://thirdweb.com/chainlist?query=138)
- [Defi Oracle Meta Mainnet](https://thirdweb.com/defi-oracle-meta)
- [DeFi Oracle Meta Mainnet](https://thirdweb.com/defi-oracle-meta)
- [Bridge FAQ](https://portal.thirdweb.com/bridge/faq)
- [Bridge Widget Documentation](https://portal.thirdweb.com/bridge/widget)

2
reports/DEFI_ORACLE_MAINNET_CONNECTION_GUIDE.md
View File

@@ -76,7 +76,7 @@ Block Explorer URL: https://explorer.d-bis.org
## 🔍 Troubleshooting Connection Issues
### Issue: "Unable to connect to Defi Oracle Meta Mainnet"
### Issue: "Unable to connect to DeFi Oracle Meta Mainnet"
**Possible Causes**:

2
scripts/test-thirdweb-bridge-widget.js
View File

@@ -26,7 +26,7 @@ console.log("ChainID 138 IS Supported!");
console.log("━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n");
console.log("According to thirdweb chainlist:");
console.log(" ✅ ChainID 138: Defi Oracle Meta Mainnet");
console.log(" ✅ ChainID 138: DeFi Oracle Meta Mainnet");
console.log(" ✅ Bridge service available");
console.log(" ✅ RPC: https://138.rpc.thirdweb.com");
console.log("");