Developers

Contract addresses and deployments

Developer-facing snapshot of current deployed addresses and where that snapshot is maintained.

Canonical snapshot

The primary developer snapshot lives in:

frontend-app/web3-app/src/config/index.ts — CONFIG.CONTRACTS
frontend-app/web3-app/subgraph/config/deployments/sepolia.json — the deployment config the subgraph regenerates from

The subgraph's src/config.ts is auto-generated from sepolia.json by scripts/sync-config.mjs. All three files agree exactly.

Current contracts

Contract	Address
`REGISTRY`	`0x88a9692069fF43A439Ff876E28A8df5769175254`
`EVE_TOKEN`	`0xFcf9F72C41E1BfA481d145933486DeF934a6C006`
`EXIT_QUEUE`	`0x56d60283b42B8125389eAEc9a3c9AFE04Aa9e8f6`
`CONTROLLER`	`0xB4a9F1df239A408998358dE3Ba8e11F0f267da7A`
`ORACLE`	`0xce2b65C769479f2CbbFcFf7213EC0917A5b26Dd3`
`STRATEGY_MANAGER`	`0xd4Bb0bEF88b6be67CD3285f8A56fa74839f36728`
`AMM`	`0xad8afa3c697D7D3B87E73e30BD9ADd42098593f6`
`CONVERTER`	`0xacB3567e20418D3B668233cF2eDB31D0801C163F`
`TIMELOCK`	`0x5E19AcCDDedAf0A185C5627f41b1AB98179CC064`

Read more in Current deployments and Contract addresses.

Last updated on

Roles, permissions, and admin powers

Governance-oriented view of who can upgrade, pause, configure, or process core flows.

Events, entities, and integrations

The minimum event and entity set required to integrate with frontend or analytics consumers.

On this page

Canonical snapshot Current contracts