# 1.1 - What is nest? {% embed url="" %} Welcome to **nest,** the **MetaDEX built for Hyperliquid**, designed to scale liquidity on HyperEVM and turn onchain activity into long-term ecosystem growth **while creating HYPE-aligned buy pressure through protocol design**. On Hyperliquid, HYPE is the dominant store of value. If you build on HyperEVM but your protocol doesn’t connect to HYPE value accrual, you end up with a disconnect: apps grow, tokens rotate, but the chain’s core asset doesn’t fully capture the upside. nest exists to bridge that gap by **plugging directly into HYPE-aligned value flows** and turning **every swap** into fuel for deeper liquidity and stronger alignment over time using the [HYPE Engine](https://docs.usenest.xyz/nest-explained/2.6-hype-engine). *** ### What you can do on nest * **Swap** any supported HyperEVM token with best-execution routing * **Provide liquidity** across three pool types (Classic, CLAMM, Automatic) and earn NEST emissions * **Lock NEST** for veNEST: earn 100% of protocol trading fees and vote to direct emissions * **Vote** each epoch to allocate NEST emissions to pools of your choice * **Deposit into HEV** for automated voting, fee compounding, and MEGAHYPE exposure {% hint style="info" %} **Key distinction:** LPs earn NEST emissions — not trading fees. Trading fees go to veNEST holders. This is the core mechanic of a MetaDEX. {% endhint %} --- # 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.usenest.xyz/start-here/1.1-what-is-nest.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.