# Kuza's core principles ### Why Kuza? At the root of **Kuza Finance** was the idea of leveraging the mechanics established by Olympus' innovative work, in conjunction with the principles of treasury management, selective token bonding, and protocol-owned liquidity, to serve the Meme Culture on Avalanche stimulated by the "Culture Catalyst" program. ### Our innovation What sets Kuza apart from other (3,3) model initiatives is the way it employs its treasury. Its focus is on providing liquidity, helping the growth and sustainability of the most established meme coins within the Avalanche ecosystem. This approach not only diversifies the possible strategies but also exploits the high growth potential of this asset category, providing an attractive perspective for the entire Avalanche ecosystem. ### (3,3) as a service - for Avalanche meme coins The term "3,3 as a service" in the context of Kuza designates the protocol's positioning as a permissionless external growth tool for any meme coin centered project on Avalanche. Essentially, Kuza's treasury aims to constitute a sufficient economic reserve, as well as a sufficient liquidity weight in meme coins, that it becomes an external growth opportunity for projects, which, through the acquisition of[ $QE](/kuza-finance/protocol/usdqe-and-usdrepo-kuzas-tokens.md) (Kuza's token), can exercise voting power to create a proposal in Kuza's open governance system that aims to integrate their project into Kuza's treasury, and can subsequently incite a favorable vote on this proposal through a number of possible means (airdrop, liquidity mining, whitelisting...). --- # 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://kuza-finance.gitbook.io/kuza-finance/introduction/kuzas-core-principles.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.