V3 Design Review

--- title: V3 Design Review tags: design --- # DAOhaus Design Review for V3 > Notes from Design Sync: > * Focus for Ven shifted towards pitch deck, Adrienne & Helle preparing for presentation for Camp Fire > * Continued work on Vaults > Notes from Design x Dev Sync 20-01 > **Groupings & DAO Relationships** > * Socially-defined vs formal (on-chain) relationships between DAOs. Social relationships between DAOs (i.e. DAO friends) will not be supported in the app > * We will not adopt new technologies that are in flux for now, such as Ceramic's DAO DID (to store DAO metadata) or MetaGov DAO URI (which points to canonical metadata for Subgraphs) > > What is a formal on-chain relationship? > * A DAO's membership in another DAO > * 2 Minions can control 1 Safe > * DAOs another DAO's tokens (but there are no tokens required for Moloch DAOs) > * On-chain transactions between 2 DAOs > > Dev Discussion > * Devs are in early stages of evaluation of component libraries. Dev & Design to sync once design is finalizing the UI, style guides, etc. > * Health-check page to show statuses / errors of DAOhaus services > * How can the UI surface scenarios where a proposal is modifying the Baal contract (e.g. Shamans / Token transferrability) but looks random on the frontend? Solution: Warning messages when these proposals are detected > * Do we need to build UberHaus UI in V3? No, it'll be separate > UberHaus delegation. Warcamp DAO owns shares of UberHaus DAO and calls delegate function on UberHaus DAO contract & pass address of delegatee as parameter > Notes from Design Standup 18-01 > * Main focus on Hub. > * Pinning & Grouping: Pinning primarily happens in the Hub, secondary feature in the search. Need to sort out grouping x pinning > * DAO Overview: New Members' information module (controlled in Settings) + Recent Activity section in the bottom > * Vaults: Lots of things to work on here > * Boosts/Shamans: Add Custom Boost button + Shamans Reduced to a Type of Boost > > Open items: > * Network errors - how can we show it? is this technically feasible? Maybe a network/app status page > ## Summoning - Templates are gone & converted into 1 configurable summoning flow. Users can see all settings & edit / summon where relevant. - Shares are non-transferable by default, but summoners can choose to use a customized DAO token - Summoners can change proposal timing (Baal feature) - Summoners can view/edit Starting Members via list or table view - [ ] **Feature to replicate a DAO's settings is coming soon (perhaps a Clone button when a user is exploring a DAO's page)** - [ ] Should we add more visiblity on Boosts during summoning (e.g. 'This is your first Boost' for Shamans) ## Hub/Dashboard (DAOhaus Profile) There are 2 main views: **Your View** (dashboard for all your DAOs & proposals) & **Others' view of your profile** (simpler version only with DAOs you joined). In your view, there are 4 main sections: 1. DAOs: List view of all your DAOs, showing vaults, interactions (30D changes), members, proposals (30D changes), delegates (options to add delegates) - [ ] **A DAO member can delegate to any address, so the dashboard (DAO section) should show a view for delegated DAOs (even if you're not a member)** - [ ] **Any way to control visibility of DAOs (e.g. hide/mute/highlight certain DAOs)?** 3. Proposals: List of new Proposal cards - Proposals are aggregated & shuffled across all DAOs. There are filters though (e.g. default view is for proposals with your address attached to it) 5. Badges (Coming soon) 6. Attestations (Coming soon) ## Navbar This should be consistent across all DAOhaus pages. DAO search is now a dropdown search bar. Search results (i.e. DAO names) can be pinned & results should indicate whether you're a member (Colored border around DAO profile picture). Search results can be sorted to prioritise DAOs you're a part of. Shares prioritisation could be unmeaningful as shares assigned are arbitrary. - [ ] Tech: Search has to be done on the backend to retrieve a mix of data from subgraph & DAO metadata - [ ] Next iteration: Search results can be based on DAO relationships (i.e. how different sub-DAOs are related to each other), so we show the main DAO for sub-DAOs that are linked together. - Should this grouping be done by users individually or something that is configured and lives across all DAOs? ## DAOs ### Overview The new DAO page has horizontal sub-navs. Current progress on V3 (Baal) and will be stripped down to non-Baal view. Overview shows About, Proposals, Members & Vaults. These cards in the Overview page can be customiseable via Boosts. - [ ] More to come on user profile & status in DAOs . ### Proposals Mostly looks the same with redesigned Propped cards. There are new filter buttons (including Spam Filter) ### Vaults The charts section is more robust now, with different views based on vaults / tokens / total value. Each Minion Vault can have tags e.g. "Protected" (non-Ragequittable) & "Early Execution", "Linked". - [ ] Add NFTs into the Vaults - [ ] We could explore a Vaults page with less emphasis on charts. Perhaps charts are a Boost? - [ ] Are there other valuable information about the Safe Minions? ### Members Members page starts with a simple chart and stats on Members. Members are listed in a card view with Shares, Loots, Delegated, Engagement (how many % of proposals do members vote? Makes Abstain important). - [ ] Delegates: You cannot delegate to multiple addresses - [x] Contract question @spengrah @Dekan **Can you only delegate 100%/0 shares or some shares too?** It is all or nothing - [ ] Engagement is good to have, but might not need to be on by default ### Member Page This page shows more details on a member's Membership Details, Delegated Shares & Membership NFTs (if any). Bottom section will include Recent Activity ### Settings Mostly includes the Baal settings. When user clicks 'Edit', user will need to sign or submit a transaction and the last step would be to submit Proposal. There will only be 1 Membership NFT and it can be customized by the DAO (separate contract from Baal). Membership NFTs will live in the Member's wallet. Sections include: 1. General Settings 2. DAO Metadata 3. DAO token (includes Token Name, Symbol, Transferrability & Current Supply.) - [ ] We need to take out Icon for now (not in the contract) - [ ] @spengrah @Dekan Contract question: **Can token name be changed after deployment/summoning**? 4. Shamans - [ ] Shamans will have a name & type. Shamans can be removed - [ ] Shamans could be combined with Boosts 5. DAO Appearance: Simplified color section with minor edits rather than being super-customisable 6. Installed Boosts 7. Service DAO Settings ## Other Discussion **Decentralisation** Storing these individual preferences for DAO groupings might require a slightly more centralised way to manage state in a performant way. (TBD on Ceramic) We aim to move towards decentralization as much as possible, but we might need to make certain trade-offs. A middleground could be having 2 versions of the app (1 that's super-decentralized, and another that has better UX & features but with more centralization). Stateless centralised calls with stateful decentralised storage is the model we'd like to go with **Same App? Different App?** If all apps are different apps, it'll be good to have a standard Navbar for people to create new apps. **Abstain** - [ ] @spengrah @Dekan Should Abstain be included in Baal? ## Next Steps: Meeting on Thursday