# Smart Contract Deployment Confirmation – Chain 138

**Date:** 2026-02-02  
**Network:** ChainID 138  
**RPC (admin):** http://192.168.11.211:8545  
**Blockscout:** http://192.168.11.140 | https://explorer.d-bis.org

---

## Deployment status (confirmed via RPC)

All contracts below have bytecode at their addresses (verified with `cast code`):

| Contract | Address | Bytecode | Status |
|----------|---------|----------|--------|
| **CCIP Sender** | `0x105F8A15b819948a89153505762444Ee9f324684` | ✓ | Deployed |
| **Oracle Proxy** (MetaMask) | `0x3304b747e565a97ec8ac220b0b6a1f6ffdb837e6` | ✓ | Deployed |
| **CCIPWETH10Bridge** | `0xe0E93247376aa097dB308B92e6Ba36bA015535D0` | ✓ | Deployed |
| **CCIPWETH9Bridge** | `0x971cD9D156f193df8051E48043C476e53ECd4693` | ✓ | Deployed |
| **MerchantSettlementRegistry** | `0x16D9A2cB94A0b92721D93db4A6Cd8023D3338800` | ✓ | Deployed |
| **WithdrawalEscrow** | `0xe77cb26eA300e2f5304b461b0EC94c8AD6A7E46D` | ✓ | Deployed |

---

## Blockscout verification status

**Automated verification (forge):** Failing

- Error: `Params 'module' and 'action' are required parameters`
- Forge’s Blockscout verifier uses a format that does not match this Blockscout instance’s API.

**Manual verification:** Use the Blockscout UI:

1. Open https://explorer.d-bis.org (or http://192.168.11.140)
2. Go to each contract address
3. Use **Contract → Verify & Publish**

---

## Canonical addresses (Chain 138)

```
CCIP_SENDER=0x105F8A15b819948a89153505762444Ee9f324684
ORACLE_PROXY=0x3304b747e565a97ec8ac220b0b6a1f6ffdb837e6
CCIPWETH9_BRIDGE=0x971cD9D156f193df8051E48043C476e53ECd4693
CCIPWETH10_BRIDGE=0xe0E93247376aa097dB308B92e6Ba36bA015535D0
MERCHANT_SETTLEMENT_REGISTRY=0x16D9A2cB94A0b92721D93db4A6Cd8023D3338800
WITHDRAWAL_ESCROW=0xe77cb26eA300e2f5304b461b0EC94c8AD6A7E46D
```

---

## References

- [CONTRACT_ADDRESSES_REFERENCE.md](../docs/11-references/CONTRACT_ADDRESSES_REFERENCE.md)
- [scripts/verify-contracts-blockscout.sh](../scripts/verify-contracts-blockscout.sh)