Hyperfiles Meta-Schema

EAS vs. Hyperfiles for Attestations

Hyperfiles are attestations. An attestation is a structured statement, or a claim, an opinion.
Each Hyperfile follows a generalized structure, and it’s contents are specified according to a user-defined schema.
Hyperfiles makes the assumption that attestation based claims are about something. This is practically implemented by creating corresponding reference objects to structured data objects.

	EAS	Hyperfiles
Schema Metadata (Name, Description, Context)	None by default. Requires using standard schemas deployed by EAS to “attest” to each metatdata field	Schema metadata fields are included in the schema type definition. Name is the object path & not required in metadata.
Private Data	Requires using special “privateData” schema to create Merkle Tree via ethers.js	TBD - goal is encryption by default
Generate Proofs for Content	Can hash on/offline and use their web tool to verify a hash	None yet
Indexed Attestations	On request	Always, via socialDB
Indexed Schemas	Always, via SchemaRegistry.sol	Always, via socialDB
Adapters for Import/Export	Need to create an entire frontend to integrate EAS w/ new sources	Publish data objects anywhere

Object Mutability (data and references)	None	Yes, can update or delete any data stored under user account
Attestation Revocability	Set by schema, immutable	Can be enable
Schema Field Types	Solidity primitives only	Any type (can import libraries from other users or define new ones)
Cross-chain Publish & Query	Deployed to multiple EVM chains, but each is fully independent.	Yes, and double-indexing will be implemented for references published off-NEAR.
Delegating Txn Cost	Yes, via EIP-712.	Yes, via relayer & meta-txns.