What are the acceptable formats for form fields on the Creators Self Service Portal?

Support
Support
  • Updated

This article's contents are an excerpt from our more complete tutorial, How to Use the Creators Self Service Portal. We recommend reading this article in its entirety before deploying your collection.

 

Below are each form field or asset type and the format required for this asset:

Form Field/Asset Description and Requirements Format Required Modifiable After Deploy
Collection Name The name of the collection, also converted into the contract name by replacing spaces with hyphens (i.e. "Bitcoin NFT" becomes "bitcoin-nft" contract name. Alphanumeric No
Collection Description The description placed alongside your collection if approved to mint on gamma.io. While this value can be modified on our user interface, it will be permanently tied to your NFT metadata. Alphanumeric No
Mint Price (STX) The price in STX that will be paid by users to mint one NFT in your collection. Integer Yes
Email Address An email address used for our ticketing system so we may contact you regarding your collection. This will never be shared publicly and will not be associated with your smart contract. Valid Email Address Yes

Artist Address

Optional

An optional STX wallet address used for mint and royalty payouts. If not entered, this will default to the address you used to login to the portal.  Valid STX Address Yes

Domain Name

Optional

An optional URL you would like to use for promotional purposes such as your Twitter profile or collection website. If not entered, this will default to your Gamma profile (i.e. gamma.io/wallet-address). While this value can be modified on our user interface, it will be permanently tied to your NFT metadata. Valid URL No
NFT Assets The files that serve as the payload of your NFT. In other words, the image, video, rendering, or audio that serve as the face of your NFT card. JPEG, GIF, PNG, APNG, BMP, SVG, MP4, WEBM, OGG No

Use File Names

Optional

Checkbox that will replace a default token name with the name of each file. The default nomenclature is "Collection Name #" but can be replaced with anything custom by customizing the name of the file and then enabling this checkbox. For example, if the first file name in your collection is "XYZ.png" and your collection name is "My Collection", if enabled, your first token will be named "XYZ", and if disabled, your first token will be named "My Collection #1" Not applicable No

Include Additional Claim Functions

Optional, Recommended

Checkbox that will add additional functions for users to mint more than one NFT with a single transaction. The total amount paid will still be relative to the number minted, but users will be able to mint more than one NFT using a single transaction. If selected, you'll then need to check additional boxes for each of the functions you'd like to include (e.g. Claim 3, Claim 5, Claim 10, Claim 25) Not applicable No

Include Non-Custodial Marketplace Functions

Optional, Recommended

Checkbox that will add non-custodial marketplace support. This is a forward-compatibility function for an upcoming standard, but it will not be used on Gamma immediately following deployment. Once we fully support this standard, enabling this function will allow users' NFTs to not be transferred to the marketplace contract's custody while listed on the market. In other words, when users list their NFT, it will remain in their own wallet until sold. Not applicable No

Include Attributes

Optional, Recommended

Optional field that allows you to add a CSV file that includes a list of descriptive traits for each of your assets. Your CSV must be formatted so that each row represents a token ID and each column represents an attribute value.

Link to Detailed Instructions Article

No

Enable Mintpass

Optional

Optional field that allows you to add a CSV file that includes a list of STX wallet addresses and numbers of pre-mints allowed per wallet address. Your CSV must be formatted so that each row includes a single wallet address and an integer representing the number of mints allowed for that address. If enabled, no mints may occur until you first initiate mintpass sale as a contract function call. Following this step, you'll need to initiate public sale as a second contract function call before users not listed on your mintpass may mint an NFT from your collection. If users try to mint before mintpass is enabled, or if users not listed on your mintpass try to mint before public sale, these transactions will always fail. Link to Detailed Instructions Article No

Enable Minting with Alternate Currency (e.g. MIA)

Optional, Multiple Selections Available

Checkbox that enables buyers to mint NFTs using alternate currencies, for example, CityCoins. If selected, you must enter a number of this currency's tokens charged to mint one NFT. If selected, users will still be able to mint using STX at the previously defined mint price in STX. Integer

No*

*Mint price may be modified but functions cannot be changed.



Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.