No-code generative art and NFT toolkit: layer-based art generator, metadata builder, and smart contract deployer for creator-owned drops.
- 01generative PFP collections
- 02trait rarity tooling
- 03metadata pipelines
- 04no-code contract deploys
- 05open editions
| Variable | Scope | Description |
|---|---|---|
| BUENO_PROJECT_ID | Server | Bueno project identifier used by the Generator API and metadata exports. |
Use Bueno for generative art and metadata generation upstream of the mint contract. Build the collection in the Generator (`https://bueno.art/generator`) by uploading layer folders, configuring trait rules and rarity weights, then exporting the metadata + image set. For minting, deploy a Bueno smart contract via `https://bueno.art/smart-contract` (creator-owned ERC-721/1155) or export the JSON and feed it into your own contract / Manifold / Highlight. Use the Bueno Manage tab to swap base URI between reveal phases without redeploying.
- ⚑Bueno-deployed contracts honor EIP-2981 royalties but do NOT include OpenSea operator filter — marketplaces that don't honor 2981 (e.g. Blur) will skip royalties; bring your own filter contract if enforcement matters.
- ⚑Generator output uses sequential token IDs starting at 1 — if your contract starts at 0, metadata will be off-by-one; verify `tokenId` indexing before locking the base URI.
- ⚑Bueno's hosted IPFS pinning is bundled with paid plans; on the free tier metadata only lives on bueno.art's CDN and can disappear if you cancel — always re-pin to Pinata/Filebase/4EVERLAND for persistence.
- ⚑Trait rules with conflicting `requires`/`excludes` constraints silently produce fewer unique outputs than requested — always run a final rarity export and verify count matches `collectionSize`.
- ⚑Multi-chain metadata export uses the same image CIDs but separate JSON per chain; don't reuse a single tokenURI across Ethereum and Polygon deploys without regenerating.