Addresses & network
Covenant has not launched on mainnet. The code has not been externally audited. Anything currently deployed is a testbed — its parameters and its state are for testing and may differ from what this documentation describes.
Always confirm addresses from the dApp's deployments.json, which is generated from the
compiled contracts, rather than trusting an address pasted anywhere else.
Networks
Covenant launches on Ethereum mainnet. Rehearsals happen on Ethereum Sepolia — same contracts, same two scripts, same parameters file, a different RPC and a real cost.
| Network | Chain ID | Uniswap v4 PoolManager |
|---|---|---|
| Ethereum mainnet — the launch | 1 | 0x000000000004444c5dc75cB358380D2e3dE08A90 |
| Ethereum Sepolia — the rehearsal | 11155111 | 0xE03A1074c86CFeDd5C142C4F04F1a1536e203543 |
Nothing else is a target. Earlier material mentioning another chain predates the 2026-08-04 decision and no longer applies.
Contract addresses
Published at launch.
| Contract | Role |
|---|---|
CovenantToken | The CVN token — fixed supply, no mint |
CovenantHook | The Uniswap v4 hook: tax, retention, launch liquidity |
CovenantBonds | Bond positions, held as ERC-721 tokens |
CovenantBondVault | Cold storage for the reward reserve |
CovenantRouter | Trading entrypoints |
Once live, every address is verifiable on
etherscan.io for mainnet, and on
sepolia.etherscan.io for the rehearsal.
How addresses reach the app
Addresses and ABIs are exported into the dApp's deployments.json by the backend export
script. The app prefers the most relevant deployed chain and pins every transaction to the
correct chainId, so it can never sign against the wrong contracts.