> 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/core-concepts/bridging.md). # Bridging How cross-chain transfers of fund assets affect NAV. Bridging refers to the movement of a fund's assets between its Safes on different chains, letting operators rebalance liquidity or deploy capital across networks. Because a fund's **Portfolio Safe has the same address on every chain** (a deterministic property of the [factory](/funds/infrastructure/architecture/deployment.md)), bridged assets stay within the fund's own custody on both sides. While a bridge transaction is in progress, the assets are **in transit**; they have left the source chain but have not yet arrived on the destination chain, so during that window they are not reflected in either chain's balances. The global NAV (the sum of per-chain NAVs) therefore temporarily **under-counts** by the in-flight amount until the transfer settles. {% hint style="warning" %} A global NAV taken while a bridge is mid-flight is incomplete and is **not** a true representation of the fund's value; it must not be used to settle subscriptions or redemptions until the transfer completes on the destination chain. See [Calculate share price](/funds/kpk-fund-integration/calculate-share-price.md). {% endhint %} --- # 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/core-concepts/bridging.md?ask=&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.