You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Records in the provenance metadata module are created around the assumption of an off-chain data store that holds the record information. In non-Figure use cases there are typically three different scenarios; directly on chain data, off-chain data referenced by URI+HASH, and off-chain object storage. Our record feature should be extended to support these other two common use cases.
Problem Definition
Not all users follow the object store approach used by Figure for NFT records. In order to better match other use cases such as the simplified ERC721 model the metadata record objects should be extended with support for the other two [more] common use cases of on-chain data and off-chain at URI location with an on-chain hash.
Proposal
Expand the record input and record output structures to include support for URI locations and (limited) inline data.
Summary
Records in the provenance metadata module are created around the assumption of an off-chain data store that holds the record information. In non-Figure use cases there are typically three different scenarios; directly on chain data, off-chain data referenced by URI+HASH, and off-chain object storage. Our record feature should be extended to support these other two common use cases.
Problem Definition
Not all users follow the object store approach used by Figure for NFT records. In order to better match other use cases such as the simplified ERC721 model the metadata record objects should be extended with support for the other two [more] common use cases of on-chain data and off-chain at URI location with an on-chain hash.
Proposal
Expand the record input and record output structures to include support for URI locations and (limited) inline data.
For Admin Use
The text was updated successfully, but these errors were encountered: