# Govrn + Ceramic Working Doc

[TOC]

### Context

Creating this document as a working doc for Govrn + Ceramic to work together on ideas, collab opps, and grant questions.

## Govrn Documentation
*Section of relevent Govrn Docs*

- [Link to Govrn Product Docs](https://govrn.gitbook.io/govrn-docs/overview/welcome-to-govrn)
- [Link to Protocol Research Paper](https://drive.google.com/file/d/1F4xgSOy7oGbQ1A-ccIh4c8N332h_6Mgi/view?usp=share_link)

## Cobranding Opportunities
There are three main cobranding areas we can dive into:
1. High Level Use Cases
- **tl;dr:**
- The combination of Ceramic to store data and Govrn to write data to that storage can enable some higher level use cases web3 constantly talks about.
- These topics are not just limited to Reputation, Identity, and DAOs, but include ideas such as Impact Evaluators, Hypercerts, and more.
- The idea would be to host lunch and learn series or write out use case documents on how builders could build any of these use cases using a combination of Govrn + Ceramic
- **Details:**
- While Ceramic specializes in storing non financial data, Govrn is both an oracle to bring online non financial data and a social graph protocol to connect the data. Our protocol is designed to be modular enough that you could build any of the higher level use cases with our base set of primitives (contributions, attestations, assignments, and groupings)
- Both our protocols upside value comes from these higher level use cases. By highlighting why these use cases are powerful, as well as providing templated instructions on the how to build them could help us both create working implmentations to point to.
3. Shared users
- tl;dr:
- Several users using Ceramic are also current Govrn users or upcoming users.
- Creating some user highlights would shed light on how people are using Govrn and Ceramic, as well as provide visibility to our communities.
- **Summary:**
- We could write blog posts and user highlights for customers that are using our joint products. By doing this, we not only expose both our protocols, but give press to users, who if in turn get more users from our highlights will then be using our protocols more.
- It's about creating a healthy ecosystem and ensuring our communities of users are remaining healthy as well.
1. Emergent Communities

## How Govrn would use ComposeDB
There are several ways Govrn has started to investigate how to use composeDB. This is supposed to be an introductory discovery and happy to start refining these more.

tl;dr of ideas:
- **Proposal 1:** Write contribution metadata to ceramic
- **Proposal 2:** Write contribution record to ceramic

1. **Gated Contributions Metadata**
- Summary:
- We've startd to explore the idea of how to "gate" or create an "access" system for contribution data based on memberships or tokens.
- Currenly all contribution data and metadata is public by default and is being stored on IPFS. While this has it's advantages, it also posses several downsides:
- The ability to have private data based on certain requirements
- Editability of the metadat
- The idea here would be to use ComposeDB to actually store the metadata associated with a contribution, giving users the ability to make "private" contributions or "gate" the information based on certain requirements.
- Considerations:
- Based on our developers previous work with composeDB, this use case looks to be the easiest one to start with and fits naturally into our the Govrn protocol already works.
2. **Writing contributions to Ceramic Natively:**
- Summary:
- The default protocol we've built works by writing the contribution record to Gnosis Chain and metadata to IPFS.
- This would enable users to write the actual contribution record to Ceramic instead of Gnosis.
- Considerations:
- These essentially takes what we write to Gnosis Chain and has us write it on ceramic.