When adding files, we want to capture authorship details and associate them with the work with minimal friction. This is done by creating an onchain attestation using the schema below:
string title, // a short title
string metadataUri, // uri for additional metadata
address[] authors, // array of author addresses (ethereum)
bytes32[] contentHashes, // sha256 hash of each file
Notes:
Each file is stored offchain and may be public or private.
Limit the number of characters in the title to keep gas costs down.
The metadataUri (if provided) would refer to a JSON file stored offchain and could include description, "authorship types" and more, none of which really benefits from being directly onchain.
Overview
When adding files, we want to capture authorship details and associate them with the work with minimal friction. This is done by creating an onchain attestation using the schema below:
Notes:
title
to keep gas costs down.Schema Deployments
Requirements
Optional:
metadataUri
field. Details include: