Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

[Feature] Split / Merge Hypercert #31

Open
2 tasks
bitbeckers opened this issue Dec 2, 2022 · 0 comments
Open
2 tasks

[Feature] Split / Merge Hypercert #31

bitbeckers opened this issue Dec 2, 2022 · 0 comments
Labels
user story Defines a user interaction to be implemented

Comments

@bitbeckers
Copy link
Collaborator

bitbeckers commented Dec 2, 2022

Goal

Claim will be minted for a single user maintaining 100% ownership of the claim

User stories

  • As a user, I can use the app to split a hypercert consisting of a single fraction to a set of fractional hypercert (on value)
  • As a user, I can use the app to split the impact of a hypercert (fraction) to a set of fractional hypercert (on impact)

Technical

This is where the 1155 becomes SFT again. All tokens should have a supply of 1 (NFT) and a value dimension to represent the portion of claim (Fungify)

Split on impact claim

  • Hypercert has baseID = 1, ImpactScopeA and ImpactScopeB
  • Token11 and Token12 each representing 50% ownership
    *Now split Token11 into separate tokens for ImpactScopeA and ImpactScopeB => generate baseID {2, 3}

In metadata: Ref: token11

  • mints Token21

Value = 100% of baseID 2 (but represents 50% of baseId=1, impactScopeA)

  • mints Token31

In metadata: Ref: token11 (stored on IPFS)
Value = 100% of baseID 3(but represents 50% of baseID=1, impactScopeB)

@bitbeckers bitbeckers converted this from a draft issue Dec 2, 2022
@bitbeckers bitbeckers added the user story Defines a user interaction to be implemented label Dec 2, 2022
@ryscheng ryscheng changed the title [Feature] Split Hypercert [Feature] Split / Merge Hypercert Dec 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
user story Defines a user interaction to be implemented
Projects
Status: Refinement
Development

No branches or pull requests

1 participant