> For the complete documentation index, see [llms.txt](https://wiki.zenlink.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.zenlink.pro/zenlinkeden/protocol-mechanisms/tokenomics-vezlk-fees/fees.md). # Fees The Zenlink Eden protocol has two revenue sources: * **YT Fees** Zenlink Eden charges a 3% fee on all yields earned from all existing YT. * **Trading Fees** Zenlink Eden charges a certain percentage of trading fees on the "implied yield" of all PT trades, determined by the pool deployer (currently, only the Zenlink team deploys pools on Zenlink Eden). Essentially, Zenlink Eden taxes the yield of PT when a trade occurs. This method provides fair fees for all pools and maturities, as it scales with the pool's maturity (shorter maturity -> lower yield -> lower fees in USD terms). Since YT trades are also routed through the PT AMM, their fees are based on the traded PT. * **Fee Distribution** Zenlink Eden allocates 40% of the protocol revenue from trading fees of the corresponding pool to veZLK voters (e.g., veZLK holders who voted for the vDOT pool will receive 40% of the protocol revenue from vDOT trading fees). The remaining 60% of the protocol revenue from trading fees is distributed as follows: * LP Share: 20% * Zenlink Treasury Share: 40% In summary, the Zenlink Eden protocol currently divides all protocol revenue into three parts, with 20% allocated to LPs, 40% to veZLK voters, and 40% to the Zenlink Treasury. In the future, the 40% protocol revenue currently allocated to the Zenlink Treasury may be fully distributed to veZLK voters. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.zenlink.pro/zenlinkeden/protocol-mechanisms/tokenomics-vezlk-fees/fees.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.