> For the complete documentation index, see [llms.txt](https://document.sunprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://document.sunprotocol.io/en/smart-contracts/dao-contract.md).

# DAO Contract

The DAO stores membership, proposals, votes, and execution state. Resolve proposal action names and parameter formats with DAO Metadata.

### Proposal reads

| Function                              | Purpose                                              |
| ------------------------------------- | ---------------------------------------------------- |
| `getProposal(proposalId)`             | Full proposal, votes, parameters, remark, and status |
| `getProposeByPage(page)`              | 20 proposals per page plus total count               |
| `state(proposalId)`                   | Live proposal status                                 |
| `proposalVoteStatus(proposalId,user)` | User voting status                                   |
| `hasVoted(proposalId,user)`           | Whether the user voted                               |
| `voteSupport(proposalId,user)`        | Recorded support or opposition                       |

Status values: `0=None`, `1=Active`, `2=Succeeded`, `3=Defeated`, `4=Executed`.

Membership reads include `isDAOMember`, `isFoundationMember`, member counts, and `getDAOMembers(offset,limit)` with a zero-based offset.

### User actions

* `applyJoinDAO()` creates a membership application proposal.
* `proposeByType(actionType,params,remark)` creates a typed proposal.
* `voteYes` and `voteNo` cast votes.
* `executeProposal` executes a successful proposal.

Proposal creation may require the USDT amount returned by `proposalFee()`. Check the receiver and approve USDT before submitting. Voting eligibility and thresholds use the membership snapshot taken at proposal creation.


---

# 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://document.sunprotocol.io/en/smart-contracts/dao-contract.md?ask=<question>&goal=<user_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.