Deployments
A network profile, sandbox configuration and deployment manifest serve different purposes. None should be relabelled as a live production deployment. Ethereum and Base mainnet deposits and mainnet margin use are not approved.
Network profiles
| Profile | Assets | Status |
|---|---|---|
| Ethereum, chain 1 | USDC, USDT, WETH, WBTC, wstETH | Native Aave/Uniswap qualification profile; pinned fork testing, not a live SEAL deployment |
| Base, chain 8453 | Native USDC, WETH, wstETH | Native qualification profile with a narrower reserve and route set |
| Sepolia, chain 11155111 | Nine test assets in config/sepolia |
Fresh checkpoint deployment pending; test tokens and custom lending/DEX venues |
| Local fork | Selected source-chain assets | Local Anvil execution; not a public-chain broadcast |
Use Getting Started for the consumer support matrix. Exact profile addresses are maintained in the repository's chain-specific profile files and must be checked against their source block and reserve qualification.
Deployment identities
Use the verified deployment record for the pool, per-asset vaults, fixed verifier registry, raw verifiers, deposit/swap adapters and authority Safes. Match chain ID, deployment ID, source/compiler settings, bytecode/runtime hashes, proof manifest and recorded blocks.
Sandbox pool addresses are zero placeholders and cannot receive deposits. A Sepolia release must install a complete verified deployment record with all four verifier routes and matching checkpoint-aware adapters. The checked-in service/browser configuration must not be activated against a deployment that fails these checks. The network selector keeps Sepolia test funds separate from Sandbox demo funds.
The deployment and artifact runbook explains address verification and production gates. Sepolia operations explains the selected deployment and active swap routes.
Margin deployments
Margin requires a separately verified manifest for SealMarginAdapter, SealPublicMarginAdapter, SealMarginAccount implementation and MarginFees, plus its Aave/Uniswap bindings. A core pool deployment does not automatically support margin.
Production builds require a verified chain-specific margin manifest when margin is configured. Local rehearsals use development proofs and explicit local manifests; they do not authorize mainnet use or establish a public deployment. No live mainnet margin deployment is advertised here. See Margin Architecture.