Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TASK: Design Hyperboard minter #993

Closed
Tracked by #991
benedictvscriticus opened this issue Aug 23, 2023 · 1 comment · May be fixed by #1068
Closed
Tracked by #991

TASK: Design Hyperboard minter #993

benedictvscriticus opened this issue Aug 23, 2023 · 1 comment · May be fixed by #1068
Assignees
Labels
category:onchain Smart contracts

Comments

@benedictvscriticus
Copy link

No description provided.

@bitbeckers
Copy link
Contributor

With my current understanding, it's valuable to consider the ERC6551 standard for the hyperboard. A 6551 enables 721 tokens to hold assets like ERC 20, 721 or 1155 tokens. This enables us to mint a hyperboard that holds and controls hypercerts. This also makes these hypercerboard transferable and -in theory- a hyperboard can own a hyperboard (because a 721 holds a 721).

Admin flows of the hyperboard state could be assigned to a DAO, mulitisig or allowlist. Or the allowlist could be managed by a multisig.

I'm just leaving this thought here for future reference. But after FTC I think we should make a PoC out of this with the learnings we gathered up to that point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:onchain Smart contracts
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants