# CurveYield DEX CurveYield DEX is a Balancer V3-style liquidity layer with CurveYield-specific economics built around it. CurveYield DEX is designed around unmodified Balancer V3-style pool contracts, with CurveYield-specific factory, fee, routing, and settlement infrastructure. Public contract references will be updated as each CurveYield-owned deployment is finalized. The DEX has two main layers: | Layer | Purpose | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | AMM layer | Weighted pools, stable-style pools, multi-token liquidity, swap execution, pool shares, and routing | | CurveYield economic layer | Admin fee policy, creator fee routing, partner revenue, permanent protocol-owned liquidity, incentives, settlement automation, and DAO-directed value capture | ## Problems CurveYield DEX solves Most DEX liquidity is temporary. A protocol launches a pool, pays incentives, attracts liquidity during the campaign, and can lose much of that liquidity when incentives decline. CurveYield DEX gives protocols tools to convert pool economics into long-term or permanent protocol-owned liquidity. Swap fees, creator fees, DAO incentives, and treasury-owned LP positions can be routed in ways that deepen markets while also building durable balance-sheet assets. The goal is not simply to create another place to swap tokens. The goal is to make liquidity programs more efficient, more durable, and more aligned between traders, LPs, protocols, frontends, and the CurveYield DAO. ## Supported pool types CurveYield DEX is designed around two primary pool families. | Pool type | Use case | | ----------------------- | ----------------------------------------------------------------------------------- | | Weighted pools | Arbitrary token weights for assets that are not tightly correlated | | StableSurge-style pools | Stable, correlated, or rate-aware assets; optional rate providers where appropriate | Both directions are designed for up to 8-token pools where the underlying pool family supports that structure. Rate-aware assets require correct accounting. A vault share, rebasing asset, or remote-chain vault token needs a pricing path that reflects its actual value. ## Admin fees All percentages in this section refer to generated swap-fee revenue, not the full swap amount. CurveYield LP swap admin fees start at **20%** of pool-generated swap fees. For qualifying protocol-owned-liquidity pools, the admin fee can be reduced as low as **5%**. If a swap generates $100 in LP swap fees and the applicable admin fee is 20%, then $20 is routed through the admin/protocol-side fee lane. ## Creator fee splits CurveYield expands on Balancer-style creator fee capabilities by allowing creator-side LP fees to be split across supported destinations. For approved protocol pools, the total creator-side allocation can be as high as **60% of generated swap-fee revenue**, subject to CurveYield policy, pool configuration, and governance limits. Standard pools may have lower limits, and the elevated creator-fee policy is not a universal entitlement for every pool. Creator fee, permanent liquidity fee, and creator payout logic are handled through generated creator fee splitters and the CurveYield settlement router. Valid creator payout tokens are the pool tokens or the pool BPT. ## Permanent protocol-owned liquidity CurveYield DEX includes a permanent protocol-owned liquidity system. Protocols can route pool economics into a permanent liquidity vault. Instead of paying incentives that disappear when the campaign ends, a protocol can use CurveYield to gradually convert trading activity, pool fees, and incentive programs into long-term LP ownership. Permanent liquidity can be managed over time. Liquidity can be shifted from one pool to another when market conditions change, and outdated tokens can be replaced when a protocol migrates, upgrades, or changes its liquidity strategy. Exits may exist only where governance permits and may include an exit fee, which discourages short-term use while preserving flexibility for legitimate treasury, migration, or risk-management needs. ## Approved protocol pool emission support CurveYield may allocate crvYIELD emissions to qualifying approved protocol pools at no cost to the partner protocol. This is a DAO-funded incentive policy, not a permanent entitlement. It applies only to approved protocol pools and depends on DAO budget, governance approval, campaign limits, pool quality, and future policy changes. A protocol pool qualifies for consideration by satisfying at least one of the following conditions: * using CurveYield's permanent protocol-owned liquidity feature; or * including `crvUSD` or `cyUSD` as at least **5%** of the pool. ## Partner frontends Protocols are invited to build frontends on top of CurveYield DEX. For approved partner frontends, up to **20% of generated swap-fee revenue** may be allocated to the frontend or integration partner for pools generated through that frontend, subject to CurveYield policy and pool configuration. This gives protocols, aggregators, communities, and application builders a direct economic reason to drive liquidity into CurveYield pools. ## Bribe efficiency support CurveYield may operate a DAO-funded bribe efficiency support policy for approved protocol pools. Under this policy, approved bribe campaigns for crvYIELD emissions on CurveYield pools may receive a minimum **105% capital-efficiency support target**, up to a maximum campaign size of **$10,000 per epoch per protocol**. In this context, 105% means the DAO may target at least $1.05 of crvYIELD emission value for every $1.00 of approved partner bribe value, subject to the cap and governance limits. For example, a $1,000 approved campaign would target $1,050 of emission support if funding, market pricing, and governance conditions allow. This support is designed to make approved incentive campaigns more efficient for partner protocols during the early growth phase of the DEX. It is not permanent and does not apply to every pool. ## Yield-bearing assets in CurveYield pools CurveYield is designed to support pools built around productive assets, not only idle tokens. The protocol has built bridge and oracle infrastructure intended to make yield-bearing assets usable in CurveYield pools across supported chains. This includes liquid-locker tokens, vault tokens, wrapped yield positions, and other productive collateral that may already earn external yield before being placed into a pool. Some target assets may show high APYs during certain market conditions. Those figures are not fixed returns. APYs change, incentives change, asset prices move, borrowing demand changes, and strategy risk varies by asset and chain. ## User interface The CurveYield DEX interface is designed for: * pool discovery; * swaps; * pool creation; * deposits and withdrawals; * pool analytics; * contract references; * supported vault and bridge routes where enabled. Governance-only controls, pause controls, and advanced protocol configuration remain outside the normal user flow. ## What makes CurveYield DEX different CurveYield keeps core AMM behavior close to proven Balancer V3-style pool mechanics, then builds a liquidity economy around them. The DEX combines flexible pools, fee routing, creator economics, permanent protocol-owned liquidity, yield-bearing assets, partner frontends, incentive support, and DAO-controlled settlement into one system. For traders, the DEX is a source of liquidity. For LPs, it is a venue for earning pool fees, incentives, and potentially underlying asset yield. For protocols, it is a way to turn liquidity programs into long-term treasury infrastructure. For the CurveYield DAO, it is a fee-generating and liquidity-accumulating foundation that can support the rest of the ecosystem. --- # 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.curveyield.com/products/curveyield-dex.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.