Artblocks
Artblocks supports collecting and publishing generative NFTs with customization for compatible works
Artblocks supports collecting generative NFTs and publishing collections, while compatible Engine Flex works can offer artist-defined PostParams controls. Collecting creates or acquires a token; publishing releases an artistic system. Customization requires enabled parameters and an authorized wallet, so the appropriate application depends on the project and its configuration.
What's inside
Previewing supported PostParams changes lets an authorized wallet test settings before recording an update on-chain.
A new mint creates an unseen output
A new mint fits the aim of receiving an unseen output from an artist's system, subject to that release's supply and sale conditions. The artist supplies the algorithm that governs the work. Minting associates the token with a hash that seeds its particular output. The token records ownership through the ERC-721 standard. Purchase submission alone does not establish ownership; the contract assigns the new token when the mint succeeds.
Sale configuration determines when that outcome becomes available. A fixed-price purchase must confirm before the available supply sells out. A ranked-auction bid competes for an allocation and precedes the creation of the winning artwork. The purchase price and Ethereum network fees are separate cost inputs. Network activity affects gas costs, so an advertised artwork price alone does not describe the transaction's total cost. Minting decisions also depend on the release's eligibility requirements.
Collecting an existing token better fits the aim of choosing a particular visible output.
Can every collected work accept PostParams?
PostParams require a compatible Engine Flex project with configured parameters; editing also requires authority to change the selected parameter. The artist defines the available settings, their allowed values and who controls each setting. Permissions can belong to the artist, current token owner or a specified address or contract. Owning a token therefore does not establish permission to edit every parameter. Available settings may govern color palettes, animation behavior or other dimensions that the artist exposes.
Engine Flex NFTs on core version v3.2.5 or later support configurable PostParams.
Compatibility provides the technical foundation; the project still needs a configured implementation. The script receives parameter values through
tokenData
and interprets them alongside its other inputs. Integer and decimal parameters can have artist-defined minimum and maximum values. Artists should provide deterministic hash-based fallbacks when a token has no configured parameter value. The script can then render the work before anyone configures that parameter.
A fallback handles an unset value. It does not add editing rights or retrofit PostParams into an incompatible contract.
Previewing settings before committing a change
The Artblocks token page lets an authorized wallet preview the work's editable PostParams before submitting a blockchain transaction. Previewing does not record an on-chain update. Submission starts a transaction; successful on-chain execution records the change. Recorded updates become part of the token's provenance. Further editing depends on the parameter's permissions and any artist-configured lock date. Once a parameter locks, it cannot be unlocked. Previewing is the appropriate stopping point when a permanent record of a change is not yet intended.
Studio publishing for artist-led collections
Studio fits an artist who wants to release a generative collection through a self-publishing platform with control over creation and distribution. The job starts with an algorithm that defines a coherent range of outputs. Its programmed rules determine which visual properties can vary. Collections can include animated, interactive or audiovisual work when the artist's script implements that behavior. Publishing a collection and receiving a specific token are different outcomes: the collection supplies the system from which individual works can emerge.
Studio's self-publishing role differs from the Curated collection program. Contract ownership becomes a separate concern when publishing expands into operating a platform.
Engine deployments for a separate platform
Engine fits a project that needs generative minting inside a separate platform whose operator owns and controls the smart contract. A deployment combines a V3 core contract with the shared Minter Suite and rendering infrastructure. The core stores project scripts, token hashes and royalty data. The Token API, Generator API and Media Proxy expose tokens through the rendering infrastructure. The minter governs the selected sale method. Supported applications include gallery releases, fashion collectibles and procedural game items. Platform ownership and a collection's creative configuration remain separate responsibilities.
For a traditional project, the token hash seeds the script's output. Engine Flex also allows the script to consume additional assets and configured parameter values. Partners can combine generative code with images, audio or stored data. Reproduction then requires the dependencies that the project actually uses, alongside the relevant settings. A changing parameter becomes an additional input to the rendered work.
Extra capabilities remain optional. A traditional project can use Flex without editable parameters or decentralized-storage assets; the contract label alone does not describe the artwork.
What is needed to display a work outside the platform?
Independent display requires the creative script, token-specific data and the libraries or assets that the project uses, together with a browser that can run the work. The on-chain generator can assemble a browser-viewable HTML document from blockchain data. Its
getTokenHtml
method takes the core contract and token ID to return the token's rendering HTML. Retrieving that document and displaying the work are distinct outcomes when rendering still requires external libraries or assets. Those dependencies must also remain accessible. The Dependency Registry stores some library releases on-chain and records a preferred content delivery network for other approved versions.
Artblocks reported full on-chain compatibility for the Art Blocks 500 permanent collection in its 9 September 2026 article, Art Blocks: True Onchain Artwork. That announcement concerns the named permanent collection. Engine Flex can also support projects that use IPFS or Arweave assets, which retain those storage dependencies. A project using only on-chain ingredients offers a different preservation path. Access to Ethereum data and a compatible rendering environment remain necessary for experiencing the work.
Publishing options by artwork requirements
Studio, Engine and Engine Flex address different publishing requirements, from an artist-led release to a separately operated platform with optional input types. The relevant choice follows the intended publishing job and the dependencies that its artwork needs.
| Publishing option | Intended job | Control model | Artwork and dependency scope |
|---|---|---|---|
| Studio | Release artist-led collections | Artist controls creation and distribution | Generative NFT collections |
| Engine | Operate a partner platform | Partner owns the core contract | On-chain scripts with at most one Dependency Registry library |
| Engine Flex | Operate a platform with optional additional inputs | Partner owns the core contract and configures project features | On-chain scripts; optional multiple libraries, IPFS, Arweave or BytecodeStorage |
| Library and storage choices determine rendering dependencies; a broader feature set does not make every project fully on-chain. | |||
Useful questions about Artblocks
Which releases require an approved wallet or an existing artwork?
Allowlist releases require an approved wallet, while token-gated releases require the specified artwork in the purchasing wallet. An artist may also set a per-wallet purchase limit for an allowlist release. Token-gated eligibility depends on holding the required artwork at the time of purchase. Selling or transferring it beforehand removes that eligibility. Meeting the access condition does not reserve an artwork beyond the release's applicable rules.
Can a ranked-auction bid be canceled after submission?
A participant cannot cancel a submitted Ranked Auction Minter bid. The system cancels the bid and returns its funds when another bid displaces it from the winning set. Increasing a winning bid collects the additional amount and resets its timestamp. That reset matters because earlier bids receive priority when bid amounts match.
When can token parameters support physical production?
PostParams can record artist-defined settings before physical production when a project provides that connection. The settings might specify choices that the artist uses to produce the physical work. Configurable parameters alone do not establish that an NFT includes a physical item or fulfillment entitlement.
How can a generative artwork respond to live blockchain data?
A PostParams-enabled project can use augmentation hooks to supply live on-chain data to its script. Documented inputs include the current token owner's address, block height and base gas fee. The artist determines how the script uses those values. A work that consumes changing data has additional rendering inputs beyond its token hash, so reproducing its display also requires the relevant data state.
Which contract version supports project-specific transfer hooks?
Transfer hooks require an Engine core of version v3.3.0 or later, or an Engine Flex core of version v3.3.1 or later. An existing incompatible core cannot gain hook support; the project needs a new compatible deployment. The project configures a hook contract that the core calls on token mints and transfers. A hook can record provenance or impose movement conditions, and a reverting hook aborts the mint or transfer. Project configuration can permanently lock the hook address, including a setting that prevents any hook. Core compatibility does not mean every collection uses one.
Does changing a PostParam automatically update the token's displayed features?
A token's displayed features reflect PostParams through the project's chosen integration. An artist can read the injected tokenData values in the features script and define how those values affect features. A separate direct-override option replaces a feature value when a configured PostParam has the same name. The direct override applies after that parameter has a configured value.
Where can artists test PostParams before activating a project?
Artists can test PostParams on artist staging before activating a project. Creator Dashboard V2 exposes Token page preview through View outputs for a minted token. The legacy dashboard uses Outputs for the same preview. An inactive project requires the artist wallet. Before a test transaction, the connected wallet, selected network and parameter values must match the intended test.
Are Engine partners able to approve their own minting contracts?
Engine partners can approve custom minters for their own contracts. The MinterFilter coordinates minter assignment within the deployment. The shared Minter Suite provides existing sale mechanisms, while partner-approved custom minters offer another integration path. The selected minter determines the sale behavior that the platform must support.