# Deployed Contracts



<Callout type="info">
  All deployed contracts are verified on their respective block explorer. MetaVault contracts use a proxy pattern — the addresses below are the proxy addresses that users and integrators should interact with.
</Callout>

**Ethereum**

| Contract           | Address                                    |
| ------------------ | ------------------------------------------ |
| MetavaultsRegistry | 0x16b28223b607b4d90e2ec628fdc1a0ad9ee1f6b8 |

**Base**

| Contract           | Address                                    |
| ------------------ | ------------------------------------------ |
| MetavaultsRegistry | 0xa2c9da26c1982cacaf01c5c691e0cf0aeb031ac1 |

**Arbitrum**

| Contract           | Address                                    |
| ------------------ | ------------------------------------------ |
| MetavaultsRegistry | 0xa355dd06f35bcfe98e45f743397b729b93c560be |

**Avalanche**

| Contract           | Address                                    |
| ------------------ | ------------------------------------------ |
| MetavaultsRegistry | 0xacf33983cab5f9e914e6a93a2f4d531b5c516602 |

**Katana**

| Contract           | Address                                    |
| ------------------ | ------------------------------------------ |
| MetavaultsRegistry | 0x191ea03cccc27546ba9f5161b4948b6afce5263f |

<Callout type="info">
  Individual MetaVaultWrapper instances are deployed per vault and are not listed here as they are vault-specific. Check the [MetavaultsRegistry](/docs/metavaults/contract-functions/metavaults-registry) on each chain to query registered MetaVaults.
</Callout>