# Introduction **VeTokenomics** refers to the economic model and incentives that are built into a token design. It outlines how the token will be used, distributed, and valued within an ecosystem, and how it incentivizes behavior that supports the overall health of the ecosystem. This can include things like token distribution through mining, staking, and airdrops, as well as the use of the token as a means of payment or as collateral for loans, among others. **Game theory** is a branch of mathematics that studies decision-making in situations where the outcome depends on the actions of multiple players. VeTokenomics often uses game theory to design its economic incentives, in order to encourage certain behaviors that benefit the overall health and stability of the ecosystem. This behavior can be achieved through mechanisms such as staking, governance, and network fees, which incentivize good behavior and disincentivize bad behavior. For example, staking rewards users who hold and lock up tokens, while punishing those who sell or transfer their tokens frequently. This helps to maintain a stable token price, ensure sufficient liquidity, and secure the ecosystem. By using game theory to design these incentives, VeTokenomics can create a **self-reinforcing system** that benefits all participants and helps to **ensure the long-term success of the network**. --- # 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.usdfi.com/dual-ve-tokenomics/introduction.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.