Luma Vulpes
Celestial / Genesis

Describe the work and Ponstudio makes it, keeps every version you try, pins the result to IPFS and deploys a collection contract in your name. Not ours.
3 works made·0 collections live·2 creators
Prompt

Versions












Most tools hand back one image and forget the rest. Here every generation and edit is a version with the prompt that made it, so a direction you abandoned at 2am is still mintable in the morning.


Version 2Hover to scrub. Every frame stays mintable, not just the last one.
No exporting, no hand written metadata, no contract pasted from a tutorial. This is the actual output: what gets pinned, and what gets deployed.
Set up a collection{
"name": "Chrome Koi #1",
"description": "A koi rendered in liquid chrome.",
"image": "ipfs://bafkrei…q4h2/1.png",
"external_url": "https://pons.studio/c/chrome-koi/1",
"attributes": [
{ "trait_type": "Palette", "value": "Chrome" },
{ "trait_type": "Series", "value": "Genesis" }
],
"properties": {
"created_with": "Ponstudio",
"creator": "0x7099…79C8"
}
}Pinned to IPFS as one directory, so every token id resolves from a single base URI.
Generation and editing happen server side against one platform account, metered in credits with a ledger behind every call. Nobody links a personal ChatGPT subscription, so cost per image is known, capped and priced rather than absorbed.
The factory clones an audited base and hands ownership over in the same transaction. Nothing about a collection depends on this platform staying online, which is the part hosted launchpads quietly get wrong.
Every project keeps its lineage: the prompt, the parent version, the model, the edit that followed. That history is why creators come back, and it is not something a generic image tool can reconstruct after the fact.
Live onchain
Luma Vulpes
Celestial / Genesis

Abyssal Bloom
Prismatic / Rare

Verdant Relic
Ancient / Legendary
