---
# System prepended metadata

title: Keating <> Sam <> JP Sync (4/5/22)
tags: [' sdk', ' ops', v3]

---

---
tags: v3, sdk, ops
---

# Keating <> Sam <> JP Sync (4/5/22)

## SDK

- Keating willing to help with the SDK
    - Further behind from where the component library is, but a goal is for us to have a spec doc by end of week
- Sam spending some time Raging this week in relation to `nx` package setup (and what goes where)
    - Defining what goes where (commons, utilities, etc) and what should be in the SDK (thinking this would be data fetching)
    - Thinking about imports/exports for the packages generally and folder structure
- Looking at Rages like Summon and Hub and see how these interact with data can inform usecases for the libraries
    - Go through what's going on here and look into the querying (proscribed queries vs. query builder type things -- similar to an ORM)
    - Evaluate the pros and cons of this
    - Query Options: https://github.com/superfluid-finance/protocol-monorepo/blob/dev/packages/sdk-core/src/Query.ts

## Ops

- Goal to wrap up moving things into the monorepo (Subgraph & Contracts) and then can jump into the SDK
- Getting familiar with Subgraph development and transforming this into different commands that can be run from `nx` that match the `serve`, `build`, `deploy`, `lint` etc.
- Contracts and git history
    - We need to do more research here to see if the the git history is preserved when moving this into the monorepo
    - Check out git submodules
    - If we *can* keep it that would be good, but this may not be completely necessary
    - We only need to include DAOhaus specific things in the `contracts` package, and the Baal contract can potentially be an `npm` package
    - A few options depending on what we want
- Document along the way! 
    - Especially for Rage 

## DAOStar

- High-level goal is to create a DAO standard (they're working to get this accepted as an official EIP)
    - DeepDAO has no standard for finding member and proposal data for Moloch, Zodiac, and Compound DAOs
    - Provide contract interface that returns a URI -> other protocols can then find data for different types of DAOs
    - This would be super helpful for the MetaOS (when we want to bring in other DAO data into the DAOhaus app)
    - Two Pieces: Open Standard and protocol-specific implementations 
- Has some dependencies related to our version of the Baal contract
- May want to take this into consideration as we're leading into the audit
- Subgraph:
    - Fork of the Subgraph that Sam is working on bringing in a structure for us to consume
- Ceramic docs that point to this subgraph and specific schemas that conform to DAO standards (proposals and standards)
- Not as clear what's going on with the contract, but Keating, Isaac, and Sam are syncing tomorrow
- On the DAOhaus side the contract changes are the higher priority changes
- Worth having a ticket or milestone related to this
    - Update contracts after DAOstart implementation is complete
    - Keep synced on this when working on the Subgraph
        - Content URI field based on the DAOStar spec
        - Keating will be focusing on this today and potentially by tomorrow (before or after the sync) and can meet up with Sam to review progress

## Action Items

- [ ] Sam continuing to Rage this week on the SDK, evaluating pros and cons of different approaches
- [ ] SDK Spec Doc (similar to component library doc)
- [ ] Create cards representing DAOStar work
- [x] Create card for Contracts package research (researching about preserving git history via sub modules)
- [ ] Sam and Keating to sync up about DAOStar related subgraph changes after Keating and Isaac meet on 4/6
