Metadata and OpenSea compatibility

Page.NFT stores data in a format fully compatible with OpenSea and many other crypto projects for trading and managing NFT tokens, as described in OpenSea metadata standards.

It should be noted that the Page.NFT token stores a link to the IPFS content of the token itself, while the link to metadata is formed in midair when the corresponding method is called and it points at the Crypto.Page service which dynamically generates metadata.

This service is an open source public service and it dynamically generates metadata exclusively from blockchain data. The following data is contained in the metadata:

  • Link to the content of the post

  • Attributes of the post (traits) in the form of:

    • The author of the post (address)

    • The number of comments to the post (number)

    • The number of likes to the post (number)

    • The number of dislikes to the post (number)

    • Post categories (string line)

    • Post hashtags (array of text strings)

    • Information about the name of the community, the owner of the post, if the post belongs to the community

These attributes will allow users to navigate the posts, compare them with each other and determine the parameters of the rarity of the post, in the same way as it is done for many other NFT tokens.

This approach is chosen in order to be able to provide mutable metadata (for example, the number of likes), while keeping the link to the content unchanged. Page.DAO may decide to commit metadata for all Page.NFT tokens or for some part of them and upload metadata to IPFS for them.

Last updated