Editing
Science DAO Framework
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== System design == === UI Software === Each sDAO must provide software that allows the public to access its capabilities. This software should provide representations corresponding to each of the areas of responsibility listed above. In the following subsections we discuss each area of responsibility, and the corresponding functionality we expect. Ideally the [[Front-end software|UI software]] will be formally governed by each sDAO, itself. However, this might reach a point of diminishing returns as smaller sDAOs will not have the resources to keep their UIs up to date with changing standards. The alternative is to allow the broader DAO community to manage the deployment processes for the UI software. SDF provides recommended defaults with off-the-shelf UI software, giving each DAO the power to select from basic useful parameters. In its purest, ideal form this system could support stateless client applications, serving all operational data reliably from blockchain storage. However, blockchain storage is expensive; so in practice, we only want to use it in cases where we really want the long-term guarantee. This means that we must implement a separate, off-chain stateful layer. There are a variety of options for this off-chain data layer, which we are exploring. For now we merely specify that such a layer must exist. === Smart Contracts === * [[availability smart contract|Availability SC]] - Enables DAO participants to declare their availability to review * [[work smart contract|Work SC]] - The main work most Science DAOs perform for fees are initially reviews of articles. Enables public users to request work products of the DAO. ** This smart contract will accept certain parameters that will function to specify the proposed agreement between the public user who pays the fee and the member worker who fulfills the work contract. * [[Validation Pool|Validation Pool SC]] - Enables REP-token-weighted democracy. * [[Forum|Forum SC]]: Database that records the entire history of the sDAO. Holds all article posts (aREP), review posts (rREP), and comments (cREP). Provides a platform where participants can discuss, propose, and vote on modifications to the sDAO operating parameters (rREP). All posts are linked by weighted references that determine the value of each post. [[Judicial governance|Judicial governmental review]] is partly enabled through the ability to reweight posts by subsequent [[Forum reference mechanisms|references]]. === Hard and soft protocols === There are both formal and informal processes ([[Governance#Hard protocols|hard]] and [[Governance#Soft protocols|soft]] protocols) associated with each of the above outlined areas of responsibility. Hard protocols are specified by code, and enacted by running systems, whether on- or off-chain. Soft protocols refer to patterns of participant behaviors.
Summary:
Please note that all contributions to DAO Governance Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
DAO Governance Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
Edit source
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information