This repository was archived by the owner on Feb 5, 2025. It is now read-only.
This repository was archived by the owner on Feb 5, 2025. It is now read-only.
EAS as Hypercerts Metadata #1257
Description
Describe the feature you'd like to request
Right now we have a hard-coded Hypercerts metadata. However, this leaves a lot to be desired because different use cases might have different refinements of the schema (e.g. a specific impact schema).
It'd be nice to be able to use any EAS attestation as the metadata of a hypercert. In other words, we can tokenize any attestation, with the current Hypercert metadata as a default fallback if EAS doesn't exist on some network.
Describe the solution you'd like
- Create an EAS schema with the current Hypercert metadata schema
- Give users the ability to fork that schema and make additions
- Provide some utility to check whether the resulting metadata "conforms". If it's too divergent, it makes it difficult for us to build the UX features we want.
- Update the contracts to be able to point to an attestation as the metadata, either on-chain or off-chain.
- Update the SDK to be able to fetch the metadata from all of these different options.
Describe alternatives you've considered
To be discussed!