Files

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

2.8 KiB

Raw Blame History

RPC Verification Memo – Chain 138 (DeFi Oracle Meta Mainnet)

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

Date: 2026-01-29
Audience: Partners, auditors, operators
Classification: Technical verification summary (one page)

1. Stack overview

Internet / LAN
      │
      ▼
DNS (rpc-http-pub.d-bis.org, rpc.d-bis.org, rpc2.d-bis.org, rpc.defi-oracle.io, etc.) → 76.53.10.36
      │
      ▼
UDM Pro port forward 76.53.10.36:443 → 192.168.11.167:443
      │
      ▼
NPMplus (192.168.11.167:443) – TLS termination, Host-based routing
      │
      ▼
Besu RPC – VMID 2201 (192.168.11.221:8545 HTTP, :8546 WebSocket)
      │
      ▼
Response: eth_chainId → 0x8a (Chain ID 138)

2. Validation results

Check	Result
DNS	Public hostnames resolve to 76.53.10.36
TLS	Valid Let's Encrypt; CN matches hostname; TLS 1.3
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

Validation command (from a host that can reach NPMplus, e.g. LAN with Split DNS or --resolve):

curl -sk --resolve rpc-http-pub.d-bis.org:443:192.168.11.167 \
  https://rpc-http-pub.d-bis.org \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Expected: {"jsonrpc":"2.0","id":1,"result":"0x8a"}

3. Public endpoints

Endpoint	Type	Backend
https://rpc-http-pub.d-bis.org	HTTP RPC	192.168.11.221:8545
wss://rpc-ws-pub.d-bis.org	WebSocket RPC	192.168.11.221:8546
https://rpc.d-bis.org	HTTP RPC	192.168.11.221:8545
https://rpc2.d-bis.org	HTTP RPC	192.168.11.221:8545
wss://ws.rpc.d-bis.org	WebSocket RPC	192.168.11.221:8546
wss://ws.rpc2.d-bis.org	WebSocket RPC	192.168.11.221:8546
https://rpc.defi-oracle.io	HTTP RPC	192.168.11.221:8545
wss://wss.defi-oracle.io	WebSocket RPC	192.168.11.221:8546

Explorer: https://explorer.d-bis.org
Chain ID: 138 (0x8a)

4. Operational notes

LAN access: From inside the same network, public hostnames may not resolve back (NAT hairpin). Use Split DNS (internal A records to 192.168.11.167) or the --resolve curl pattern for testing.
Port forwarding: 76.53.10.36:80 and :443 → 192.168.11.167 (NPMplus). Confirmed on UDM Pro.
No auth: Public RPC endpoints do not require API keys or auth.

5. References

Verification detail: RPC_CHAIN138_VERIFICATION.md
Wallet/SDK configs: CHAIN138_WALLET_CONFIG_VALIDATION.md
IDS/IPS and WebSockets: IDS_IPS_WEBSOCKET_GUIDANCE.md

2.8 KiB Raw Blame History Unescape Escape