# Role and Responsibilities

### DSW DAO's Role

The primary role of DSW DAO is to facilitate the launch and sound operation of the DeSciWorld ecosystem, including desci.world, science.tech and the World of DeSci conference circuit. DSW DAO is an evolving structure that is governed by the [Microbes NFT](/ecosystem/governing-dsw-dao.md).&#x20;

<figure><img src="/files/e0vThy087bnebvM2s2mL" alt=""><figcaption></figcaption></figure>

To deliver on its role, DSW DAO will access the resources held in its multisignature wallet.

{% hint style="info" %}
The DSW DAO is not yet deployed, thus all information here is displayed for informational purposes only. It is suggestive and not prescriptive for the operations of DSW DAO. Full managerial authority over its goals and operations lies with the DAO Governors.
{% endhint %}

Responsibilities

1. Ship web3-enabled products and tools that unlock the potential of open research
2. Further the mission of DeSciWorld in a value-aligned way
3. Support the development of the DeSci ecosystem and global community
4. Maintain accountability in leadership, both internally to the DAO and in DeSci proper
5. Act as the issuing authority of $KNOW emissions contracts

***

## The relationship between:&#x20;

### DSW DAO and [Proof of Knowledge](/ecosystem/ecosystem-map.md)

DSWDAO is tasked with developing and deploying the Proof of Knowledge smart contracts. It will continuously deploy new additions, updates and fixes. It will maintain the infrastructure necessary to serve thousands of researchers. You can consider Proof of Knowledge an incubated platform by the DSW DAO.&#x20;

The $KNOW token emissions that are primarily used to incentivise Proof of Knowledge participation are deployed by DSW DAO.

### DSW DAO and [$KNOW](/ecosystem/usddsci-or-usdknow-token.md)

The $DSCI token is deployed via two methods:

1. Token Generation Event (TGE)
2. Emissions Schedule

Both the TGE and the Emissions Schedule will be organised and executed by the DSW DAO.&#x20;

### DSW DAO and [desci.world](/ecosystem/terminal.md)

desci.world is considered a curated platform; DSW DAO assumes role of curator.

The DAO is tasked with maintaining the dataroom, adding new features and engaging with listings and sponsors. It will continuously aggregate information and news for the public good of proliferating DeSci; working together with listed projects to provide the most optimal experience for both user and project teams.

Further, Spotlight and NFT listings are not permissionless; application and selection require discussions with DAO members to initiate.&#x20;

### DSW DAO and [science.tech](/ecosystem/science.tech.md)

The primary function of science.tech is to provide permissionless access to on-chain tooling. Through the Research Collectives, descientists have an open-governance mechanism for their research goals. Each Collective is a self-governing unit, seperated from the control of DSW DAO through its unique governance token. The Collectives provide a seperation of authority from DSWDAO, giving autonomy over finances and operations to each Collective.

Understanding the DSW DAO as a facilitator of DeSci makes for a better appreciation of the DAO's purpose; the goals of DSW DAO align with proliferating access to decentralised tools through science.tech.&#x20;

### DSW DAO and [World of DeSci](/ecosystem/world-of-desci.md)

The World of DeSci conference circuit requires a significant amount or coordinated effort and resources. The DSW DAO acts the primary facilitator and overseer of the process..


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.desci.world/governance/dsw-foundation/role-and-responsibilities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
