---
# System prepended metadata

title: 2022-09-20 Hypercerts x RG re Scope and Budget

---

# 2022-09-20 Hypercerts x RG re Scope and Budget

This is in part a continuation of [Hypercerts x RG: Milestone 2 discussion](https://hackmd.io/oVs7_WQORdilu5ASK60nvQ)

## Features


### 1. Fractionalisation
#### Contract
* Fractional tokens -> implementing ERC3525
    * Refactor to 721, locally ready
    * Build 3525 contract + tests
    * Extend 721 with 3525
    * Adding name to cert
- [x] Create user stories in GH
- [ ] Create tasks in GH

#### App 
* View of own hypercerts
    * Add split and merge calls + UI
    * Burn (already there)
    * Graph metadata (fraction values per owner, burned)
    * Updating IPFS data
- [x] Create user stories in GH
- [ ] Create tasks in GH

### 2. SVG generation
#### Contract
* SVG generation
    * Add an SVG ID to cert
    * When calling for tokenURI build string/bytes/json, get SVG data from SVG contract
    * Randomness for color generation
#### App 
* SVG loading

<hr />

⬇️ Beyond agreed-upon scope of Milestone 2

### 3. Gallery page
#### App 
* View all certs 
* Manage collections
    * Collection admin in Google Sheets-API
* Update/replace owner with -possibly- ENS data

### 4. Detail page
#### App 
* SVG manipulation (take out details)
* IPFS data like description
* Contributor overview
* Owners overview


## Tangential Convo
* Linking from fractions to hypercerts
* Data model of hypercerts and their fractions
    * Each hypercert has a metadata object residing on IPFS
* The single use case for a user-invoked burn is "Hypercert minted erroneously / with outdated data". Under the hood, burning may also happen when splitting/merging hypercerts