Minting a Token
Minting your own tokens
To create an NFT you need to have a contract deployed to either mainnet or Goerli. Start minting your first tokens by selecting the contract you wish to mint a token to.
As with contracts, tokens can be deployed to Goerli first. This allows you to test out how tokens will look in different marketplaces such as OpenSea and Rarible before minting to mainnet.
Manifold Studio provides support for several filetypes, customization through properties, editions, collections and much more.
In this section we will explain all you can do when minting tokens through Manifold Studio.

Contents

1. Supported File Types

Manifold Studio allows you to mint all kinds of file types.
File
Format
Comments
Images
.png, .jpeg, .jpg, .gif, .tif, .tiff, .raw, .svg
Video
.mp4, .mov*
As some marketplaces do not display .mov/H.265 we recommend videos be in mp4 format.
Audio
.mp3, .wav, .flac, .acc
3D Models
.glb
HTML Pages
.html
Check our tutorial on how to mint HTML pages

2. File limits

When minting through Manifold Studio there is a size limit of 200MB. If your files are heavier than that simply fill in this form.
Take into consideration that other platforms such as OpenSea, Rarible, Zora, etc. might have their own file size limits when showing your tokens, so while you can mint a token that has a size of 3GB, the consumption experience of that token might be broken since the file is too heavy to load.

3. Storage

When minting through Manifold Studio, all your assets and metadata are stored on Arweave.
Arweave is a decentralized storage similar to IPFS with the difference that Arweave ensures your files are stored permanently. Currently, Manifold Studio assumes the cost of uploading files to Arweave.
Manifold Studio assumes the cost of uploading files to Arweave
Note that while your files are uploading to Arweave, Manifold Studio will upload all files to Cloudinary as a staging step so they are available right away.

4. Properties

Properties are additional storytelling to your NFTs.
Properties have both a Property Name and a Property Value. For example, if you wanted to add the year when your picture was taken you could create a property with name "Year" and value "1993", same with any other characteristic you would like to be reflected as metadata on your NFT.
Properties can be of different types, such as text, number, boost number or hidden. These types are rendered differently on marketplaces like OpenSea and Rarible.
Jordan Inglee for instance uses NFT properties to enrich his photography NFTs
Boost Number and Boost Percent are a type of properties that are rendered as completion circles inside OpenSea. They are usually used for gaming NFTs such as character health or magic power.
Not sure how your properties will look on Opensea? Try it out by deploying to Goerli so you can ensure all your metadata looks just the way you want before deploying to mainnet.
The Hidden property value is a fun one. Here you can set metadata that won't show up in Opensea or Rarible, and is only accessible if your collectors examine the raw metadata of the NFT. For instance you could add a hidden property with a link to an easter egg such as a unique video or image.
To find these hidden properties you can simply follow these steps:
  1. 1.
    Head over to your contract on Etherscan.
  2. 2.
    Click on the Contract tab where you can see the code and ASCII art of your contract.
  3. 3.
    Click on "Read as Proxy" where you will be able to see all functions that allow you to inspect your contract.
  4. 4.
    Go to a function called "tokenURI".
  5. 5.
    Click on it a query it with the token number you want to see the hidden field from. It will return a link.
  6. 6.
    Navigate to the link and there you will see your hidden property!
Hidden properties are also used for minting HTML pages.

5. Creating a Collection

There are two ways to create collections:
  1. 1.
    Having one contract per collection.
  2. 2.
    Specifying the collection the NFT belongs to in its properties.
At Manifold we strongly recommend the second approach. Our point of view is that provenance is key for an artist and having one contract per collection makes provenance challenging since you need to track all the contracts that belong to a single artist. This would be equivalent to having multiple Twitter profile accounts for a single artist.
Collections can be defined within the properties of your NFT by adding a property with name "Collection" and value with the name of the collection e.g "Genesis Project". The property name is not restricted to "Collection", it could be anything you want really, like "Album" for example.
OpenSea has one way of rendering collections in their platform right now which is 1 "collection" = 1 contract. If you would have all collections in one contract the only way to figure out the floor for each collection would be by using OpenSea's filters (e.g you'd filter by property "Collection" = "Genesis").
We are in chats with the different marketplaces to see how we could render collections in a different way similar to how Art Blocks show up (https://opensea.io/collection/art-blocks), again making emphasis on provenance being key (you always know this piece is an original because it is minted on the creator's contract).

6. Editions

After the token metadata has been created, Manifold Studio allows multi editions for the ERC-721 and ERC-1155 contracts.
For ERC-721 contracts editions will have their own unique number, for example, an edition of 25 will be numbered “Title #1/25”.
For ERC-1155 contracts, editions will be unnumbered, so collectors don't know the exact token they own, but they know they own one token from 25 that exist. Typically this would be displayed as a single image with multiple copies.
Copy link
On this page
Contents
1. Supported File Types
2. File limits
3. Storage
4. Properties
5. Creating a Collection
6. Editions