A boilerplate to automate and ease the creation of Generative Tokens on fx(hash) using fx(params).
- provide a local environment in which you can iterate and use modern features from the javascript ecosystem
- interactive environment to test your project with different seeds and params, called fx(lens)
- automate the creation of a .zip file ready to be uploaded on fxhash
- node >= 14
- npm >= 6.14.4
- Clone this repository:
npx degit fxhash/params-boilerplate your_project_name
- Install dependencies and fx(lens):
npm install
npm start
: Starts a local http server serving your project within fxlens and hot reloading enabled- Your browser should open automatically otherwise visit
http://localhost:3000/?target=http://localhost:3301/
to see your project in the browser
fxhash requires you to use a javascript code snippet so that the platform can inject some code when tokens will be generated from your Generative Token. The code snippet is already in the index.html
file of this boilerplate, so you don't have to add it yourself.
During the development stages, the snippet will generate a random hash each time the page is refreshed. This way, it helps you reproduce the conditions in which your token will be executed on fxhash.
The code snippet exposes the $fx
object with the following structure:
{
hash: String, // a random 64 characters hexadecimal string. This particular variable will be hardcoded with a static hash when someone mints a token from your GT
rand: () => Number, // a PRNG function seeded with the hash, that generates deterministic PRN between 0 and 1
minter: String, // The string of the wallet address of the minter injected into the iteration
randminter: () => Number, // a PRNG function seeded with the minter address that generates deterministic PRN between 0 and 1
preview: () => void, // trigger for capture module
isPreview: Boolean, // is TRUE when capture module is running the project
params: (definitions) => void, // sets your projects fx(params) definitions
getParam: (id: String) => any, // get transformed fx(params) value by id
getParams: () => any, // get all transformed fx(params) values
getRawParam: (id: String) => any, // get raw fx(params) value by id
getRawParams: () => any, // get all raw fx(params) values
getDefinitions: () => any, // get all fx(params) definitions
features: (features) => void, // sets your projects features
getFeature: (id: String) => any, // get feature by id
getFeatures: () => any, // get all features
stringifyParams: (definitions) => string, // JSON.stringify that can handle bigint
}
The index.js of this boilerplate quickly demonstrates how to use the whole "SDK".
This is how Generative Tokens work on fxhash:
- you upload your project to the platform (see next section)
- you mint your project
- when a collector will mint its unique token from your Generative Token, a random hash will be hard-coded in the fxhash code snippet
- the token will now have its own index.html file, with a static hash, ensuring its immutability
The Guide to mint a Generative Token give in-depth details about this process.
The following fx(params) types are available. All types share the same attributes but have different options available to e.g. constrain your parameters to your needs.
The available fx(params) types are:
number
:Number
aka float64bigint
:BigInt
aka int64boolean
:boolean
color
: Color in 8-hexdigit and abbreviationsstring
: String with max 64 charactersselect
: Selection of provided options options
The index.js of this boilerplate quickly demonstrates a meaningfull configuration for each fx(params) type.
All param share a few base attributes and have each param has a type specific options attribute to adjust the param to your needs.
{
id: string, // required
name?: string, // optional, if not defined name == id
type: "number" | "bigint" | "boolean" | "color" | "string" | "select", // required
default?: string | number | bigint | boolean, // optional (see Randomization)
options: TYPE_SPECIFIC_OPTIONS, // different options per type (see below)
}
The fxhash snippet generates a random value for each parameter. The random value generation happens within the defined constrains of the parameter definition. Each parameter has the possibility to define a default
value. Setting the default will prevent the parameter to be initialised with a random value. This can be relevant during the development stage but is also relevant to consider for the final minting flow, when the user will define the final parameter configuration for the uniquely minted token.
All options are optional.
Options:
{
min?: number,
max?: number,
step?: number,
}
All options are optional.
Options:
{
min?: number | bigint,
max?: number | bigint,
}
No options.
Options:
undefined
No options.
Options:
undefined
All options are optional.
Options:
{
minLength?: number,
maxLength?: number,
}
Options are required. They define the options of the select
Options:
{
options: string[],
}
For ease of usage the fx(params) are being transformed into their type specific representation.
not transformed
not transformed
{
hex: {
rgb: '#ff0000',
rgba: '#ff0000ff',
},
obj: {
rgb: { r, g, b},
rgba: { r, g, b, a },
},
arr: {
rgb: [r,g,b],
rgba: [r,g,b,a],
},
}
The fx(snippet) exposes two different way to retrieve fx(params) values:
getParam
andgetParams
will return the transformed values as described abovegetRawParam
andgetRawParams
will return the raw values after being serialized from the bytestring and without any transformation
The fx(lens) offers an interactive environment to tweak and develop your generative token project.
npm start
: Starts two local http serverlocalhost:3301
serves your project with live reloadinglocalhost:3300
serves fx(lens) you can connect to a token
- Visìt
http://localhost:3300/?target=http://localhost:3301
to see your local project within fx(lens)
⚠️ Disclaimer: Sandbox is not yet compatible with fx(params).
npm run build
: Will createdist-zipped/project.zip
file
Go to https://fxhash.xyz/sandbox/ and upload the project.zip file in there to see if it works properly. If your token does not work properly, you can iterate easily by updating your files, running $ npm run build again, and upload the zip file again.
Finally, you can mint your token using the same project.zip
file.