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 before use; the registry is the source of truth and is regenerated on release.

Chain	Chain id	IporFusionFactoryProxy (use)	IporFusionFactoryImpl (reverts)	Verified
Ethereum	1	0xcd05909C4A1F8E501e4ED554cEF4Ed5E48D9b852	0xf19C1E9f6616F6056AF1e322A86fDaAaAf0263f5	implementation slot
Unichain	130	0xC9b4E839e86284C558791C13Bda97999fc49aF63	0xf5Bc40C192D51ED93ADD6557884766772FA72589	implementation slot
TAC	239	0x26b5561E2E0e7d7977431E92740903Ef3cB7194b	0x7DDd0bBB59eFB4b7791cE5E1Cf1587F083aE4Ef5	implementation slot
Botanix	3637	0x7c9857f22D0cc6523C8e88BFDCbf411AB8300fF5	0xddb0EFB2a7a5C02e01b5A1f85C0a1110d68EeC26	registry only
Base	8453	0x1455717668fA96534f675856347A973fA907e922	0x610152A79BE7F2Aa3aA70520c9331c18fe8D33b7	clone executed on a fork
Plasma	9745	0x70d41759FBF90fB63c88197217cB08F93a1c65CB	0x3A42bD6fEa94421025Ae2ed01CE6f137ac785abD	implementation slot
Arbitrum	42161	0x134fCAce7a2C7Ef3dF2479B62f03ddabAEa922d5	0x87f94ac9aF79261F0BC73582114f805F55Cd0b25	clone executed on a fork
Avalanche	43114	0xa00b6379833D77fA9C9497b32dae00dF39Ac751e	0x399596cFccFEbBb60f8652bece8586a6Bb4199ab	implementation slot
Ink	57073	0xEC53f69Bd1D991a2F99e96DE66E81D0E42A61D8D	0xe7372BC46b79e0c87AfE5286c41c20687018E425	implementation slot
Katana	747474	0xc29b8D591d6a3f109Ca7ba384F2e00162866D37B	0x4a4De6e86AD0d0546F55B595cA75f55803D940bA	registry 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, 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.