> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synclear.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Verified Smart Contract Addresses Across Synclear Networks

> Official Synclear contract addresses on Ethereum Mainnet, Base, and Arbitrum — with on-chain verification guidance and security warnings.

This page lists the canonical smart contract addresses for all core Synclear protocol contracts. Addresses are provided per network and should be used as the authoritative reference when verifying contracts before interaction. All contracts are verified on their respective block explorers and are linked for direct inspection.

<Warning>
  **Always verify contract addresses independently before interacting with any Synclear contract.** Cross-reference addresses listed here against the official Synclear GitHub repository and the relevant block explorer verification records. Phishing sites and unofficial deployments may present counterfeit contracts. Synclear will never ask you to interact with a contract address communicated via social media, Discord DM, or unofficial channels. If in doubt, do not proceed.
</Warning>

The addresses below marked `0x000...EXAMPLE` are placeholder values for documentation purposes. When the protocol launches on each network, live addresses will replace these placeholders. Check the [Synclear app](https://app.synclear.io) and official GitHub for the most current addresses.

***

## Ethereum Mainnet

**Chain ID:** `1`\
**Block Explorer:** [etherscan.io](https://etherscan.io)

| Contract            | Address                                                  | Description                                                                                   |
| ------------------- | -------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| `CreditPoolFactory` | `0x0000000000000000000000000000000000000001` *(example)* | Deploys and registers new credit pool instances.                                              |
| `VaultFactory`      | `0x0000000000000000000000000000000000000002` *(example)* | Deploys savings vault and yield strategy contracts.                                           |
| `BorrowRouter`      | `0x0000000000000000000000000000000000000003` *(example)* | Entry point for all borrower drawdown and repayment operations.                               |
| `MandateRegistry`   | `0x0000000000000000000000000000000000000004` *(example)* | Stores and manages on-chain mandate configurations for AI agents and institutional operators. |
| `TrustScorer`       | `0x0000000000000000000000000000000000000005` *(example)* | Computes and stores on-chain credit trust scores for borrower entities.                       |

***

## Base

**Chain ID:** `8453`\
**Block Explorer:** [basescan.org](https://basescan.org)

| Contract            | Address                                                  | Description                                              |
| ------------------- | -------------------------------------------------------- | -------------------------------------------------------- |
| `CreditPoolFactory` | `0x0000000000000000000000000000000000000011` *(example)* | Deploys and registers new credit pool instances on Base. |
| `VaultFactory`      | `0x0000000000000000000000000000000000000012` *(example)* | Deploys savings vault contracts on Base.                 |
| `BorrowRouter`      | `0x0000000000000000000000000000000000000013` *(example)* | Borrower drawdown and repayment entry point on Base.     |
| `MandateRegistry`   | `0x0000000000000000000000000000000000000014` *(example)* | Mandate configuration registry on Base.                  |
| `TrustScorer`       | `0x0000000000000000000000000000000000000015` *(example)* | Trust score oracle on Base; synced from Mainnet state.   |

***

## Arbitrum One

**Chain ID:** `42161`\
**Block Explorer:** [arbiscan.io](https://arbiscan.io)

| Contract            | Address                                                  | Description                                                  |
| ------------------- | -------------------------------------------------------- | ------------------------------------------------------------ |
| `CreditPoolFactory` | `0x0000000000000000000000000000000000000021` *(example)* | Deploys and registers new credit pool instances on Arbitrum. |
| `VaultFactory`      | `0x0000000000000000000000000000000000000022` *(example)* | Deploys savings vault contracts on Arbitrum.                 |
| `BorrowRouter`      | `0x0000000000000000000000000000000000000023` *(example)* | Borrower drawdown and repayment entry point on Arbitrum.     |
| `MandateRegistry`   | `0x0000000000000000000000000000000000000024` *(example)* | Mandate configuration registry on Arbitrum.                  |
| `TrustScorer`       | `0x0000000000000000000000000000000000000025` *(example)* | Trust score oracle on Arbitrum; synced from Mainnet state.   |

***

## Contract Verification

All deployed Synclear contracts are open-source and verified on their respective block explorers. To verify a contract:

1. Navigate to the block explorer for the relevant network.
2. Enter the contract address in the search bar.
3. Select the **Contract** tab and confirm the **Verified** checkmark is present.
4. Review the contract source code and ABI to confirm it matches the Synclear GitHub repository at the corresponding release tag.

Synclear's contract source code is published at [github.com/synclear](https://github.com/synclear) (canonical repository link; verify the organization name independently). All contract deployments include a matching deployment artifact in the repository with the deployer address, deployment transaction hash, and constructor arguments.

## Proxy and Upgrade Architecture

Synclear's core contracts use a minimal proxy pattern for factory-deployed pool and vault instances. The implementation contracts (logic contracts) are separately deployed and verified. Upgradeability, where present, is governed by on-chain governance with a mandatory time-lock delay. Non-upgradeable contracts are noted as such in the repository documentation.