---
# System prepended metadata

title: Moloch Pack Working Notes
tags: [' Product', v3]

---

---
tags: v3, Product
---

# Moloch Pack Working Notes


## Hooks

Optional context comes with the hooks
- allows to load dao id and chain outside of params
- stores filters and sort order
- any list hooks need to follow the proposals

### Next steps

- sam to do members



## Design Considerations

- Getting daoid and daochain. Single DAO app use constant variables. Multi-DAO apps use the URL. We need a solution that satisfies both constraints.  
    - [ ] Try adding daoid and daochain to connect? 
    - [ ] DAOChain and DAOId as props? 
    - [x] Connect with optional props as alternative? 

~~*I added daoChain and daoId to props of connect. It's non-breaking. ~~
*I created a new Context that exists within 

- Remove unnecessary friction by replacing all ValidNetwork and EthereumAddress types with string. 
 - new ticket



## Macros

1. review admin app to define component scope
    - any other macros from dao apps we've built?

2. start to define apis
    - where do we use hooks vs. prop drilling
    - cannont rely on router/params or context

#### Proposal list

- can define new proposal types
- can pre seed with a filter? limit
    - pass desired filters in for filter list
- search

![](https://i.imgur.com/N1oINGd.png)


#### Proposal card
- details + action
- custom proposal type

![](https://i.imgur.com/cmTwZ2v.png)


stretch:
- expanded details section (from prop details page)
- pass in a face plate


### Proposal action data

![](https://i.imgur.com/3VRM1xg.png)


### Proposal history

![](https://i.imgur.com/pLXMTEz.png)


### Vault card
- pass menu items prop

![](https://i.imgur.com/LFG9xvI.png)


### Members list
- can we configure the columns
    - types hell
- or do we need to hard code for now
- upgrade to tan table?
- delegate modal can come over
- pass in action panel - where you can send a link to a form in your app

![](https://i.imgur.com/nNweb7h.png)



### STRETCH: Member detail page/rage quit




### Future
- look into storing forms in the hooks context
    - might want its own store
- ties into static data planning
    - target dao finds proposal data in ifps by hash
    - proposal lego is a single ipfs hash