---
# System prepended metadata

title: Hypercerts Technical Planning

---

Hypercerts Technical Planning
===


:::info
- **Date:** Nov 21, 2022
- **Participants:**
    - Holke
    - Ken
    - davidad
    - Raymond
    - Jason
    - Carl
- **Agenda**
    1. Intros `5 min`
    2. Agreeing on the objective `5 min`
    3. Requirements discussion `40 min`
    4. Action items `10 min`
- **References**
    - Off-chain hypercerts and their tradeoffs [[new doc](https://docs.google.com/document/d/1AtrEIhwQK8ww3XcBJOLKMxGXcqkicHUBdm2tjlKbvws/edit?usp=sharing)]
    - Hypercerts [protocol repo](https://github.com/Network-Goods/hypercerts-protocol)
    - Hypercerts [minting app](https://pilot.hypercerts.xyz/)
    - Obsidian [design specs](https://docs.google.com/document/d/1PvImHmWe8v_F4SWwIdkKpb5xYDThScH_/edit?usp=sharing&ouid=108465674412661376195&rtpof=true&sd=true) and [implementation plan](https://docs.google.com/document/d/15I_2lD7nu6DywyFsdjP0HAideEM5UZl3vVCrIthoh4c/edit?usp=sharing) [all docs [here](https://drive.google.com/drive/folders/17Yo84_IEKhK3ubbeoCFgnK-MHUaRajQP?usp=share_link)]

:::

## :wave: Intros

## :dart: Agreeing on the objective
- **Objective: Grow protocol adoption**
    - Q4 | Launch the hypercert protocol on first EVM chain (v0)
    - Q4 | Draft EIP standard for hypercerts; establish working group to steward EIP
     
What do we want to focus today's session on? Carl's assumption is we want to focus on how to launch the protocol on an EVM chain. If so, then continue.

Goal is to launch something that we want to stand by and be the first "permanent" use case of hypercerts. We are willing to take responsibility for data migration.

As long as contract doesn't need to hold funds, it doesn't need to be audited.



## :mag: Requirements discussion

- What use case(s) do we want to prioritize now?
    - Existing web3 communities who just need an (audited) smart contract and will bring the rest (eg, Gitcoin, Longevity Prize)
    - Crypto networks with clearly-defined impact needs but no tooling (eg, IPFS, Optimism, Celo)
    - Funders who may be less web3-savvy but want to fund things retrospectively (eg, more traditional donors)
- What do we think is most important to those users?
    - Which chain? 
    - Gas costs?
    - ERC-3525 (semi fungible) or 1155 (multi) token standard?
    - Any functions users can't do right now?
- Impact NFTs vs IP NFTs vs hypercerts
- What needs to be on-chain in the v0? What can be off-chain?
---
==Importance== (5 = must-have, 3 = should-have, 1 = could-have)
### Smart contracts:
Current contracts: Minter, Metadata and SVGGenerator
- ==3== Upgradeability. We expect the first version to be

### Pilot app:
- ==3== x

### Docs:
- ==3== x

### Other:
- ==3== x

---
## :heavy_check_mark: Action items
- [ ]  Ray, Ken, Jason - work on design doc, using Gitcoin and Longevity Prize as initial use cases for 'onchain-minus-checks' (ingestion from multiple chains in a consistent and linearalizeable way, state machine for accepts/rejects/updates to the state)

## Notes / parking lot
- Technical debt: cleanup method and variables, optimising inheritance and local variable usage, among others
- Donation flow, really talk it through including state changes and impacts
- Roles/right adding background & colours. Who has rights? Or anyone? Also impacts SVG generation
- Updating/freezing metadata? Who has rights?
- Gnosis safe integration