---
# System prepended metadata

title: Yeeter App Specs
tags: [magesmiths]

---

---
tags: magesmiths  
---


# Yeeter App Specs

> The following section is a collation of notes during followup discussions on Yeeter


## Summon Flow
- **V1 Contract Runthrough: There are 4 transactions / steps for the summoning process (none goes through the proposal process)**
    - Transaction 1: New Factory summons a DAO with 1 Member, creates Minion (Admin Shaman) 
        - [ ] TBD on whether Multi Summon can fit into 1 transaction 
    - Transaction 2: Deploy config_yeeter & Add 
    - Transaction 3: Approve Yeeter in the DAO 
    - Signature (Step 4): DAO Registration is flexible and can be placed anywhere
- **Design**
    - [ ] Create new steps for the above transactions
- Summoning gas cost is estimated to be at least $2,000
- Shaman issues Shares for summoners only. Loot is issued for everyone Yeeting funds in. If Yeeters want shares, they can request shares via a normal proposal 
- Shareholders can add project metadata which can be edited later on. 
- TBD items 
    - We will have Multi-Summoner, but not Multi-Looter. 
    - We add a DAOhaus multi-sig as a Loot holder, but this will result in a flat fee instead of transaction fee
    - Proposal velocity & settings could be hardcoded into Fast, Medium, Slow


## Project Page 
- **General Discussion**: 
    - Shaman should control for cases where contributions come in odd/non-whole ratios 
    - V1: Contributions are only in native network tokens
    - Users can only send native network tokens to the address, instead of doing a function call  
    - Naming should be a sub-brand, e.g. DAOhaus Yeeter or Yeeter by DAOhaus 
    - Soft cap is more for social 
- **Design**: 
    - DAO activity can show proposals in Queue, Voting and Grace Period (Pulling this information should be manageable)
    - [ ] Remove Activity & replace it to a Leaderboard of Loot Holders
    - [ ] Branding should follow DAOhaus' look & feel 
    - [ ] Add some clarifications to explain Loot vs Shares / 'Core Team' vs 'Contributors'
    - [ ] Modal: Add a new Copy Address & Contribute Button to trigger sending of funds + copy on gas fees 
    - [ ] Modal: Disable button if user is on the wrong network
    - [ ] Success / Failure Message: Simple text copy with a link to the DAOhaus DAO 
    - [ ] Show a message if the project funds has hit the hard cap
    - [ ] Show a message for individual's hard cap
- Subgraph: 
    - Some work is needed to add historical data on Loots & logic. 
    

**Shaman Logic**
- Every X amount of funds added will issue new Loot
- Shaman can grant infinite shares to a Merkle Drop Minion which the admin controls and people can claim. 
- On receipt of native tokens, tokens will be wrapped and sent to the DAO

## Network Deployments  
- Deployment on testnets, Mainnet, Arbitrum/xDai/Polygon

## Archive Project 
- Add a hide flag in metadata, which hides archived projects on DAOhaus

## Refunds
- We let the refunds & deadline be socially determined. Any RageQuit or refunds are done by the summoners or contributors themselves. 
- The danger is if lootholders forget to RageQuit and shareholders can pass funny proposals to steal funds. 
- RageQuit costs $200+ for RageQuit & Withdraw






Notes from meeting 11/19
Spencer/Sam/Amos/Adrienne 

### Overview 
Building out the Yeet UI and the Moloch contract to support simple Shaman contracts. Depending on ratios determined by creator, tokens amounts will provide loot and/or shares in the DAO.

### Benefits
- Good use case to help with v3 learning and getting feedack
- Potential revenue generation 
- Can under the hood be upgraded to Baal without updates to UI 

### Current Workflow (Yeet/Juicebox/iRobot/Mirror):
* Send your funds and hope that something happens - funds are sent to a gnosis safe right now
    * Custody of funds is lost
* Snapshot voting via tokens by communities can be available

### Yeeter App Workflow
* Send funds to Yeeter project - 
    * Moloch v2 funds are sent to minion?
* Based on ratio determined by creators - shares/loot


## App Overview
### DAOhaus
* Link from DAO to Yeeter project page

### Yeeter Site
* Webpage for launching app 
* Highlights moloch DAO adventage over other alternatives 

### Create Project Workflow
* Summon a DAO
    * Deposit token
    * Multisummoner (needs to be extremly transparent on Yeeter Project Page)
    * Summoner gets 1 share
* Summon a Shaman 
    * Set up contribution/loot ratio
    * Start/End date/time
    * Min/Max contribution
    * Yeet token 
    * Funding Goal - max (min is social not in contract)
* Whitelist Shaman for DAO (this will be part of the summoning, not a seperate step)
* Yeeter project created 
    * Link to DAOhaus DAO
    * Unique link to share from Yeeter

### Yeeter Project Page 
* Project Name
* DAO Name 
* Time remaining
* Description of Project
* Link to DAO
* Contribution action
    * Output info on shares/loot
* Member list
    * Shares
    * Power 
* Activity list of contributions 
    * Ceramic profile(?) name
    * Address
    * Amount
    * Shares/Loot amount provided 
* Last 3 proposals 
    * Name
    * Link to proposal in DH
    * Current Status
    * Anything else? or fine to start?

### Other Yeeter Pages
* Yeeter Project List 
    * Active projects
    * Completed projects
    * Projects I've contrbuted to
* Link to documentation and FAQ 

## Revenue
* DAOhaus will take 2-3% of contributions in exchange for HAUS tokens. Ratio tbd on this.
* First few projects on the app will have fees waved for beta testing 

## Fundraising 
* What is fundraising goal is not met? 
    * If not met - Yeeter Project Page indicates this - ragequit button available 
    * Max funding goal reached - Project page stops accepting funds
* If met - archived project - page should still be available and links over to DAOhaus DAO with messaging

# Problems and Questions to Solve
* How much custom messaging allowed for creators?
    * If edits need to be made after creation, is there any way to do it?  
* Moloch v2 - where will funds be initially? If not in Treasury, how will ragequitting work? 
* What kind of problems with gaming the system/preventing sybil attacks on funds need to be considered? 
    * Possibly solution: only loot is available for contributors, shares must be requested through the DAOhaus app 
        * May need tribute for proposals to help with spam  
    * Possibly future solution: create snapshot voting for holder signalling
* How much messaging do we want to add (like Juicebox has) for informing users of the risks? This may be a good option for an initial MVP until proposal info is more integrated 
* What chains will this be available on? 


# Things to build
* forged shaman
    * w/ factory
    * init with contribution params
    * takes contribution, sends to dao treasury, assigns sender loot
* moloch v.2.3
    * shaman support
* subgraph 
    * mappings on the factory
    * use v2 mappings for v2.3
* bolt on app
* daohaus app link to yeet app in settings or dao home

