Files

defiQUG dbd517b279 Sync workspace: config, docs, scripts, CI, operator rules, and submodule pointers.

- 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

2026-04-12 06:12:20 -07:00

13 KiB

Raw Blame History

Chains & Protocols: Bridges, Ledger, and Integrations

Last Updated: 2026-04-03
Status: Authoritative reference for bridge chains and protocol acceptance

Overview

This document consolidates:

Chains handled by bridges – CCIP, Bridge Vault, Li.Fi, AlltraAdapter
Protocols and wallets that have accepted ChainID 138 – Ledger, Chainlist, thirdweb, MetaMask, etc.
Protocols and wallets that have accepted ALL Mainnet (651940) – Chainlist, MetaMask, etc.

The key normalization for 2026-04 is:

Live EVM CCIP destinations are one bucket.
Alltra is a separate custom bridge bucket.
Truth is a registry adapter on 138 plus an Ethereum ↔ Truth public bridge story, not a direct 138 ↔ Truth CCIP lane.
Tron is a deployed non-EVM adapter on 138 with relay/off-chain dependencies.
Etherlink / Tezos are scaffolded and feature-gated, not live public bridge lanes.
XDC Zero and OP Stack L2 ↔ 138 remain separate programs, not rows in the live CCIP destination matrix.

Part 1: Chains Handled by Bridges

1.0 Canonical bridge-program classification

Program / destination	Chain / ID	Classification	Current repo state	Canonical note
Ethereum Mainnet	`1`	EVM CCIP destination	✅ Live	Standard CCIP WETH9/WETH10 destination
Optimism	`10`	EVM CCIP destination	✅ Live	Standard CCIP destination
Cronos	`25`	EVM CCIP destination	✅ Live	Standard CCIP destination
BSC	`56`	EVM CCIP destination	✅ Live	Standard CCIP destination
Gnosis	`100`	EVM CCIP destination	✅ Live	Treat as live, not merely config-ready
Polygon	`137`	EVM CCIP destination	✅ Live	Standard CCIP destination
Arbitrum One	`42161`	EVM CCIP destination	✅ Live	Standard CCIP destination
Avalanche C-Chain	`43114`	EVM CCIP destination	✅ Live	Standard CCIP destination; separate `avax-cw` GRU corridor also exists
Base	`8453`	EVM CCIP destination	✅ Live	Standard CCIP destination
Celo	`42220`	EVM CCIP destination	✅ Live	Treat as live, not merely config-ready
Wemix	`1111`	EVM CCIP destination	⏳ Pending operator completion	Repo wiring exists; deployment/funding not fully closed
ALL Mainnet	`651940`	Custom Alltra bridge	✅ Live	`AlltraAdapter`, not CCIP
Truth Network	Substrate / non-EVM	Registry adapter + Ethereum Truth bridge	⚠️ Partial / pointer only	No direct 138 ↔ Truth CCIP lane documented
Tron	non-EVM	Adapter + relay program	⚠️ Partial / relay-dependent	`TronAdapter` exists on 138; not part of the CCIP lane table
Solana	non-EVM (SVM)	Adapter + relay program	⚠️ Partial / relay-dependent	`SolanaAdapter` in `smom-dbis-138`; no EIP-155 chain id; not part of the CCIP lane table
Etherlink	`42793`	Scaffold / gated bridge target	⏳ Planned / feature-gated	Placeholder token mapping and runbook tasks exist
Tezos L1	non-EVM	Scaffold / gated bridge target	⏳ Planned / feature-gated	Relay/service plan exists, not live lane
XDC Network	`50`	Parallel bridge program	⚠️ Separate program	`XDC Zero`, not CCIP
OP Stack L2	separate future chain	Future bridge design	⏳ Design only	Optional future L2 ↔ 138 program

1.1 Chainlink CCIP Bridge

Primary use: ChainID 138 ↔ Ethereum cross-chain transfers
Tokens: WETH, WETH10, cUSDT, cUSDC, LINK
Fees: Paid in LINK

Chain	Chain ID	Status
Ethereum Mainnet	1	✅
Optimism	10	✅
Polygon	137	✅
Arbitrum One	42161	✅
Base	8453	✅
BSC (BNB Chain)	56	✅
Avalanche	43114	✅
Gnosis Chain	100	✅
Celo	42220	✅
Wemix	1111	⏳ Pending operator completion
ChainID 138 (DeFi Oracle Meta Mainnet)	138	✅

Deployed CCIP WETH bridges: CCIPWETH9Bridge and CCIPWETH10Bridge on the live EVM destination set above, with Wemix still pending final operator completion.

Additional CCIP selectors tracked in repo: Gnosis Chain (465200170687744372), Celo (1346049177634351622), Wemix (5142893604156789321).

Remaining completion checklist for pending CCIP chain(s)

Wemix (1111) still needs operator completion:

Verify CCIP support — Confirm the current supported-network metadata is still valid.
Deploy bridges — Deploy CCIPWETH9Bridge and CCIPWETH10Bridge on Wemix (see runbook).
Configure destinations — Run smom-dbis-138/scripts/deployment/complete-config-ready-chains.sh with the Wemix bridge addresses and CHAIN138_SELECTOR.
Fund with LINK / gas — Complete the documented operator funding step for the Wemix deployer and bridge addresses.

Runbook: CONFIG_READY_CHAINS_COMPLETION_RUNBOOK.md
Env example: smom-dbis-138/docs/deployment/ENV_CONFIG_READY_CHAINS.example

1.2 Bridge Vault (Multi-Chain Stablecoin Bridge)

Status: ✅ Deployed
Vault: 0x31884f84555210FFB36a19D2471b8eBc7372d0A8
Tokens: cUSDT, cUSDC

Chain	Chain ID
Ethereum	1
Polygon	137
BNB Chain	56

1.3 Li.Fi / Settlement Layer

Chain	Chain ID	Li.Fi	CCIP	Routing
Ethereum Mainnet	1	✅	✅	Li.Fi Pay
Base	8453	✅	✅	Li.Fi Pay
Arbitrum One	42161	✅	✅	Li.Fi Pay
Polygon	137	✅	✅	Li.Fi Pay
Optimism	10	✅	✅	Li.Fi Pay
ChainID 138	138	❌	✅	Custom CCIP
ALL Mainnet	651940	❌	❌	AlltraAdapter

1.4 AlltraAdapter (Custom Bridge for ALL Mainnet)

Chain	Chain ID	Notes
ALL Mainnet	651940	Custom bridge; CCIP/Li.Fi not supported

USDC (AUSDC): 0xa95EeD79f84E6A0151eaEb9d441F9Ffd50e8e881

1.5 Truth Network

Item	Status	Notes
`TruthNetworkAdapter` on Chain 138	✅ Deployed	Adapter is registered in `ChainRegistry` on 138
Direct 138 ↔ Truth CCIP lane	❌ Not documented	Repo does not define Truth as a normal CCIP destination
Public Truth bridge story	✅ Ethereum ↔ Truth	Truth bridge narrative is Ethereum-centered (`TRUU` lift/burn)
138 role today	⚠️ Registry / pointer	Use 138 as metadata/registry attachment to the Ethereum Truth bridge story

Canonical reference: TRUTH_NETWORK_BRIDGE_SPEC.md

1.6 Tron

Item	Status	Notes
`TronAdapter` on Chain 138	✅ Deployed	`TRON_ADAPTER_CHAIN138` is recorded in the address inventory
Part of standard EVM CCIP matrix	❌ No	Treat as non-EVM relay program
End-to-end bridging	⚠️ Relay / ops dependent	Requires off-chain relay/oracle workflow and operational wiring

1.7 Etherlink and Tezos

Item	Status	Notes
Etherlink token mapping row (`42793`)	✅ Scaffolded	Placeholder `addressTo` values only
Tezos / Etherlink feature flags	✅ Present	`TEZOS_BRIDGE_ENABLED`, `ETHERLINK_BRIDGE_ENABLED`
Public production bridge lane	❌ Not live	Treat as planned / gated until runbook items are completed

Canonical reference: TEZOS_CCIP_REMAINING_ITEMS.md

1.8 XDC Zero

Item	Status	Notes
XDC ↔ 138 program	⚠️ Separate track	Parallel to CCIP and non-EVM adapter programs

Canonical reference: CHAIN138_XDC_ZERO_BRIDGE_RUNBOOK.md

1.9 OP Stack L2

Item	Status	Notes
L2 ↔ 138 bridge	⏳ Design only	Optional future design, not a live lane

Canonical reference: OP_STACK_L2_AND_BESU138_BRIDGE_NOTES.md

Part 2: Protocols That Have Accepted ChainID 138

2.1 Ledger App-Ethereum

Status: ✅ Accepted and integrated

Source: pr-workspace/app-ethereum (Ledger HQ App-Ethereum)
Configuration:
- src/network.c: {.chain_id = 138, .name = "Defi Oracle Meta", .ticker = "ETH"}
- makefile_conf/chain/defi_oracle.mk: Chain ID 138, AppName "Defi Oracle Meta", Ticker ETH
Derivation path: 44'/60' (standard EVM)
RPC: Not in firmware; wallets (Ledger Live, MetaMask) supply RPC URLs
Public RPCs: https://rpc-http-pub.d-bis.org, https://rpc.d-bis.org, https://rpc2.d-bis.org, https://rpc.defi-oracle.io

References: PUBLIC_RPC_CHAIN138_LEDGER.md, TASK9_LEDGER_RPC_VERIFICATION.md

2.2 Chainlist (ethereum-lists/chains)

Status: ✅ Accepted

Entry: pr-workspace/chains/_data/chains/eip155-138.json
Public URL: https://chainlist.org/chain/138
Chain name: Defi Oracle Meta Mainnet
RPCs: d-bis.org, defi-oracle.io, thirdweb
Explorer: https://explorer.d-bis.org (Blockscout)

Ledger Live and other clients can discover ChainID 138 RPCs via Chainlist.

2.3 thirdweb

Status: ✅ Accepted and supported

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

References: CCIP_BRIDGE_MAINNET_CONNECTION.md · CROSS_CHECK_SUMMARY_CCIP_9_CHAINS_AND_MAINNET.md · ADDRESS_MATRIX_AND_STATUS.md

2.4 MetaMask

Status: ✅ Supported via custom network / Chainlist

Add network manually or via Chainlist
RPCs: https://rpc-http-pub.d-bis.org, https://rpc.d-bis.org, etc.
SDK: defi-oracle-metamask-sdk with addOrSwitchNetwork()
Limitations: MetaMask Swaps and Bridge do not yet support ChainID 138

References: CHAIN138_WALLET_CONFIG_VALIDATION.md, METAMASK_NETWORK_CONFIG.json

2.5 Blockscout (Explorer)

Status: ✅ Deployed

URL: https://explorer.d-bis.org
Technology: Blockscout
Role: ChainID 138 block explorer

2.6 ethers.js

Status: ✅ Compatible

Chain 138 config validated for ethers v5/v6
HTTP and WebSocket providers work with public RPCs

Part 3: Protocols That Have Accepted ALL Mainnet (651940)

3.1 Chainlist (ethereum-lists/chains)