# How Votes Are Calculated The Lynxify DAO gives token holders a say in how the protocol's yield is attributed. But designing a fair voting system is harder than it sounds. This page explains the choices we made, why we made them, and how the system is built to stay fair as it grows. If you disagree with how this system was established we would love to hear your thoughts in our [Discord](https://discord.gg/TkbrWN855a). *** ### The Sybil Problem The first issue you have to account for when developing a voting a system is a Sybil Attack. A single person with 100 wallets gets 100 votes, which means one well-funded actor can completely flood a vote and make the result meaningless. We wanted to build something that doesn't reward that behavior — where creating extra wallets gives you nothing. *** ### How Voting Power is Calculated In Lynxify's DAO, your voting power is determined by how much you've contributed to the protocol vault. This counter acts any reason to utilize a Sybil Attack. **Every 1 LYNX you hold equals one vote.** Because LYNX is backed 1:1 by the underlying treasury basket, holding LYNX is the same as having a proportional stake in the vault. The more you've put in, the more say you have in how it's managed. Wallets with no LYNX have no voting power, which makes creating extra empty wallets completely useless. This means: * **No Sybil advantage.** Splitting your LYNX across ten wallets gives you the same total voting power as holding it in one. * **Skin in the game.** The people with the most votes are the people with the most at stake in the protocol's success. * **Simple to verify.** Voting power can be read directly from on-chain LYNX balances — no snapshot games or off-chain tracking needed. *** ### The Trade-Off: Whale Concentration We're not going to pretend this model is perfect. Dollar-weighted voting has one well-known weakness: large holders — sometimes called **whales** — can accumulate enough voting power to push decisions through on their own or in a small group. We think this trade-off is worth making, because the alternative (one-wallet-one-vote) is simply too easy to game. But we also think whale dominance is a real concern that needs a real solution — not just an acknowledgment. That solution is delegation. *** ### Delegation — Coming Soon Delegation is currently on our roadmap and will be rolled out in a future update. This section explains how the system will work once it launches. #### What is delegation? Delegation lets you hand your voting power to someone else to use on your behalf. You keep ownership of your LYNX — you can undelegate at any time — but while it's active, your votes are counted alongside theirs when proposals go to a decision. #### Delegate pools Rather than delegating to a single person, the Lynxify system uses **delegate pools** — groups of voters who coordinate their position and vote together. Any LYNX holder can join a pool and assign their voting weight to it. This matters for two reasons: **1. It dilutes whale dominance.** A pool with 500 members, each holding a modest amount of LYNX, can collectively outweigh a single large holder. Delegation gives smaller participants a way to combine their power into something meaningful. **2. It allows passive participation.** Not everyone wants to research every proposal, follow governance discussions, and vote on each one manually. Delegation lets you assign your votes to a pool you trust and step back — your weight still counts, but you don't have to show up for every decision. ### --- # 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-votes-are-calculated.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.