Manifold Studio Video Walkthrough
This series is ideal to users getting started with Manifold and learning about the different elements of minting a token. If you're looking to create an Open Edition, once you've deployed your contract to Mainnet head over to the Claim Page app.
Manifold 101 will do a complete walkthrough of Manifold Studio. It will guide creators through the deployment of a test contract, all the way to minting on mainnet. There will be a series of explanations and introductions to concepts like contract types and reviewing your contract on Etherscan.
Learning to navigate Manifold Studio
What are the different elements to deploying your own soverign smart contract?
This smart contract is owned by you and is important to note that Manifold Studio is completely stateless and doesn't have any ownership or takes any cut out of your contract. What does that mean? If Manifold Studio disappears you will still be the owner of your contract and will be able to do anything that you want with it!
The contract name is the main identifier for your contract and will appear anywhere your contract is mentioned. This is usually your artist name, brand, or identity. This field accepts alpha numeric characters and spaces and can be any length. We recommend less than 15 characters, however this is not a hard requirement.
Check out some Manifold contracts to get a flavor of the types of ASCII art creators have deployed. FVCKRENDER and Mad Dog Jones have some awesome examples. There's also plenty of tools out there for generating your own from images or design.
Ideally, ASCII art used here should be less than 120 characters in width. Something like 150 characters is acceptable, but the more columns you add, the more you risk text wrapping when viewing your contract on certain displays. There is no limit to ASCII art height. Take note that a boarder and padding will be automatically generated when compiling your smart contract.
The ASCII art is a signature detail of the Manifold Creator contract. ASCII art is used to visually identify your contract, and plus it just looks really cool. Take the time to pick some ASCII art that is meaningful and represents your work, identity, and creativity.
Understanding the elements of a contract on Etherscan
The ERC-721 is the standard for minting 1 of 1s. In other words this standard will allow you to mint tokens that are unique and can have different value than another token from the same smart contract due to age, rarity, other properties, or simply the visual difference of the artwork.
When it comes to editions, tokens will be numbered and marked with the corresponding number of that edition e.g a collector can own the token number 3 of 20 editions.
ERC-721 Editions show up as different numbered tokens on OpenSea.
The ERC-1155 is a dual purpose fungible and non fungible token standard. While you can mint fungible NFTs under the ERC-1155 standard, the most common use cases include applications like in-game items or multiple editions of the exact same artwork or photography, situations where minting and managing bulk fungible items can save time and gas.
Editions in this standard are not numbered. If you mint 10 editions of the same token on a ERC-1155 contract, these will show on OpenSea as one token that has 10 copies.
Clarification: The video mentions deleting testnet tokens before going to mainnet. This is only if you are looking to edit any details of the contract and looking to redeploy the contract. If the contract and token are to your liking, you can go ahead and deploy to the mainnet.
Testnet tokens do not have to be deleted.