> For the complete documentation index, see [llms.txt](https://docs.openetf.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openetf.xyz/developers/integrations.md).

# Building with OpenETF

**Every ETF comes from one Factory, so an integration works the same way across all of them. Each ETF issues one ERC-20-compatible share token, and wallets, funds and applications can hold its shares and build on them.**

## Composition runs in two directions

**Inward**, a strategy combines Supported Markets: HyperCore spot, perpetuals and HIP-3 markets. A new asset type joins only once its valuation, cash movements and exits connect to fund accounting, and only in ETFs whose disclosed scope includes it: while outside investors hold shares, an existing ETF does not gain it ([Who controls what](https://docs.openetf.xyz/how-it-works/control.md#changing-a-funds-risk-scope)).

**Outward**, the share token carries the whole managed portfolio. Wallets can show it, other funds can hold it, and applications can build on it. Longer-term directions are on the [Roadmap](https://docs.openetf.xyz/roadmap.md).

## One issuance path serves every ETF

Every ETF comes from the Standard Vault Factory, and the OpenETF interface uses the same path. A valid Factory output is native whoever calls it.

Any ETF that OpenETF itself offers to outside investors runs under an active [Mandate](https://docs.openetf.xyz/how-it-works/risk-controls/mandate.md).

## The OpenETF API is a Manager's programmatic client

A Manager's own strategies, bots or third-party terminals submit trades through the [OpenETF API](https://docs.openetf.xyz/developers/api.md) for ETFs that Manager runs. It applies the Trading Terminal's checks, uses a revocable credential and never returns the Trading Agent Wallet or a detached signature.

## Shares behave like ERC-20 tokens

Shares keep ERC-20-compatible metadata, balances, allowances, events and transfers under the Share Transfer Policy. They are non-rebasing, and the redemption right belongs to the current holder. The token claims no ERC-4626, ERC-7540 or ERC-7575 interface profile.

An integration tracks three separate states: an unpriced request, a fixed entitlement and an actual payment. When shares sit in a lending protocol or DEX, notices go to that contract address.

A [receipt](https://docs.openetf.xyz/transparency/receipts.md) stores raw protocol reads rather than a summary, because a default public RPC cannot re-read past protocol state. Each pricing receipt records the block where its cash first became observable and the block where it was fixed.

Transferability creates no liquidity or secondary price equal to NAV; subscriptions and redemptions always use NAV.

## External vaults get fact pages, not native status

**External vault integration — Coming soon.** An existing vault will get a sourced fact page for comparison with ETFs on OpenETF, without implying OpenETF execution, Manager participation or a Mandate. A vault can also route trades through Managed Execution; OpenETF's assurances then cover only its own path. A contract that only resembles the Factory interface gains no native recognition.
