# Verifi

## What's in the docs?

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><h4>User guides</h4></td><td>Discover non-technical documentation for the platform.</td><td><br>This is the go-to place for creating spaces, proposing ideas, or casting votes.</td><td></td></tr><tr><td><h4>Protocol</h4></td><td>Explore the technical documentation for the Verifi protocol. Visit this section to gain a deeper understanding of the protocol architecture.</td><td>Go here if you want to understand the protocol architecture.</td><td></td></tr></tbody></table>

## What's Verifi?

**Verifi** operates as an on-chain voting protocol, consisting of modular smart contracts that collaboratively handle all bookkeeping. From a technical standpoint, it's a network of smart contracts interacting to manage all aspects of the protocol. Verifi is **fully on-chain**, meaning:

* **Censorship Resistance**: Every individual has the ability to cast a vote. The protocol operates independently of off-chain or centralized services that might have the authority to censor votes. \[1]
* **On-chain Voting Power**: The voting logic is entirely on-chain and auditable, ensuring transparency in computing voting power and making decisions on proposals.
* **Trustless Execution**: Proposal on-chain transactions are automatically executed upon the successful passing of a proposal.

\[1] While off-chain services exist for use with Verifi, they are optional and cannot result in censorship. 🙀


---

# 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.verifi.network/readme.md?ask=<question>
```

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.