---
# System prepended metadata

title: DAOsquare CCO MVP Full-Specs

---

# DAOsquare CCO MVP Full-Specs

# Spec Template

### Spec Type

- [X] Feature
- [ ] Maintenance
- [ ] UX Improvement
- [ ] Bug 

### Spec Size
- [ ] Goal/Objective (long term change, multiple initiatives, cross-community)
- [ ] Initiative (multiple epics / cross-team or single team)
- [X] Epic (A collection of tasks / single team)
- [ ] Single Task 
- [ ] Bug 

## Overview 
Build a customized view to show only DAOsq CCO DAOs and the progress of each CCO DAO in terms of funds raised, contribution :: share ratio, plus a polished CCO view for each of these CCO DAOs. 

## Details 

Please fill out the following sections. 

### Problem:
DAOsquare wants to curate a number of CCO DAOs for projects it supports in a way that makes it easy for DAOsquare members and its network to view these CCOs and contribute to them. DAOsquare needs this done by May 10th for the first of these CCOs. 

They would also like an easy way to set up farms for each CCO at the conclusion of that CCO. 

### Solution: 
Given the limited time, our solution is to:
- create a custom view on the DAOsquare DAOhaus page that essentially shows a version of the explore page sorted for only DAOsquare CCO DAOS, displaying their progress and status in addition to the normal data. 
- polish the CC1 UX so that it can be applied to each of these DAOs 
- create a more repeatable system for creating CCO-related farms, contribution manager bots, and whitelist uploads. 

### Implementation Details:
The implementation details are split out by the different views. These will be broken into subtasks and assigned.  

**DAOsquare CCO DAO List View:**
- Create a special explore page that sorts only for DAOs tagged as DAOSquare CCO DAOs.
- The  easiest solution for creating this page is probably a new route that displays the explore page with the sorting auto-set to only display these DAOsquare CCO DAOs.
- We could add an additional field to our database that tags DAOs as DAO, CCODAO, DAOSQCCODAO in order to track these and differentiate them from any non-DAOsquare CCO that might also be going on.
- Modified DAO cards that display the following information: 
    - Time left in CCO
    - CCO contribution goal
    - CCO contribution progress
    - DAI to CCO token ratio 
    - NOTE: The above are also items that we can store in the web2 database and only display if the tag is CCODAO or DAOSQCCODAO

**CCO DAO PAGE VIEW:** 
- Polish the CCO page and use theme colors more inline with the DAOsquare desired theme /color 
- Add a place to the CCO UI for the particular project name. 
- Add a place to explain in 1 sentence whitelist universe / restrictions 

CCO DAO Creation:
We will need a more repeatable, scalable process for creating these DAOs. Rather than include some special CCO DAO summoner in the create flow, we can just use the following process: 

- DAOsquare emails us the details for a new CCO DAO at least 5 days before the scheduled CCO is to begin. The details must include:
    - The DAO name
    - A brief project description and link to the project info (website, github, twitter, etc)
    - The CCO goal 
    - The contribution currency 
    - The contribution to tokens ratio
    - Any other rewards being offered (i.e. NFTs)
    - The CCO start and end dates 
    - A json of the whitelist addresses and a brief explanation of what qualified someone for that whitelist. 
- We create a new DAO using the standard summoning form with DAOsquare and a CCO team address as the two shareholders (1 share each). 
- We launch a transmutation minion for that DAO. 
- We manually tag the DAO as a DAOSQCCODAO and add the additional CCO information into our database and hide the DAO until 1 day before the open date. 
- We upload the whitelist to an Airtable and deploy a new bot to check eligibility / contributions against that whitelist. 
- We create new farm pages to go live when the CCO tokens are claimable. 
- At the end of the CCO we direct the CCO team to fund the transmutation minion with their tokens and then submit the transmutation proposal.  


**Are there wireframes or code patterns?**
- [X] Yes (provide link)

DAOhaus wireframes: 
https://www.figma.com/file/DyuLU9SbCf8BWNrUMnSXsi/DAOHaus-v2-UX?node-id=920%3A0

    DAOsquare wireframes (ideal version / not MVP): https://xd.adobe.com/view/d3d93166-31a1-4907-b738-4f80ef02ca94-868a/screen/6811818e-5d41-4059-804e-2287de46448d
- [ ] No (ok for bugs, maintenance)

**Provide a detailed spec for technical implementation and the required updates to each part of the app (if applicable). 

**Does this require any third-party integrations?**

- [ ] Yes, if so, list: 
- [X] No 

**Repos**
**Link to repo once created

**Documentation**:
**Link to any other documentation once created

**Test Resources**:
**Link to tests once created


## Deliverable
**List what is required to consider this task complete. 

 
## Notes
