Main Page
From Decentralized Autonomous Organization
Contents |
Welcome to the Decentralized Autonomous Organization Wiki Page
The goal of this wiki is to provide an overview of terms & definitions related to new ways organizing supported by web3-technology mostly referred by as DAOs (Decentralized Autonomous Organizations).
A DAO can be defined as “a men/machine construct for the support of a community in reaching its mission and in which storage and transaction of value and decision, ownership & access rights, accountability and incentives can be designed, executed, recorded, and archived and where data and actions are recorded and autonomously executed in a decentralized way”.
DAO Elements
DAOs consist of at least the following basic elements:
They can also contain various (very important!) optional elements
Criteria Explanation Y/N Minimal criteria for being an organization (minimal set of functions/subsystem) A DAO must have the following subsystems: DAO Identifiable Data & Profile • A DAO must have a name and preferably additional identifiable data. • A DAO must be able to be found. Y/N Constitution • Rules for collaboration, governance & ownership are preferably explicitly publicly stated and acknowledged by the DAO participants • These rules should be coded into software as much as possible. • Decision making on a proposals and value transfers must only be possible by using coded logic. • Rules that are coded, either can be hard coded or updateable by decision of the community. These coded rules are guarded by the “Notary” function Y/N Treasury • A DAO must have a treasury function to manage its community funds and assets. • Having community-specific tokens is not mandatory Y/N Member(ship) & Organizational structures • It must be transparent, at least to the other participants, who the account holders are (at least their public key should be known) • A DAO may consist of only one organizational unit but can exist of multiple units or autons. • The organizational chart should preferably be transparent. Y/N Notary/Log • A DAO must log all transactions made by the DAO or by community members. • Each recorded transaction result must contain the digital signatures of the transaction parties and a timestamp. • It must be clear that a log item is the result of coded temper-proof logic. • For reasons of privacy protection, hybrid technology can be used where some data is stored on-chain and some data off-chain. Y/N Minimal criteria for being decentralized Agents participating in shared decision making / governance ≥ 2 There should always be multiple agents: • With governance rights. • Being involved in decision making on a proposal. Y/N Agents with ownership rights ≥ 2 There should always be multiple agents with ownership rights. Y/N Minimal criteria for being autonomous Logic (coded in software) must execute as agreed upon. When certain predefined criteria are met, code should execute automatically without the possibility to interfere one-sided (censorship resistant). Y/N Automatic execution of a decision (= approved proposal) Approved proposals should be automatically executed as described in the proposal if viable for automated execution. For example, a transfer of funds to a deposit from which the contractor can be paid. Y/N Used software and infrastructure Web3 based • Web3 software and infrastructure is decentralized, censorship resistant, secure and transparent (code & data). • Not all the software used by a DAO has to be web3. Y/N Information equality Internal equality of information There should be no information asymmetry among members so that each member can protect their interests and make informed decisions. Y/N
DAOs in practice
- Deployment or setup - one can code DAOs themselves or use no-code DAO deployment platforms
- Transfercrypto-assets
Notes to ourselves!
- We moeten hem gaan vullen met content! @Peter, je kan pas wat toevoegen als je inlogt. dus wel even login creeeren.
- Moeten even beter plaatje linksboven, kan via control panel
