Addresses

Canonical IporFusionFactoryProxy addresses per chain, verified against the ipor-abi registry.

Canonical per-chain deployment addresses for the IPOR Fusion vault factory. This table is the source you should resolve IporFusionFactoryProxy from before following Deploy your first Fusion vault — never hardcode an address from a test or an example without checking it here first.

Factory proxies per chain

clone() goes to the proxy column. The implementation column is listed only so you recognise and avoid it — calling it directly reverts DaoFeePackagesArrayEmpty(). Verify against ipor-abi (opens in new tab) before use; the registry is the source of truth and is regenerated on release.

ChainChain idIporFusionFactoryProxy (use)IporFusionFactoryImpl (reverts)Verified
Ethereum10xcd05909C4A1F8E501e4ED554cEF4Ed5E48D9b8520xf19C1E9f6616F6056AF1e322A86fDaAaAf0263f5implementation slot
Unichain1300xC9b4E839e86284C558791C13Bda97999fc49aF630xf5Bc40C192D51ED93ADD6557884766772FA72589implementation slot
TAC2390x26b5561E2E0e7d7977431E92740903Ef3cB7194b0x7DDd0bBB59eFB4b7791cE5E1Cf1587F083aE4Ef5implementation slot
Botanix36370x7c9857f22D0cc6523C8e88BFDCbf411AB8300fF50xddb0EFB2a7a5C02e01b5A1f85C0a1110d68EeC26registry only
Base84530x1455717668fA96534f675856347A973fA907e9220x610152A79BE7F2Aa3aA70520c9331c18fe8D33b7clone executed on a fork
Plasma97450x70d41759FBF90fB63c88197217cB08F93a1c65CB0x3A42bD6fEa94421025Ae2ed01CE6f137ac785abDimplementation slot
Arbitrum421610x134fCAce7a2C7Ef3dF2479B62f03ddabAEa922d50x87f94ac9aF79261F0BC73582114f805F55Cd0b25clone executed on a fork
Avalanche431140xa00b6379833D77fA9C9497b32dae00dF39Ac751e0x399596cFccFEbBb60f8652bece8586a6Bb4199abimplementation slot
Ink570730xEC53f69Bd1D991a2F99e96DE66E81D0E42A61D8D0xe7372BC46b79e0c87AfE5286c41c20687018E425implementation slot
Katana7474740xc29b8D591d6a3f109Ca7ba384F2e00162866D37B0x4a4De6e86AD0d0546F55B595cA75f55803D940bAregistry only

"Implementation slot" means the proxy's EIP-1967 implementation slot was read and matches the registry's IporFusionFactoryImpl; "registry only" means the pair was taken from ipor-abi without an on-chain read.

Fuse addresses

Fuse addresses are not in this table — they are market- and chain-specific (for example SupplyFuseAaveV3 and BalanceFuseAaveV3 on Base). Resolve them by registry name and chain in ipor-abi (opens in new tab), or with the hosted MCP server's fusion_address_lookup(name, chain_id=...). The SDK class for a registry name swaps the parts: SupplyFuseAaveV3 is AaveV3SupplyFuse.

Last updated