# EarnPark On-Chain Architecture EarnPark is moving to a full on-chain protocol layer — **EarnPark OnChain Protocol** — on which the platform's yield strategies will run. \ The architectural principle: *one underlying — one wrapper — many strategies*, with compliance enforced at the system's boundaries and a clean separation between reserve, yield and protocol revenue. * **Boundary AML.** Compliance is enforced at mint (ingress) and cash-out (egress), not on every secondary transfer. This preserves the full on-chain utility of the asset while keeping a defensible compliance perimeter. * **Wrapper rail.** For each underlying asset the protocol issues a single freely transferable wrapper token (e.g. USDEP for USDT), fully backed by a reserve of that asset. Reserve yield accrues to the protocol as a separate revenue stream — the wrapper remains a transport layer, not a yield-bearing instrument. * **Strategy products.** Each strategy is a standalone product with its own share token, wrapped in smart contracts that hard-code the rules of capital movement: approved addresses, exposure limits, cooldowns. Capital cannot move outside the defined perimeter. Strategy access is opened through **non-custodial wallets**: the user holds wrapper and strategy share tokens directly and decides whether to stay in the clean wrapper or enter a specific strategy. Contracts are verifiable on-chain; upgrades go through timelock. Integration of the PARK token into the on-chain layer is the phase that follows protocol launch; specifics will be added in later revisions of this whitepaper. > The full architecture, economic model, risk framework and go-to-market are described in a separate document — [*EarnPark OnChain Protocol Whitepaper*](/earnpark-protocol/whitepaper-versions.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.earnpark.com/token-whitepaper/park-token-utility/earnpark-on-chain-architecture.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.