# How to Vote ## How to Vote Voting in the Lynxify DAO isn't just a yes/no decision — it's a way of expressing exactly how you think the treasury should be working for the community. When you submit a vote, you're telling the protocol what percentage of the vault should go into liquidity pools, which pools should receive that liquidity, and how the staking allocation should be spread across assets. Your vote is weighted by your LYNX balance. The final treasury configuration is the weighted average of all votes submitted for that round. {% hint style="info" %} Before you vote, make sure your wallet is connected and that you hold LYNX. If you haven't picked up any LYNX yet, see the Mint Guide or the Swap Guide. {% endhint %} *** ### Getting to the Vote Page Head to [https://token.lynxify.xyz/dao](https://token.lynxify.xyz/dao/lp). From the DAO landing page, select **Management.** The management page is split into four sections, each one building on the last. Work through them top to bottom. *** ### Step 1 — Set Your Split The first thing you decide is how the total treasury budget gets divided at the highest level: between **Staking**, **LP Deployment**, and **Burn Reserve**. You'll see two sliders — one for Staking and one for LP Deployment. As you move them, the numbers update in real time and the pie chart on the right reflects your current split. The three values always add up to 100%. **What each category means:** * **Staking** — the portion of treasury assets placed into single-asset staking positions to earn staking rewards directly. * **LP Deployment** — the portion used to provide liquidity into trading pools, earning swap fees and LP incentives. * **Burn Reserve** — a buffer held back from deployment. This portion stays liquid in the treasury as a reserve. There's no single correct answer here — different splits carry different risk and return profiles. A higher LP allocation tends to mean more fee income but more exposure to impermanent loss. A higher staking allocation is more conservative. Your vote reflects what you believe the right balance is. *** ### Step 2 — Choose Your LP Pools Once you've set your overall split, the next section asks you which specific liquidity pools should receive the LP portion of the treasury. You'll see a list of available pool pairs — for example HBAR/USDC, HBAR/WETH, HBAR/WBTC, and others. Each row shows the current pool metrics: TVL, APY, and any active incentives. **How selection works:** Click **Add** on any pool you want to include in your vote. Once selected, the button changes to show the pool is active. You can select as many pools as you like. {% hint style="info" %} **The split between selected pools is always equal.** If you select two pools, each receives 50% of the LP budget. If you select three, each gets 33.3%. You're choosing which pools receive liquidity, not manually setting percentages. {% endhint %} This keeps things simple and avoids the complexity of managing precise per-pool percentages. If you believe strongly in one pool over others, the most effective way to express that is to select only that pool. *** ### Step 3 — Choose Your Staking Distribution Below the LP pool section you'll find the staking allocation. This is where you decide how the staking portion of the treasury (set in Step 1) gets spread across individual assets. You'll see the five assets in the Lynxify basket — HBAR, WBTC, USDC, WETH, and xSAUCE — each with a slider. Each slider controls what percentage of the staking budget goes to that asset's staking position. Move the sliders until the allocation feels right to you. The total must equal 100% before your vote can be submitted — the interface will flag this if something is off. Current staking APYs are shown next to each asset, along with the estimated dollar amounts at the current treasury size, so you can see the practical impact of your choices. *** ### Step 4 — Preview the Token Composition After setting your split, pools, and staking distribution, scroll down to see the **Projected Blended APY** and the **token composition bar**. This section shows you exactly what the treasury would look like — in terms of asset allocation and estimated yield — if your vote were the only vote counted at 100% weight. **What to look for:** * The **blended APY** gives you an at-a-glance view of the total expected return from your configuration across both staking and LP positions. * The **token composition bar** shows the resulting percentage of each asset in the vault. You can use this as a sanity check — if one asset looks unexpectedly over- or under-weighted relative to what you intended, you can scroll back up and adjust. This preview updates live as you change any setting, so feel free to experiment before committing. *** ### Step 5 — Submit Your Vote When you're happy with your configuration, scroll to the bottom of the page to the **Cast Your Vote** section. You'll see your current LYNX balance shown — this is your voting weight. Below it is the **Submit LP Vote** button. Click **Submit LP Vote**. This will prompt your connected wallet (HashPack or similar) to approve a transaction. Review the transaction details and confirm. {% hint style="info" %} Submitting a vote is an on-chain transaction and carries a small Hedera network fee, typically well under 1 HBAR. Your LYNX is not spent or locked — you're simply recording your governance preference on-chain. {% endhint %} Once confirmed, your vote is registered. The treasury configuration is recalculated from the weighted average of all active votes at the end of each voting round. *** ### Can I Change My Vote? Yes. You can return to the DAO page at any time before the voting round closes, adjust your settings, and resubmit. Your new submission replaces the previous one. Each wallet can only hold one active vote at a time. --- # 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://lynxify.gitbook.io/lynxify-docs/dao-controls/how-to-vote.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.