Deployment Addresses

Gearbox v3.1 contracts are deployed through a deterministic deployer, so every system contract has the same address on all supported chains. This page is the canonical address list for the protocol.

Programmatic Discovery

The recommended way to resolve contract addresses at runtime is through the AddressProvider contract. Rather than hardcoding addresses, query the AddressProvider to get the latest verified deployment for any protocol component:

import { GearboxSDK } from '@gearbox-protocol/sdk';

const sdk = await GearboxSDK.attach({ client, marketConfigurators: [] });

// Resolve any protocol contract by its key
const [address, version] = sdk.addressProvider.mustGetLatest(
  AP_MARKET_COMPRESSOR,
  VERSION_RANGE_310
);

See the SDK setup guide for full initialization details.

System Contracts

Factories

Used by market configurators to deploy and upgrade market components.

Periphery Contracts

Read-only compressors and the router, registered in the AddressProvider under GLOBAL::* keys.

Activated Chains

Chains activated through cross-chain governance, with the per-chain treasury, wrapped native token, and GEAR token addresses. This table is generated from the InstanceManager.activate calls executed by the Cross-Chain Governance multisig on Ethereum (npm run generate:addresses).

Notes

• Always prefer the AddressProvider for programmatic address resolution. Hardcoded addresses may become stale after protocol upgrades.
• Market-specific contracts (Pools, Credit Managers, Credit Facades) are discoverable through the Market Compressor once you have the AddressProvider.
• For a complete list of address keys, see the AP_* constants exported by the SDK.