> For the complete documentation index, see [llms.txt](https://docs.chainguardians.io/cgdao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chainguardians.io/cgdao/governance-process/participation-vs-apathy.md).

# Participation vs Apathy

## Encouraging Participation 

* Implementing two tiers of votes
  * Proposals with low impact only require 1000 VP to vote. 
  * Proposals with high impact affecting protocols/governance/treasury will require 10,000 VP to vote. 
* Using Elections 
  * Electing community members to show commitment towards more decentralization. 
* Incentivize voting 
  * “I Voted Poaps” 
  * Possible Guardian NFT

### Avoiding Voter Apathy 

* Creating template and time requirements for proposals
  * Templates make it easy for users to progress through research and get to voting efficiently
  * Time requirements allow good proposals to filter to the top after peer review. 
* Direct proposal flows through forum admins. 
  * This filters useless and junk proposals which can dilute and bore users. 
* Present tools for ease of use voting, data tracking, and provide governance education.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.chainguardians.io/cgdao/governance-process/participation-vs-apathy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.