> For the complete documentation index, see [llms.txt](https://docs.builtbydao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.builtbydao.com/governance/voting.md). # Voting Power The contracts separate contribution, capital, and council stewardship into different houses so one form of participation cannot silently dominate another. ## Contributors Contributor power uses snapshotted effective contribution credits, then applies bounded rank and tenure weight: ``` base power = √(effective contribution credits × 10,000) final power = base power × bounded rank-and-tenure multiplier ``` This is a square-root curve: four times the effective credits produces twice the base power. Housing Loyalty does not enter contributor power. | Effective contribution credits | Base power | | -----------------------------: | ---------: | | 100 | 1,000 | | 400 | 2,000 | | 2,500 | 5,000 | For small contributor groups, The policy can require one-member-one-vote totals rather than pretending a tiny sample is a mature weighted electorate. ## Investors Investor credentials carry their configured weight only inside the Investor house. A person who holds both member and investor credentials cannot use capital to inflate contributor power. On investor-required subjects, the contract applies its coalition rule to overlapping participation. ## Council Leadership Council members participate through consent or a reasoned objection, one person at a time. There is no personal unilateral veto; the category's objection threshold determines whether the Council house blocks. ## Frozen eligibility Voting opens only after an eligibility snapshot commits the voter set, per-house counts, and power totals. Each voter proves inclusion against that snapshot. Live member standing is still checked for contributor votes, so suspension cannot be bypassed by an old snapshot. The exact formula, bounds, and policy seeds live in the current contracts and deployment fixture. Public examples illustrate the curve; they do not replace the deployed manifest. ballots are keyed to stable account identity. Authorized wallet recovery does not create another vote or recalculate the account’s frozen power. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.builtbydao.com/governance/voting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.