Essentials
Welcome to fxhash
Web3 Fundamentals
The fxhash Ecosystem
Getting Started
Artist Guides
Project Setup and Artist Tools
The fx(hash) API
Generative Art with fx(params)
Browser Based Generative Art
Releasing your Project
This is an overview of the fxhash minting interface and a walkthrough of the minting process.
The minting interface is the portal that takes you through the necessary steps to upload your project to fxhash. The interface will guide you through some final checks to make sure that things are working properly, help you set up the appearance of the final project page on fxhash and allow you to set distribution options such as the edition size, pricing, royalties, reserves and allow lists.
Once you’ve made sure that your token works properly and created a zip file that contains all of your project files (either created through the fxhash CLI or by manually adding your files to an archive), then you’re ready to get started!
<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/a3295794-cd95-4ae1-b59f-975456aac3c3/fx_doc-icon_info_001.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/a3295794-cd95-4ae1-b59f-975456aac3c3/fx_doc-icon_info_001.png" width="40px" /> The minting interface can be accessed from the drop down menu that expands from your profile button in the top right corner by clicking on the mint generative token option.
</aside>
The first step in the minting process is selecting which blockchain you want to mint your project on, you can choose between Ethereum, Base (Ethereum L2), and Tezos:
Next you’ll be asked whether your project is an individual original work, or if it is a collaboration with one or more other artists:
For the purpose of this walkthrough we’ll assume that you are the sole author. The subsequent steps don’t actually vary much when a project is a collaborative one, you simply need to create a collaboration contract beforehand and then indicate the contract during this step. You can learn more about collaborations and collab contracts here:
Next you’ll be asked how you’d like your project to be stored - either on IPFS or On-chain:
You can read more about the differences between IPFS and On-chain storage here:
Decentralised Storage: IPFS and ONCHFS
Upload your project's .zip file that contains all of your project files. This zip file can be created manually or with the fxhash CLI via the fxhash build command:
If there is a problem with the fxhash.js script, it will show you an error in red here - for instance, this happens when the fxhash script is outdated. When publishing your project onchain, green checkmarks next to files indicate that these files already exist on the blockchain and are indexed with fxhash’s file system, hence don’t need to be re-uploaded:
Here it will also show you an estimate of the storage costs to deploy your project onchain, this varies between the different blockchains available. Make sure to also include any additional licensing files in this project directory:
<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/a3295794-cd95-4ae1-b59f-975456aac3c3/fx_doc-icon_info_001.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/a3295794-cd95-4ae1-b59f-975456aac3c3/fx_doc-icon_info_001.png" width="40px" /> What’s the size limit on projects?
Currently the cut-off point is 500MBs - if you require more you can get in touch with us on discord.
</aside>
In the next view you’ll go through a final check to ensure that your piece is deterministic by rerunning the code for the same and different hashes. In this step you also decide on the preview image that will front your project page, this is done by fixing a specific preview hash:
Here you can also set the iteration number and/or minter address if those influence some aspects of your artwork. In case your token implements parameters and/or features, they will show up here as well. After you’ve checked that everything is working properly you can go ahead and mark the two boxes to proceed to the next step - this will also lock in the hash that determines the preview image of your project.
In this step you’ll configure how fxhash generates the previews of the collected iterations via the capture module:
There’s two different manners in which the capture module can be triggered:
$fx.preview(): The capture module will wait until your code calls the fxpreview() function. As soon as it is invoked, the capture will be triggered. The placement of this function in your code is up to you, but usually it should be placed towards the end of your code, when all of the graphics have been rendered. If the piece is animated you might want to trigger it after the initial frame has been drawn.<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/a3295794-cd95-4ae1-b59f-975456aac3c3/fx_doc-icon_info_001.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/a3295794-cd95-4ae1-b59f-975456aac3c3/fx_doc-icon_info_001.png" width="40px" /> The capture module will automatically take a capture at the 300 second mark after your project was loaded in the browser.
</aside>
In the case of our example token we’re using the programmatic trigger since it is a static artwork where we want to trigger the capture after all shapes have been rendered to the canvas. After setting the capture trigger we also need to indicate the target of this capture; this can be a canvas element, or the entire viewport of the window:
In our case we only want to capture the canvas, and not the entire viewport. Selecting From <canvas> will reveal a third input field where you need to specific the CSS selector that defines this canvas - make sure to select the correct one if you are using multiple canvases in your project.
When selecting the viewport capture you’ll also have to specify a capture resolution, this essentially refers to the dimensions of the virtual browser window that the artwork is captured in. Viewport captures are useful for dynamic projects that adapt to different window dimensions:
Towards the end you’ll also see a toggle to enable a GPU rendering instance for generating the token previews. By default a CPU instance will be used and is suitable for the majority of projects. A GPU instance should only be used if your project necessitates it - if you’re uncertain about this, reach out on discord. The caveat with GPU instances is that they’re way slower to bootstrap which increases the time it takes to generate the captures.
<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/0d136645-2de0-4067-ba30-04e8977f390f/fx_doc-icon_warning_001.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/0d136645-2de0-4067-ba30-04e8977f390f/fx_doc-icon_warning_001.png" width="40px" /> When should you use a GPU-enabled rendering instance?
In a nutshell, if your project requires a GPU to render, you should ****use a GPU-enabled instance. Since these types of projects are not very common, we currently only have 4 GPU instances available, as a result the metadata assignment will be slower for projects using these GPU-enabled instances.
We can however scale to a very high number of CPU instances without bloating the rendering queue.
</aside>
If you don't use WebGL and only the regular canvas API, it's also possible that your project doesn't render properly on the CPU instance because the canvas API uses GPU acceleration. If you observe differences between the capture and your live version, then try using GPU-enabled rendering.
If your project is loading asynchronous requests from the project's folder, always consider that one of those resources may be slow to load. In that regard, if you load resources please always use fxpreview() to trigger the capture.
To verify that the capture actually works properly, the captured preview image should be identical to the generative artwork running in your browser:
In this case, although the artwork is identical you can see a slight difference between the preview and the generative artwork - the CSS border that we applied to the canvas is actually not a part of the canvas graphics itself. Generally the artwork and preview should be identical, hence here we’d have to go back and fix this detail.
In this step you’ll set the distribution settings for your project. This includes the edition size, the pricing method, the royalty percentage as well as as allowlist:
Here you essentially need to specify the following:
If you aren’t certain about how to choose these settings, we provide more detailed explanations on all of these settings here:
In this step you will configure the interface options for previewing variations generated by you project:
As the artist, we want you to have control over the freedom viewers will have when exploring variations of your project on the token page. Under the display frame, a variations button can be used to explore different variations, if enabled when you minted the Generative Token:
For projects using fx(params), the explore params button allows users to navigate the parameter space of your Generative Token.
You can configure the following settings, for both during the mint period and after fully minted:
variations and explore params buttons are active. If disabled, these buttons will be unclickable and visibly deactivated. Note that pre-mint exploration cannot be disabled for fx(params) projects.These settings should give enough control to define a strategy during the lifetime of your token. You can for instance disabled infinite exploration after token is minted, so that the front end only display a finite number of states through the minted collection of the token.
<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/40d8b4a6-9271-4a10-9394-730742c3842d/fx_doc-icon_notes_001.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/f9d1e984-50ed-4650-a543-95d2b6c0ba90/40d8b4a6-9271-4a10-9394-730742c3842d/fx_doc-icon_notes_001.png" width="40px" /> Please note that the variation settings have no effect on the iterations which will be generated from your project.
</aside>
In the penultimate step you’ll add a quirky title, a description for the project, optionally a different description for the collected iterations, a list of tags that are geared towards discoverability of the project on the fxhash website and other 3rd party exploration tools, as well as some labels that can indicate a special behaviour of your project:
One step that many artists struggle with, is writing a description for the generative artwork. This description will live on the GENTKs project page and is frequently the first point of contact that collectors have with the artwork. In a way, it's your sales pitch in which you tell your potential collectors a little about the artwork and try to capture them.
This can be a romantic backstory, the discovery of a bug that led to an interesting visual composition, or even the recount of a quick coding session that led to a new algorithmic method. However, artists make art simply for the love of making art, it is often the case that there isn't a romantic backstory, especially in generative art that often ends up being a very exploratory endeavour. In this case it is also perfectly okay to reflect on the provide retrospective insights into the art-making process.
It is also a nice gesture to give a little shoutout to the libraries that you might have used and their creators, as well as the people that contributed and helped you in the ideation and development process of the code. And it is also a good idea to provide an overview of the different ways that users can interact with the GENTK, for instance the keys that map to certain user interactions.
To summarise, a good description provides:
This is the final preview of your project, and essentially indicates what your project will look like once published:
Additionally if you selected that your project should be stored on-chain it will indicate how much this storage transaction will cost, and you’ll have to perform this operation to unlock the publish project button. If you chose IPFS you can directly go ahead and publish the project.
If it happens that you need to break off this minting process, fxhash will save your progress and you can always return later and resume from where you left off, simply hit the ‘continue’ button when it asks you to:
After you complete all of these steps you’ll have to do another confirmation in your wallet, cover the transaction costs. After a few seconds the project should then show up of your profile page and in the fxhash feed.
← Previous
