What is a DAO?
A DAO describes structures where collective decision-making and resource management are organized through specific rules and on-chain tools.
On this page
What does DAO mean?
DAO stands for Decentralized Autonomous Organization; it describes a form of organization where collective decisions are executed through specific rules and often via blockchain tools. It can be used to manage a protocol’s treasury, distribute grants, or participate in product decisions.
The presence of “autonomous” in the name does not mean that all operations are carried out without human intervention. Proposals can be prepared by humans, discussions can take place in forums, and certain operations may be implemented by elected teams. The technical and legal structures of DAOs vary from one another.
An example of a treasury decision
Imagine the community discussing a 50,000-unit payment to a development team. First, the proposal is prepared, then a vote is held. If passed, the payment can be sent automatically via a smart contract or executed by the administrators of a multi-signature wallet. In these two methods, the distribution of authority between the decision and the implementation differs.
Participation in voting may depend on token balance, membership, or other rules. Not every DAO follows the “one person, one vote” principle. Large token holders may possess more voting power.
How is decentralization understood?
Token distribution, proposal thresholds, participation rates, treasury control, and emergency pause powers should be examined together. Many people speaking in a forum does not indicate that decisions are distributed equally. A small group of administrators may have the final say.
DAO membership or token ownership does not automatically provide limited legal liability. Rights and obligations depend on the structure and the rules of the relevant country. When joining a project, it is necessary to understand not just the community rhetoric, but also what authority you are assuming and what transaction you are signing. Governance by code does not eliminate the possibility of faulty decisions or software vulnerabilities.