> For the complete documentation index, see [llms.txt](https://punkland.gitbook.io/grannys-house/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://punkland.gitbook.io/grannys-house/en/grannydao.md).
# GrannyDAO
GrannyDAO is a community connected to the Granny's House lore, where you can come up with and share your own opinions that may trigger changes to that lore by posting or voting on items posted by other players. The Granny's House Development team is obligated to review comments that come from GrannyDAO for applicability to the Granny's House universe and to respond to them. This cooperative relationship between the game and the community will allow Granny’s House to keep making its universe more complete. GrannyDAO uses the GrannyDAO token (GDO) on the blockchain to ensure transparency and fairness. This will be the basis for the development team and the community to form a deep and trustworthy relationship, creating active two-way communication.
### Token Information
Blockchain
Klaytn Mainnet Cypress
Contract Address
0x6b3e09010803860625e780de45814513dcc125b1
Symbol
GDO
---
# 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://punkland.gitbook.io/grannys-house/en/grannydao.md?ask=&goal=
```
`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.