# Chains & Protocols: Bridges, Ledger, and Integrations

**Last Updated:** 2026-01-29  
**Status:** Authoritative reference for bridge chains and protocol acceptance

---

## Overview

This document consolidates:
1. **Chains handled by bridges** – CCIP, Bridge Vault, Li.Fi, AlltraAdapter
2. **Protocols and wallets that have accepted ChainID 138** – Ledger, Chainlist, thirdweb, MetaMask, etc.
3. **Protocols and wallets that have accepted ALL Mainnet (651940)** – Chainlist, MetaMask, etc.

---

## Part 1: Chains Handled by Bridges

### 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 | ✅ Config ready |
| Celo | 42220 | ✅ Config ready |
| Wemix | 1111 | ✅ Config ready |
| ChainID 138 (DeFi Oracle Meta Mainnet) | 138 | ✅ |

**Deployed CCIP WETH bridges:** CCIPWETH9Bridge and CCIPWETH10Bridge on BSC, Polygon, Avalanche, Base, Arbitrum, Optimism, ChainID 138.

**Additional CCIP-ready chains (selectors configured):** Gnosis Chain (`465200170687744372`), Celo (`1346049177634351622`), Wemix (`5142893604156789321`).

#### Completion checklist for Config-Ready chains (Gnosis, Celo, Wemix)

To move Gnosis (100), Celo (42220), and Wemix (1111) from **Config ready** to **✅**:

1. **Verify CCIP support** — Confirm each chain is listed in [Chainlink CCIP supported networks](https://docs.chain.link/ccip/supported-networks).
2. **Deploy bridges** — Deploy CCIPWETH9Bridge and CCIPWETH10Bridge on each chain (see runbook).
3. **Configure destinations** — Run `smom-dbis-138/scripts/deployment/complete-config-ready-chains.sh` (requires bridge addresses and `CHAIN138_SELECTOR` in `.env`).
4. **Fund with LINK** — Send ~10 LINK per bridge on each chain for CCIP fees.

**Runbook:** [CONFIG_READY_CHAINS_COMPLETION_RUNBOOK.md](../07-ccip/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`

---

## 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](../04-configuration/PUBLIC_RPC_CHAIN138_LEDGER.md), [TASK9_LEDGER_RPC_VERIFICATION.md](../../smom-dbis-138/docs/deployment/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](../07-ccip/CCIP_BRIDGE_MAINNET_CONNECTION.md) · [CROSS_CHECK_SUMMARY_CCIP_9_CHAINS_AND_MAINNET.md](CROSS_CHECK_SUMMARY_CCIP_9_CHAINS_AND_MAINNET.md) · [ADDRESS_MATRIX_AND_STATUS.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](../04-configuration/CHAIN138_WALLET_CONFIG_VALIDATION.md), [METAMASK_NETWORK_CONFIG.json](../04-configuration/metamask/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)

**Status:** ✅ **Accepted**

- **Entry:** `pr-workspace/chains/_data/chains/eip155-651940.json`
- **Public URL:** https://chainlist.org/chain/651940
- **Chain name:** ALL Mainnet
- **RPC:** https://mainnet-rpc.alltra.global
- **Explorer:** https://alltra.global

---

### 3.2 MetaMask

**Status:** ✅ **Supported via custom network / Chainlist**

- Add ALL Mainnet via Chainlist or manual entry
- RPC: `https://mainnet-rpc.alltra.global`

---

### 3.3 thirdweb

**Status:** ⚠️ **Check chainlist**

- ALL Mainnet may be discoverable via thirdweb chainlist if submitted/merged to upstream chains repo.

---

### 3.4 Protocols NOT Yet Supporting ALL Mainnet

| Protocol | Status |
|----------|--------|
| **Chainlink CCIP** | ❌ Not in CCIP Directory |
| **Li.Fi** | ❌ Not in Li.Fi API |
| **Ledger App-Ethereum** | ⚠️ Not in firmware; use custom network in Ledger Live |

---

## Summary Table: Protocol Acceptance

| Protocol | ChainID 138 | ALL Mainnet (651940) |
|----------|-------------|----------------------|
| **Ledger App-Ethereum** | ✅ In firmware | ⚠️ Custom network only |
| **Chainlist** | ✅ eip155-138 | ✅ eip155-651940 |
| **thirdweb** | ✅ Chain + Bridge | ⚠️ Verify |
| **MetaMask** | ✅ Custom/Chainlist | ✅ Custom/Chainlist |
| **Blockscout** | ✅ explorer.d-bis.org | — |
| **CCIP** | ✅ Custom implementation | ❌ |
| **Li.Fi** | ❌ | ❌ |
| **Bridge Vault** | — | — |

---

## References

- [CHAIN_SUPPORT.md](../../alltra-lifi-settlement/docs/CHAIN_SUPPORT.md) – Chain support matrix
- [BRIDGE_CONFIGURATION.md](../../smom-dbis-138/docs/deployment/BRIDGE_CONFIGURATION.md) – CCIP bridge config
- [PUBLIC_RPC_CHAIN138_LEDGER.md](../04-configuration/PUBLIC_RPC_CHAIN138_LEDGER.md) – Ledger RPCs
- [CHAIN138_WALLET_CONFIG_VALIDATION.md](../04-configuration/CHAIN138_WALLET_CONFIG_VALIDATION.md) – Wallet configs
- [ALL_MAINNET_CONFIGURATION.md](../../smom-dbis-138/docs/deployment/ALL_MAINNET_CONFIGURATION.md) – ALL Mainnet config