# DeFi Oracle Meta Mainnet - Connection Guide

**Date**: 2026-01-09  
**ChainID**: 138 (0x8a)  
**Network Name**: DeFi Oracle Meta Mainnet

---

## ✅ All RPC Endpoints Verified Working

### Internal Network Endpoints (192.168.11.0/24)

These endpoints work from within your internal network:

1. **RPC Translator** (ThirdWeb Compatible)
   - `http://192.168.11.240:9545`
   - Status: ✅ Working
   - Supports `eth_sendTransaction` with automatic signing

2. **Core RPC**
   - `http://192.168.11.250:8545`
   - Status: ✅ Working
   - Full API access (ADMIN, DEBUG, etc.)

3. **Permissioned RPC**
   - `http://192.168.11.251:8545`
   - Status: ✅ Working

4. **Public RPC**
   - `http://192.168.11.252:8545`
   - Status: ✅ Working

---

## 🌐 Public Endpoints (via Cloudflare Tunnel)

For connections from outside your network, use these public endpoints:

### Recommended for MetaMask/dApps

1. **Primary Public RPC**
   - `https://rpc-http-pub.d-bis.org`
   - Should NOT require authentication
   - Recommended for MetaMask

2. **Alternative Public RPCs**
   - `https://rpc.d-bis.org`
   - `https://rpc2.d-bis.org`

3. **Core RPC** (if you have JWT token)
   - `https://rpc-core.d-bis.org`
   - May require authentication

---

## 🔧 MetaMask Configuration

### Correct Network Settings

When adding DeFi Oracle Meta Mainnet to MetaMask, use these **exact** values:

```
Network Name: DeFi Oracle Meta Mainnet
RPC URL: https://rpc-http-pub.d-bis.org
Chain ID: 138
Currency Symbol: ETH
Block Explorer URL: https://explorer.d-bis.org
```

**Important Notes**:
- Chain ID must be `138` (decimal, NOT `0x8a` in hex)
- Use `https://rpc-http-pub.d-bis.org` for public access
- Do NOT use internal IPs (192.168.11.x) from outside the network

---

## 🔍 Troubleshooting Connection Issues

### Issue: "Unable to connect to Defi Oracle Meta Mainnet"

**Possible Causes**:

1. **Using Internal IP from External Network**
   - ❌ Wrong: `http://192.168.11.250:8545` (only works internally)
   - ✅ Correct: `https://rpc-http-pub.d-bis.org` (works from anywhere)

2. **Wrong Chain ID Format**
   - ❌ Wrong: `0x8a` (hex format)
   - ✅ Correct: `138` (decimal format for MetaMask)

3. **RPC URL Requires Authentication**
   - If you get "Unauthorized" or "JWT token" errors
   - Use `https://rpc-http-pub.d-bis.org` instead of `https://rpc-core.d-bis.org`

4. **Network/Firewall Issues**
   - Check if you can access the public endpoints
   - Test: `curl https://rpc-http-pub.d-bis.org`

5. **Cloudflare Tunnel Issues**
   - If public endpoints don't work, check Cloudflare tunnel status
   - VMID 102 should be running cloudflared service

---

## ✅ Verification Steps

### 1. Test Internal Endpoints
```bash
# From within your network
curl -X POST http://192.168.11.250:8545 \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Expected: {"jsonrpc":"2.0","result":"0x8a","id":1}
```

### 2. Test Public Endpoints
```bash
# From anywhere
curl -X POST 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","result":"0x8a","id":1}
```

### 3. Test RPC Translator
```bash
curl -X POST http://192.168.11.240:9545 \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Expected: {"jsonrpc":"2.0","result":"0x8a","id":1}
```

---

## 📋 Current Service Status

### All Services Operational ✅

- **VMID 2500** (Core RPC): ✅ Running, port 8545 listening
- **VMID 2501** (Permissioned RPC): ✅ Running, port 8545 listening
- **VMID 2502** (Public RPC): ✅ Running, port 8545 listening
- **VMID 2400** (RPC Translator): ✅ Running, all dependencies healthy
- **Network Connectivity**: ✅ All IPs pingable
- **Port Accessibility**: ✅ All ports accessible

---

## 🎯 Quick Fix Checklist

If you're still having connection issues:

- [ ] Are you using the correct RPC URL for your location?
  - Internal network: Use `http://192.168.11.250:8545` or `http://192.168.11.240:9545`
  - External network: Use `https://rpc-http-pub.d-bis.org`
- [ ] Is Chain ID set to `138` (decimal, not hex)?
- [ ] Are you using HTTPS for public endpoints?
- [ ] Have you tested the endpoint with curl?
- [ ] Is your firewall allowing outbound HTTPS connections?
- [ ] Are you behind a corporate proxy that might block connections?

---

## 📞 Next Steps

If issues persist:

1. **Check which endpoint you're trying to use**
2. **Verify you're using the correct URL for your network location**
3. **Test the endpoint directly with curl**
4. **Check MetaMask network settings match exactly**
5. **Verify Cloudflare tunnel is running** (for public endpoints)

---

## References

- MetaMask Troubleshooting: `docs/09-troubleshooting/METAMASK_TROUBLESHOOTING_GUIDE.md`
- Network Configuration: `docs/05-network/RPC_NODE_TYPES_ARCHITECTURE.md`
- RPC Translator Status: `reports/VMID2400_ALL_STEPS_COMPLETE.md`