# The Ticketing Revolution DAO

<figure><img src="/files/niOila1rNWxyDbGBBR4j" alt=""><figcaption></figcaption></figure>

The OPEN Ticketing Ecosystem has a goal of continuing to bring ticketing infrastructure and business processes onchain, through the Ticketing Revolution DAO.

Here DAO participants can seed ideas, discuss proposals and vote on matters that can both positively impact the OPEN Ticketing Ecosystem along with the global ticketing industry.

The DAO operates across Discourse and Discord, with plenty of ideas to chew upon for new participants.

The DAO is run by DAO Representatives who are elected to represent the DAO every 6 months. DAO Reps are able to enact small decisions that don't require wider DAO consensus, such as small grant applications and seed new votes to the community.

{% embed url="<https://discord.com/invite/onopen>" %}

{% embed url="<https://ticketingrevolution.discourse.group/>" %}

### DAO Warchest

The DAO has a war chest of approximately 2 Billion OPN which it can use to grow the DAO, bring in new business and incentivise the development of new infrastructure from community builders.

### DAO Builder Grants

In an effort to grow the suite of onchain ticketing infrastructure, the DAO has a builder grants program of up to 10k in individual grants to provide ecosystem builders looking to contribute infrastructure that can benefit OPEN and its integrators.

You can read more here:

{% embed url="<https://mirror.xyz/openticketing.eth/emcqhY4vddbB8o1VgWW2seESTDGJBvYhoky9VSJoOMU>" %}


---

# 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://learn.onopen.xyz/the-opn-token/dao.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.