---
# System prepended metadata

title: v3 Blacksmiths Show & Tell
tags: [' show and tell', ' blacksmiths', v3]

---

---
tags: v3, blacksmiths, show and tell
---

# v3 Blacksmiths Show & Tell

## DAO Database Spec

- Using Poster to manage schemas on our subgraph for record entitities for any bits of data
- Allows DAOs to own metadata and can validate/ensure that permissions are what the DAO wants
    - Needs to be updated by Baal
- Transactional

### Poster contract 

`content`
- Can start defining our schemas for different table types
- Where should we publish our schemas as we define them?
    - For us to know the standards and the schemas
    - Publish schemas similar to Cearmic ([JSON Schema](https://json-schema.org/))
    - Look to handle our parsing once we get the data back
    - Can also use this in the SDK and give the users parsed data
    - Would this be done at the Subgraph level or at a higher level?
    - SDK could do the parsing

`tag`
- Poster is used wherever, so the tags will help us ignore posts that aren't relevant, and also tell us about how we want to parse and validate
- `daohaus.shares.daoProfile`
    - first is the DAO, second is the permission, third is the target table
- So far, single entity type called `Record`
- `contentType` can help with decoding since we can tell if its json, ipfs, etc.
- There will then be a record -- if someone updates we'd have the new id
- Can order by ascending and display 1 will show the latest update to the DAO record
- Shows who updated it last
    - Could have a changelog and run a diff on the frontend

### Validation

- Checks if event is a tag we care about (so we don't listen to events we don't care about)
- Check the content to make sure that it is json -- if not it's ignored
- Can then add conditionals to parse the content

### Future

- In the future our forms will send the data
    - Will require frontend to be sure to not make destructive updates as a blob
- Each entry has a unique id

## Summon


