01
In short
vibe builds NFT collections from one approved subject. You describe a character, a product or a mark, the engine opens every prompt with that description and moves only the trait phrase after it, and the same page composes the traits, computes the rarity and writes the ERC-721 files.
The point is a run you can repeat and audit, without carrying folders between five programs and hoping the numbering survived.
02
Where a collection breaks
A single frame is the easy half
Image models handle a single frame well. A set of ten thousand needs the character to hold, repeats to be caught, trait rules to be obeyed, rarity to add up, JSON to be correct and a single road to the chain.
Five tools, five places to lose the thread
Today that work is spread over a model, a layering script, a spreadsheet, a storage dashboard and a contract. Every handoff is a chance for image 417 to end up described as image 471. Here all of it reads and writes the same project record.
03
What the engine does about it
- Subject lock: your approved text opens every prompt the engine sends, and only the trait phrase after it changes.
- Variation: one style clause plus one trait phrase per candidate, and nothing else changes.
- Review: lock the candidates that hold the subject and run the rest again.
- Composition: categories carry weights and forbidden pairs, and rarity is derived from them.
- Files: IDs, names, descriptions, attributes and the image each record points at.
- Publishing: pinning to IPFS, then a gated mint your wallet has to approve.
04
What moves through it, and what it writes
InputPrompt / reference
ModelRenders the variants
RecordsHolds traits and JSON
ChainSettles ownership
Every layer hands the next one something you can look at. Up to the mint, anything can be thrown out and rendered again, and the zip you export stands alone whether or not you ever publish.
A token is one record: name, description, image pointer, attributes, collection. The mapping from picture to record is fixed rather than guessed, and blank fields, repeated IDs and dangling image paths are all caught before the zip is written.
{
"name": "vibe Sprite #0001",
"description": "Snowfield variant from the locked vibe Sprite subject.",
"image": "ipfs://…/0001.png",
"attributes": [
{ "trait_type": "World", "value": "Snowfield" },
{ "trait_type": "Light", "value": "Moonlit" }
]
}
05
Where the mint happens, and what it costs
Settlement happens on Robinhood Mainnet, chain ID 4663, paying gas in ETH. Connecting, switching network, asking the contract for a price and signing the call all begin with a click from you.
What it costs: vibe adds nothing on top. A free collection costs gas. A priced one costs gas plus whatever the contract was configured to charge, and the value you send has to equal the quote to the wei.
No launch happens before the address and its verified source are published. Until then the publish step says so plainly and the export zip is what you walk away with.
06
Rights, risk and your keys
- You need the rights to whatever you upload and to whatever comes back.
- Look at the output for trademark, copyright and safety problems before it goes public.
- Test the contract, read its permissions and get an outside audit before any mainnet deployment.
- Nothing here is a claim about what a token will be worth or whether anyone will buy it.
- Keys stay in your wallet. A seed phrase is never requested and never stored.
07
The V4 hook, and what a swap pays for
$VIBE trades in a Uniswap V4 pool with the vibe hook attached. The hook runs inside every swap of the pool, so nothing sits between a trade and its effect.
A buy credits the buyer with renders in the studio. Every swap, buy or sell, sends one percent of the trade to the engine's compute budget, which pays the render provider. The more the token trades, the more the engine renders.
There is no tax contract and no owner switch. The hook is the pool's own code, readable on the explorer at the address published on the home page once the pool is open. Render credits are read from the hook by the studio and spent there; they never leave the wallet that bought them.
08
What ships next
Phase 01
The studio
Locking a subject, previewing a direction, running batches, exporting the zip.
Phase 02
The composer
Rules you can see, a rarity preview before you commit, repeat detection.
Phase 03
The publisher
An audited deployment, gated minting and the collection showing on OpenSea.