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.
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.
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 and official GitHub for the most current addresses.
Ethereum Mainnet
Chain ID: 1
Block Explorer: etherscan.io
Base
Chain ID: 8453
Block Explorer: basescan.org
Arbitrum One
Chain ID: 42161
Block Explorer: arbiscan.io
Contract Verification
All deployed Synclear contracts are open-source and verified on their respective block explorers. To verify a contract:
- Navigate to the block explorer for the relevant network.
- Enter the contract address in the search bar.
- Select the Contract tab and confirm the Verified checkmark is present.
- 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 (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. 