StableUnit DAO is in the process of forming its organizational structure and governance. We envision a structure that ensures productivity and scalability while preserving creative freedom for its members.
At a high level, the StableUnit DAO is governed by its community of NFTs and suDAO token holders. All members are responsible for providing the vision and goals for StableUnit, and for interacting with its active contributors to help build this vision. The protocol development is being maintained by a core team. DAO votes on core-team performance and can vote to withhold core-team reward for 3 additional months if a particular milestone hasn't been reached. At the end of the 3 months period DAO can decide should they change the core team, or the initial return of all funds for suDAO token holders. DAO members can also propose to form separate teams to contribute to the project. Please see details on how to contribute.
The StableUnit DAO protocol is governed through a series of following steps, each representing increasing levels of consensus from the DAO. Proposals and ideas are surfaced on the discord and are finalised once deployed on-chain. The progression of increasingly binding consensus can be seen below.
The highest level discussions may surface ideas in many places including (but not limited to) the #dao-ideas channel on Discord, Telegram, Twitter. When it appears that there is enough general support, the initiator may formalize the idea by submitting a more formal proposal.
Each proposal has a dedicated thread in Discord 『🗣』dao-proposals channel where the outcome-driven discussion takes place. The goal at this step is to finalize any unresolved issues and formalize off-chain consensus. Please see a 👉 Proposal guideline page.
If the prior step did not arrive at an obvious consensus, sentiment may be gathered in a non-binding way via off-chain signaling from token holders. This provides more insight into the likelihood of the outcome of the final binding vote by using actual voting power. https://snapshot.org/#/stableunit.eth
Requirements are implemented in code, launched on testnet, and audited for security.
The concluding step is a binding vote that happens on-chain. The on-chain vote is “binding” because its success results in the execution of code, without intermediaries. This includes deploying new protocol contracts or modifying the state of existing ones.