# QY + IP

Although larger than initially imagined these are exciting projects and we are eager to support the ZuVillage and Ethereum Community Fund.

From smart contracts, to interface designs this goes way beyond simply forking Yeeter and DAOhaus Admin.

Splitting Quadratic Yeeter and Inverted Precedent allows each project to focus on its unique features and requirements while reducing dependancies and enablig concurrent development.

- What is the connection between these two projects?
- Why do they make sense together?

## [Quadratic Yeeter](https://hackmd.io/8pv3LIVLSqe5Fip4ZvvuXA?view)

Quadratic Yeeter combines Moloch and Allo—in a way we haven’t seen. Adding ragequit to matching rounds is a big step for accountability. The unruggability this brings is something we believe is essential for building trust in community funding. Rounds of Yeeters promoting each other and competing adds some cool dynamics. And setting up a parent and sub DAO structures for projects demonstrates standards we are excited to help communities put into action.

### Questions

1. Will Yeeter projects be organized by distinct rounds?
2. Will each round have its own matching pool?
3. Are projects within a round assigned the same group of voters?
4. Should contributors who Yeet receive voting shares?
5. How will matching funds impact the distribution of shares?
6. How does ragequit affect the matching distribution if a participant exits before execution?
7. Do you have any concerns about Sybil resistance?

## [Inverted Precedent](https://hackmd.io/PcGIaCwLTOid52aZ7T7JCw?view)

Inverted Precedent finally adds a feature we’ve been wanting for a long time: comments on votes. Knowing why someone voted a certain way has been missing in DAOs, and it’s often hard to understand why proposals pass or fail. Adding context helps people understand each other’s perspectives and helps communities make decisions reflect their shared values. Recording comments and building a “common law” is a meaningful advance in governance. This system can improve alignment across DAOs, make delegate standards explicit, and build an on-chain record of reasoning that organizations can point to over time. We’re excited to see how this helps organizations define and reinforce what they stand for in a way that’s accessible.

### Questions

1. Who has voting rights in this governance system?
2. Will the Yeeter project DAOs need to adopt this type of governance?
3. Are the precedents tied to a higher level organization?
4. How is jurisdiction defined within this framework?
5. Does an opinion need to be added before the vote, or is it submitted afterward to provide context?
6. Can votes be accompanied by multiple IPFS-linked opinions?
7. How does the abstain option affect quorum?
8. Are we combining the roles of judiciary and legislature within this framework?

## Next Steps

- [ ] Provide responses to the questions above
- [ ] Schedule a call with the team
- [ ] Organize scoping sprint to define milestones, timeline, and costs