---
# System prepended metadata

title: 'Farcastle :: Raid Home UI'

---

# Farcastle :: Raid Home UI

Goal to outline web3 interaction using existing contracts/tooling. Can inform whitepaper solutioning and future build out of new contracts/factories.

![Screenshot from 2024-12-09 13-47-57](https://hackmd.io/_uploads/BJJJdCNEke.png)



## set up assumption

In existing infra, a Raid could be a single dao/yeeter shaman setup
- contracts launched in [yeet.haus ui](https://app.yeet.haus/#/launch)

Out of the box in yeet.haus the daos are setup with team members as share holders and contributors as loot holders, however there is flexibility at the contract level.

[launch params](#Launching)

### Raid Data
Raid title, description, raise/goal stats and proposal data are available out of the box attached the the dao/yeeter and indexed in related subgraphs.

### Raid Party
If using out of the box yeet.haus set up, Raid party can be displayed by looking at share holders. 

Open roles can be applied for using DAO share request proposals.
- NOTE: There isn't a current solution for role titles and open position data. We have a flexible dao database using the poster contracts + daohaus subgraphs that could be explored.

Hats could be explored here and maybe implemented without any new contract/data indexing needs? Have played with daos owning the hats tree and proposals for granting hats 

### Contribute/Yeet

Example yeeter
https://basescan.org/address/0xc313665721f79979b2884989308b52aa25744a99

address: yeeter shaman attached to the dao
function: `contributeEth`
value: amount contributing
args:
- message: string


### Proposals
Looks like membership, funding and signal proposals are displayed here. All can run through the raid dao.
- funding could payout individual roles/hats/members
- membership would give out shares/roles

### Revenue Split
We don't have much of a concept for this in out current setup. Some ideas:

1. If all profits are returned to the dao, then rage quit is used to distro, then we might be able to control those percentrages by balancing loot and shares for the team and funders. The Castle split can be controlled by giving that an address and allowing it to hold shares/loot as well.

2. If we want to skip rage quit and use some sort of oxsplit mechanism we could make a special proposal type that configures all the percentages to a team safe, the castle and when the proposal passes the execution will spin up the split contract and send the team/castle it's cuts. the remaining could stay in the dao where the loot holders/funders can then rage quit their 69%.


### Launching


**params on launching** - we default almost all of this in the yeeter ui
- dao 
    - name
    - loot token name/symbol
    - share token name/symbol
    - loot/share token transferability settings
    - voting perios length
    - grace period length
    - quroum % to pass proposals
    - proposal sponsor threshold (shares a proposer must hold for the proposal to not require member sponsorship)
    - eth offering required on a proposal submission
- yeeter campaign
    - startTime
    - endTime
    - isShares: does the contibutor get shares or loot
    - minTribute
    - multiplier: how much to multiply the eth contribution amount by for share/loot return
    - goal
    - feeRecipients and feeAmounts: list of recipients and the % amount of fees they get on each yeet - remaining is sent to the dao treasury

- metadata
    - see dao and campaign forms for these fields
        - https://admin.daohaus.club/#/molochv3/0x2105/0x2a48a2f2c9db54612dd1732b47c56467e44135f3/settings/update
        - https://app.yeet.haus/#/molochv3/0x2105/0x2a48a2f2c9db54612dd1732b47c56467e44135f3/update


### Resources

[Yeeter architecture](https://hackmd.io/YcJH2JFCRN-rFF3iKwrUeg)
[Moloch v3 contract docs](https://docs.daohaus.club/contracts)

**Contracts**
Factory Yeeter Higher Order Summoner contract to launch the following
- Moloch v3
- Single safe treasury
- Share erc20 membership/voting/treasury share token
- Loot erc20 membership/treasury share token
- Yeeter fundraising contract with admin permission on DAO
    - We can play with configuration of shares/loot for team and contributors

[Example yeeter campaign](https://app.yeet.haus/#/molochv3/0x2105/0x2a48a2f2c9db54612dd1732b47c56467e44135f3)
[Example DAO w/ links to related contracts](https://admin.daohaus.club/#/molochv3/0x2105/0x2a48a2f2c9db54612dd1732b47c56467e44135f3/settings)

**Data indexing**
This set up could use the [daohaus](https://docs.daohaus.club/subgraphs)/[yeeter](https://hackmd.io/YcJH2JFCRN-rFF3iKwrUeg#Subgraph-endpoints-and-explorer-urls) subgraphs

The [yeeter mvp app](https://hackmd.io/YcJH2JFCRN-rFF3iKwrUeg#MVP-Yeeter-App) has a lot of examples and reusable hooks for fetching campaign/dao data


