---
# System prepended metadata

title: MVP for Yearn v2 Subgraph

---

# MVP for Yearn v2 Subgraph

## Agenda for meeting 13/01/21

Registry address:

https://etherscan.io/address/0xe15461b18ee31b7379019dc523231c57d1cbc18c

- Timelines
    - Key dependent is the x48 API
    - MVP release in roughly 1 week would be ideal (targeting 20 jan)
- MVP scope [https://hackmd.io/IzcimaawRx-R3BIGGUYYfg](https://hackmd.io/IzcimaawRx-R3BIGGUYYfg)
    - Primary customer is x48, seek validation of scope with him
    - Project management
- Schema
    - Comment out schema that isn't implemented with mappings
        - PRs to implement should uncomment schema and include mappings to populate fields
    - Most-MVP blobs of work
        - Aggregated Data Entities
            - "Root" entities -> deltas
            - Aggregated Entities -> cumulative (or the other way around? deltas in aggregate)
            - Which aggregations make sense?
            - Outcome:
                - remove aggregate data entities until we have finalsiation of which aggregates make sense for each field (https://docs.google.com/spreadsheets/d/1V7r8kRAWTwJm9oR-EOK6biukU42XyZqJMSOxxZ7Dsg0/edit#gid=0)
                - update <>Update (timeseries data) entities to use action values rather than aggregates (!)
        - VaultRelease/Vault lifecycle / registry pipeline
            - Outcomes:
                - Not a priority for MVP
- Mappings
- Timelines/objectives recap


## MVP scope

Critical:
- [ ] list all vaults
- [ ] list all active strategies attached to vault
- [ ] list deposit/withdraws/balances


Nice to Have
- [ ] earnings

ToDos after release:
- [ ] harvest reports
- [ ] aggregate data
- [ ] ??


## Note:
Main goal is to estimate effort left and ETA for having a subgraph deployed for v2 release

Rest of features in schema can be added as issues and track for future grapgh API release to iterate on
