EAS as metadata

[bitbeckers]

By composing EAS and hypercerts we can tokenize all kinds of impact while increasing flexibility in the metadata schema. We could, for example, even explore splitting and merging over impact domains by burning a hypercert and creating two new ones with subsets of the attestations.

[bitbeckers]

From DMs added here for reference:

Moonshot:
I'd be open to hacking on hypercerts 1.5 where we specifically break open the metadata. We're shipping the evaluations MVP soon, which entails our own indexer and support for EAS schemas, so I think we could have a sidequest to explore how EAS schemas to build claim data could work.
We'd create schema version 1.5 and when that is detected we skip certain checks in the SDK. We'd build the minting flow in the easyRPGF app and would rely heavy in indexing EAS data.
It could be a claimData schema covering core hypercert traits and then LEGO it up to support different datasets.

[bitbeckers]

It should allow for splitting and merging claim data.

Ref: hypercerts-org/hypercerts#552