Deployment Addresses

Gearbox Protocol contracts are deployed across multiple networks. This page lists the core contract addresses for each supported chain.

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.

Ethereum Mainnet

Placeholder addresses shown above. Refer to the AddressProvider or the Gearbox GitHub for canonical deployments.

Arbitrum

Placeholder addresses shown above. Refer to the AddressProvider or the Gearbox GitHub for canonical deployments.

Optimism

Placeholder addresses shown above. Refer to the AddressProvider or the Gearbox GitHub for canonical deployments.

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 MarketCompressor once you have the AddressProvider.
• For a complete list of address keys, see the AP_* constants exported by the SDK.