> For the complete documentation index, see [llms.txt](https://docs.kpk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpk.io/funds/infrastructure/architecture/deployment/deployment-addresses.md).

# Deployment addresses

Deployment addresses for the fund factory infrastructure: the canonical CREATE2 layer (factory, orchestrator, shares mastercopy, timelock deployer) shared across every chain.

The **fund factory infrastructure**, the contracts that deploy funds (see [Fund deployment](https://docs.kpk.io/funds/infrastructure/architecture/deployment.md) and [Cross-chain deployment](https://docs.kpk.io/funds/infrastructure/architecture/deployment/cross-chain-deployment.md)), is deployed at the **same address on every supported chain**. Every contract except `Empty` is placed by the canonical CREATE2 deployer (`0x4e59b44847b379578588920cA78FbF26c0B4956C`) with identical bytecode and constructor arguments, so their addresses are deterministic and chain-independent.

{% hint style="success" %}
**The factory:** `KpkOivFactory` at [`0x73Bb12a05669748f3c9cbE8764271c69182f49E5`](https://etherscan.io/address/0x73Bb12a05669748f3c9cbE8764271c69182f49E5), the same address on every chain. New Funds are deployed by calling it (directly, or via the CCIP orchestrator).
{% endhint %}

The machine source of truth is the contracts repo: [`script/deployed-infra.json`](https://github.com/karpatkey/onchain-investment-vehicles/blob/main/script/deployed-infra.json) (per-chain deploy block, tx hash, and verification), mirrored by [`docs/DEPLOYED_ADDRESSES.md`](https://github.com/karpatkey/onchain-investment-vehicles/blob/main/docs/DEPLOYED_ADDRESSES.md).

## Canonical layer: salt v4 (current)

Each generation of the infrastructure is deployed under a new CREATE2 salt; **salt v4** is the current one and the **only** deploy target for new funds. Every contract below shares one address on every chain.

| Contract                                   | Address                                                                                                                 | Role                                                                                                                                                                                                                                                                |
| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `KpkOivFactory`                            | [`0x73Bb12a05669748f3c9cbE8764271c69182f49E5`](https://etherscan.io/address/0x73Bb12a05669748f3c9cbE8764271c69182f49E5) | Deploys a fund's Safe + Roles + shares stack, and its timelocks, in one transaction ([Fund deployment](https://docs.kpk.io/funds/infrastructure/architecture/deployment.md)).                                                                                       |
| `CcipOivDeployer`                          | [`0xD99e4B13fc50A6321f6A84f2D4F83d6e34AE699D`](https://etherscan.io/address/0xD99e4B13fc50A6321f6A84f2D4F83d6e34AE699D) | Cross-chain orchestrator: one transaction on any wired chain fans a fund's operational stack out over CCIP to the other chains it can reach ([Cross-chain deployment](https://docs.kpk.io/funds/infrastructure/architecture/deployment/cross-chain-deployment.md)). |
| `KpkShares` mastercopy                     | [`0x729Fb58a61a6f8349657fBc9f17BA4D36C9e72fC`](https://etherscan.io/address/0x729Fb58a61a6f8349657fBc9f17BA4D36C9e72fC) | The single shared `kpkShares` implementation. Every fund's ERC-1967 shares proxy on the chain points at it; each proxy still controls its own upgrades.                                                                                                             |
| `KpkTimelockDeployer`                      | [`0xdd23Ba8B2c4D3D916605361e29600121DeFC2d9f`](https://etherscan.io/address/0xdd23Ba8B2c4D3D916605361e29600121DeFC2d9f) | Deploys a fund's governance timelocks (called by the factory).                                                                                                                                                                                                      |
| `TimelockControllerUpgradeable` mastercopy | [`0x9760280fED9e760668186334f88b6d763A7d976E`](https://etherscan.io/address/0x9760280fED9e760668186334f88b6d763A7d976E) | The implementation each fund timelock clones.                                                                                                                                                                                                                       |
| `Empty`                                    | [`0xA4703438f8cc4fc2C2503a7e43935Da16BA74652`](https://etherscan.io/address/0xA4703438f8cc4fc2C2503a7e43935Da16BA74652) | The Portfolio Safe's sole signer: a contract with no logic, so the Safe can only act through its Roles Modifiers. Unchanged across every salt.                                                                                                                      |

`KpkSharesDeployer` no longer exists in salt v4: funds no longer get a per-fund `kpkShares` implementation.

## Ownership

| Party                              | Address                                                                                                                 | After deploy                                                                                                  |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Security Council Safe** (5-of-8) | [`0x8b884f80B3B839F52b6cE168f133e7a5D1f0A537`](https://etherscan.io/address/0x8b884f80B3B839F52b6cE168f133e7a5D1f0A537) | `Ownable.owner` of the factory and the orchestrator on every chain (same address everywhere).                 |
| Deployer EOA                       | [`0xAa5A7C7Ea51F276301f881F9CCB501a1dFeF4F72`](https://etherscan.io/address/0xAa5A7C7Ea51F276301f881F9CCB501a1dFeF4F72) | Deployed the infrastructure, then transferred ownership to the Safe. Holds **no** privileged role afterwards. |

What ownership controls:

* **Factory**: **only** the curated fund registry (`registerFund` / `unregisterFund`). Every infrastructure address (Safe and Zodiac contracts, the `kpkShares` mastercopy, the timelock deployer) is a **constructor argument with no setter**, so no owner, compromised or not, can redirect a future deployment. Deployment itself is permissionless.
* **Orchestrator**: the per-chain CCIP wiring: the router (`configure`), edits to the chain-selector registry (`setChainSelector(s)` / `removeChainSelector`), and sweeps of any stray LINK or native balance. The registry is **seeded at construction** with 19 of the 20 chains below, so those need no post-deploy seeding step. Robinhood Chain is not seeded, so it cannot use CCIP unless its selector is added with `setChainSelector` (see [Cross-chain deployment](https://docs.kpk.io/funds/infrastructure/architecture/deployment/cross-chain-deployment.md#supported-destinations)). The owner never holds a role on any fund. Because it can repoint the router, the owner is also trusted for the integrity of CCIP deliveries.

{% hint style="warning" %}
The owner should remain a governance multisig, never an EOA. It can no longer backdoor future funds through the factory, but it still curates the registry and controls the orchestrator's CCIP wiring. See the trust assumptions on [Fund deployment](https://docs.kpk.io/funds/infrastructure/architecture/deployment.md).
{% endhint %}

## Chains

The salt v4 infrastructure is deployed on **20 chains**. On each, the factory and orchestrator are owned by the Security Council Safe: Ethereum (1), Optimism (10), Gnosis (100), Base (8453), Arbitrum (42161), BSC (56), Polygon (137), Avalanche (43114), Celo (42220), Linea (59144), Scroll (534352), Sonic (146), Unichain (130), World Chain (480), HyperEVM (999), Mantle (5000), Plasma (9745), Ink (57073), Berachain (80094), Robinhood Chain (4663).

Bob and Katana are **excluded**: no infrastructure is deployed there, and the orchestrator's registry does not include them. Robinhood Chain is deployed but not in the orchestrator's registry, so Funds there deploy locally; see [Cross-chain deployment](https://docs.kpk.io/funds/infrastructure/architecture/deployment/cross-chain-deployment.md#supported-destinations).

### Source verification

Each chain carries five salt v4 contracts: the factory, the orchestrator, the `kpkShares` mastercopy, the timelock deployer, and the timelock mastercopy. `Empty` predates salt v4 and is not counted. Counts are as of 30 September 2026 (6 October 2026 for Robinhood Chain).

| Backend      | Coverage                                                                                            | Verified              |
| ------------ | --------------------------------------------------------------------------------------------------- | --------------------- |
| Sourcify     | All 20 chains                                                                                       | 100/100 (exact match) |
| Etherscan V2 | 18 chains: every chain except Scroll and Ink                                                        | 90/90                 |
| Blockscout   | Ethereum, Base, Arbitrum, Polygon, Celo, Unichain, Ink, World Chain, Robinhood Chain                | 45/45                 |
| OKLink       | Ethereum, Optimism, Gnosis, Base, Arbitrum, BSC, Polygon, Avalanche, Linea, Scroll, Robinhood Chain | 55/55                 |
| Routescan    | Ethereum, Avalanche, Mantle, Plasma                                                                 | 20/20                 |
| Tenderly     | 19 chains: every chain except HyperEVM, which Tenderly does not support                             | 95/95                 |

{% hint style="info" %}
These are the shared **factory** addresses. A fund's own contracts (Portfolio Safe, Manager Safe, Roles Modifiers, timelocks, `kpkShares` proxy) are per-fund and listed on each Fund's page, for example [USD Alpha](https://docs.kpk.io/funds/funds/usd-alpha.md).
{% endhint %}

## Earlier generations (existing funds only)

Funds deployed before salt v4 keep running on the factory generation they were born on. A fund's Portfolio Safe address depends on the factory's address, so **a fund can never straddle two generations**: the same `(caller, salt)` produces different addresses under each. These factories are documented so existing funds can be operated and audited. **Never deploy a new fund through them.**

| Fund                                                             | Shares contract                                                                                                         | Factory generation |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ------------------ |
| [USD Alpha](https://docs.kpk.io/funds/funds/usd-alpha.md) (kUSD) | [`0x6D1a4C0878aD24793b1655ae1f78Cfa4522Ba765`](https://etherscan.io/address/0x6D1a4C0878aD24793b1655ae1f78Cfa4522Ba765) | Legacy             |
| XAUt Carry                                                       | [`0xDa35793Dc733fEFfb294938F95ff3B593170f9F8`](https://etherscan.io/address/0xDa35793Dc733fEFfb294938F95ff3B593170f9F8) | Salt v3            |
| WBTC Carry                                                       | [`0xf180800f239f0ea0ED2F8156581fac2984cEe389`](https://etherscan.io/address/0xf180800f239f0ea0ED2F8156581fac2984cEe389) | Salt v3            |

[ETH Alpha](https://docs.kpk.io/funds/funds/eth-alpha.md) (kETH, [`0xED01a1Fe4e020Ca901F43E17B6203A7e0cEa818C`](https://etherscan.io/address/0xED01a1Fe4e020Ca901F43E17B6203A7e0cEa818C)) was deployed outside the factory, with pre-factory scripts.

### Salt v3

Deployed 24 July 2026 on 19 chains, owned by the Security Council Safe. The factory **owner** of this generation controls the infrastructure setters (Safe and Zodiac contracts, and the shares deployer) with no timelock, and the salt v3 orchestrator's owner (also the Security Council Safe) controls its CCIP configuration. Fan-out originates **from Ethereum mainnet only**.

| Contract            | Address                                                                                                                 |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| `KpkOivFactory`     | [`0xbafbca1804B6e46D4c54Cac0A0273F5B2A8F677F`](https://etherscan.io/address/0xbafbca1804B6e46D4c54Cac0A0273F5B2A8F677F) |
| `KpkSharesDeployer` | [`0xea084E763F8535CBe28759b990F963BeDf60be9a`](https://etherscan.io/address/0xea084E763F8535CBe28759b990F963BeDf60be9a) |
| `CcipOivDeployer`   | [`0x6F2A3D35Ff275d6B76dB47eFB0Da1b2358daf11b`](https://etherscan.io/address/0x6F2A3D35Ff275d6B76dB47eFB0Da1b2358daf11b) |

### Legacy factory (pre-v2.1.1)

The first factory build (pre-v2.1.1 Roles Modifier), deployed on Ethereum, Optimism, Gnosis, Base and Arbitrum. USD Alpha (kUSD) runs on it.

| Contract            | Address                                                                                                                 |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| `KpkOivFactory`     | [`0x0d94255fdE65D302616b02A2F070CdB21190d420`](https://etherscan.io/address/0x0d94255fdE65D302616b02A2F070CdB21190d420) |
| `KpkSharesDeployer` | [`0xA4B485Efe30F2b1D277b7A2279310239B26775F0`](https://etherscan.io/address/0xA4B485Efe30F2b1D277b7A2279310239B26775F0) |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kpk.io/funds/infrastructure/architecture/deployment/deployment-addresses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
