---
# System prepended metadata

title: How Govrn thinks about DAOs
tags: [vision]

---

# How Govrn thinks about DAOs

###### tags: `vision`

## tl;dr

## Summary

Govrn thinks about DAOs as nothing more than groupings of contributors or contributions towards a common goal.

The magic of DAOs is that you're able to create groups and communities from any attribute or trait, then give the the super powers of organizing. You could create a DAO of everyone with two left hands if that attribute was on chain.  Once that attribute is on chain, you just have to create a relationship of everyone with that attribute.

So for Govrn, we want anyone to be able to create a grouping or relationship based on any contributions the group as deemed valuable.

Once that relationship is created, then we can give them DAO super powers, organizing.

Note, that this is also where we are thinking of inserting the [Govrn Biz Model](https://hackmd.io/oN6jvp9FQSWXGAJfP2WnZA).

## What functionality do users receive when they updated to a DAO?

**Ideas:**

Key Pillars:
- Value Pool
- Validity Pool
- Relationship/Linkage Creator

High Priority:
1. Create a context for value assignments
1. Create a context for validity attestions
1. Create a verification framework
1. Create a valuation framework

Low Priority:
1. Create a DAOuri location
1. Integrations to other DAO tools


## What does it mean to `Create a DAO` on Govrn?
Creating a DAO means creating a relationship between different contributors.
- This can be done by identifying the Contributors or by identifying a set of contributions and backing into the contributors

**Question:**  Should this be an onchain relationship?
- I think yes
- The relationship could be a shared context of attestations or assignments
- **🌟 Implication** - in the data structure of attestations and assignments, we need to be able to relate them to each other somehow.


## Unique Properties of a DAO
- DAOs can be ephemeral, but these should be thought of DAOs that are ephemeral in "activeness", not "existence".
    - If a DAO ends up "closing", that should be thought of as moving from Active -> Inactive.
    - The relationship that created that DAO for that moment in time should exist in perpetuity.
- Govrn DAOs can have 0 treasury, they can be just be a specific relationship between contributors and contributions
- DAOs should be able to import relationships from other DAO frameworks
- DAOs should be able to export the Govrn relationships to other frameworks


## Follow up Actions:
1. Start building out the user flows and experiences we want users to go on and get back into the structures and implementation details



## Random thoughts

- Creating a "DAO" means creating a value pool for the value conversion to happen from
- if you want to make value assignments for a contribution, it has to be assigned to a value pool
- this plays into the biz model where everyone that subscribes to a value pool, can opt into paying for it
- the value pool is what a DAO sets up
- anyone can setup a value pool and others can join at different levels as well
- example
    - i made a conribution to RG by meeting with sasquatch
    - this is a contribution that maybe only sasquatch finds valueable, so he gives a value assignment from is own value ppol
    - other people could decide to join sasquatches value pool, or just fund it 
    - that then becomes it's own DAO of sorts


## User Journey of a Govrn DAO

### First Journey

1. A user comes onto Govrn, and reports their contribution.
2. They want to attribute it to a DAO, but the DAO doesn't exist yet.
    - they can either create a new DAO or submit it un-assigned
1. When they create a new DAO, on the frontend we are "assigning" it to a DAO.
    - this can be thought of as adding an attribute to a contribution
    - that is and should be a 1 to many relationship. 

What we want to be able to do is relate different contributions to one another.
- The interesting part of this is that we want different types of on chain records to be able to be related together.
- Currently there is DAOs/DAO memberships that can be based on a particular NFT or a particular token, but what we want to enable is heterogenious on chain primitives to be able to be related together to create a DAO
    - Example, it's easy for everyone with a bored ape to be identified as a DAO member.  What we'd want is that a bunch of different types of NFTs, Bored Ape or a dog or a squiggle or a specific nft, to have some relationship so that together they can have an "on chain value pool to be governed"
    - The idea is that once these relationships are created, everyone tthat has an NFT that is related together with a specific relationship can get be identified as a DAO member and have their value assignments play into the distribution of the value pool.



## Can 1 contribution be enough to consistute a DAO?

- A DAO must have a minimum of 2 contributions?