Field manual.

01 / 11

Overview

Stampad builds NFT collections from one locked 3D model. The subject is a rigged mesh, not a sentence. Traits are parts attached to that mesh and palettes painted onto it, so every token in a set shows the same character — not because a model was coaxed into it, but because there is no mechanism by which the character could change.

Generating a collection this way is not generation at all. It is photography: the same object, under different conditions, shot by the same camera. A stamp pad does not redraw the stamp each time you press it.

• Consistency is structural: one subject geometry across the whole run, measured, not promised.
• Metadata is a readback of the rendered scene, so the rarity table cannot disagree with the art.
• Sampling is derived from a hash, so the same seed rebuilds the same collection on any machine.
• Trading fees fund renders through a vault contract with no owner and no withdraw path.
• Every token ships as PNG + ERC-721 JSON + GLB — the 3D asset comes with it.

Stampad is pre-launch. The token has not launched, the vault is not deployed and the studio is not open. Everything on this page describes what is built (Phase 1) and what is being built. Numbers marked as proof come from a 36-token test set, not from a live collection.

02 / 11

The subject

A subject is one rigged mesh with named slots. A slot is a bone that parts can be attached to, so a part follows the joint exactly — a hat moves with the head, a tool moves with the hand.

head

hats, helms, crowns, horns, halos

hand.L / hand.R

tools, banners, weapons, lanterns

back

capes, packs, wings, shells

face

visors, masks, expressions

palette

repaints shell · accent · visor · metal · trim — no vertex moves

backdrop

world and ground colour behind the shot

Two ways in

Library rigs ship first. Curated base rigs: humanoid, creature, mech, critter, vehicle, totem, warden, drone. Every rig arrives with named slots and a fitted trait kit. Consistency guaranteed · rig failure rate zero · generation cost zero. The trade-off is honest: eight starting points, not infinite ones.

Custom subjects come after the library is proven. Describe a subject → concept sheet → pick one frame. That frame becomes a mesh and is auto-rigged. Rigging failures are caught before the subject can be locked, never after. Once the mesh exists, consistency is identical to a library rig.

A prompt box offers unlimited subjects and loses more than half of them. The library offers eight and loses none. For someone shipping a collection rather than experimenting, that is the point.

03 / 11

Trait tables and the seed

A trait table is a list of categories. Each category holds values with weights, and the table may declare forbidden pairs. Rarity is never typed in: it is derived from what the sampler actually produces, and previewed before a single image is rendered.

roll  = sha256( seed / token / category / attempt )
value = weighted_pick( category, roll )

• The same seed produces the same collection on any machine.
• A creator cannot quietly re-roll for a better personal token — the mapping is fixed before the first render.
• Anyone can recompute the full table from the seed and diff it against what was minted.

Duplicates and forbidden pairs

If a roll produces a combination that already exists, or one that breaks a forbidden pair, the sampler rolls again with the attempt counter raised by one. The attempt number is part of the hash input, so retries are as deterministic as first tries.

The seed lab on the home page runs this exact function in your browser. With the proof seed it reproduces all 36 published tokens; the project's own test script checks that against the published metadata, token by token.

04 / 11

Rendering and readback

The subject mesh is loaded once per collection and reused for every token. Per token, the renderer toggles which parts are visible, repaints the shared materials, sets the backdrop, renders, and then reads the scene back.

1. 01Decide the traits (from the seed).
2. 02Configure the scene.
3. 03Render.
4. 04Read the scene back: which parts were actually present, which palette was actually applied.
5. 05Write what was there into the token's JSON.

The readback is asserted against the intended combination. On any mismatch the run aborts, so a collection cannot reach the pinning step with a trait table that disagrees with its own art.

The subject's vertex hash is recomputed after every render and compared. A single divergence fails the whole run.

Known gap: the check proves a part was in the scene, not that the camera could see it. A part hidden behind the body would pass today. A per-trait pixel-occupancy check ships before the first public mint.

05 / 11

The three proof numbers

① Subject geometries — must be 1

Distinct subject mesh hashes observed across the whole run. Anything else means the character drifted, and the build rejects the collection.

② Metadata match — must be N of N

Tokens whose attribute list equals a readback of the scene that produced their image.

③ Reproducibility — must be identical

A re-run from the same seed compared pixel by pixel against the published art.

Checking a collection without trusting us

1. 01Read the seed and the subject hash from the contract
2. 02Recompute the full trait table from the seed — the function is published and deterministic
3. 03Diff that table against the on-chain token URIs
4. 04Fetch the subject GLB, hash it, compare to the contract
5. 05Re-render any token locally and compare to the pinned art

The in-browser verifier does the first three in one click. The last two need the renderer; the steps will be published with the studio.

Phase 1 results

Tokens rendered

36, off one rigged subject

Distinct subject geometries

1

Metadata matched the rendered scene

36 of 36

Full re-run, pixel comparison

36 of 36 identical

Third-party generation calls

0

06 / 11

The RenderVault

The creator fee on $STAMP trading does not go to a personal wallet. The fee recipient is the RenderVault contract — and ETH that enters it can only leave by paying for renders.

What the contract has

• pull() — anyone can move accrued fees in
• claimCredits() — a verified buy becomes credits
• consume() — burns one credit, emits the record
• event Rendered(wallet, promptHash, imageHash, remaining)

What it deliberately does not have

• no owner
• no withdraw, no rescue, no sweep-to-treasury
• no pause
• no upgrade path

Those omissions are the product. A vault with an owner is a wallet with extra steps.

This is a deliberate revenue sacrifice. The largest income stream in this category is routed away from the team on purpose, because it is the only way the central claim is checkable.

Known risk — disclosed up front: The launchpad factory's owner holds a timelocked power to change the creator fee recipient of any token launched through it. The current recipient cannot veto that change. ETH already inside the RenderVault is permanently safe — no owner, no withdraw path. The future fee stream could be redirected after the timelock elapses. The vault balance and the live fee recipient will both be displayed on this page, read from chain, so a redirect would be visible to everyone the day it happened.

07 / 11

$STAMP utility

The free tier finishes a real collection. $STAMP raises the ceiling — it never buys the right to exist on the site.

Free — hold 0%

Full studio, library rigs · 50 renders per day · ZIP export, no watermark · Publish on-chain at the standard fee

Press — hold 0.1%

Everything in Free · 500 renders per day · Batch size up to 500 · Queue priority

Foundry — hold 0.5%

Everything in Press · 5,000 renders per day · Custom subject route unlocked · Reduced publishing fee

Master — hold 2%

Everything in Foundry · Unmetered renders · Private rigs kept off the public library · Direct line on rig commissions

Render credits

Buy $STAMP

credits are granted to the buying wallet

Render one image

one credit is consumed, an event is emitted

Credits

never transferable, never sellable

What the token may never do

• No reward for holding
• No distribution to holders
• No claim button, no staking dashboard
• No protocol buyback, no burn promise — a lever we control is a lever we can stop pulling

Token facts

Total supply

1,000,000,000 $STAMP

Team allocation

0%

Pre-sale

none

Distribution

100% through the launchpad curve

Team purchases

bought from the curve like anyone, locked publicly, lock transaction linked

Supply behaviour

burnable by any holder; the protocol runs no buyback and promises no burn

Token status

not launched

08 / 11

Revenue

• Publishing fee — A flat fee per on-chain deployment, reduced for Foundry and above.
• Custom subjects — Per-subject fee covering concept generation, mesh conversion and rig QA.
• Rig commissions — A bespoke rig built to a brief, delivered with slots and a fitted trait kit.
• Studio production — Asset families for games and brands: one mesh, a variant matrix, stills, sprite sheets and GLBs. No token or mint required.
• Render API — Headless pipeline for teams that want the engine without the interface.

Allocation of non-token revenue

• Development40%
• Render infrastructure25%
• Rig library and commissioned art15%
• Marketing and creator grants10%
• Reserve10%

Allocation of non-token revenue. Token trading fees are excluded entirely — they never reach the team, so they are not ours to allocate.

09 / 11

Contracts and stack

StampadCollection (ERC-721)

• Fixed supply cap, set at deployment
• No open mint — a batch moves only with a signed authorization that expires and works once
• The ordered list of token URIs is hashed into that signature
• Seed and subject mesh hash stored on the contract, immutable
• Exact-value payment · reentrancy guard · source verified before any mint

Pipeline

Browser studio

rig preview · trait table · rarity math · proof verifier

Render service

headless 3D renderer · deterministic · queue-backed · the mesh is loaded once per collection

Metadata builder

asserts readback = intended · writes ERC-721 JSON

Pinning layer

content-addressed storage for art + metadata · no timestamps in published images

Robinhood Chain 4663

StampadCollection (ERC-721) · RenderVault · $STAMP

Stack

Frontend

Next.js · React · Tailwind · three.js

Renderer

headless 3D renderer driven by a build script

Assets

PNG · ERC-721 JSON · GLB per token

Storage

content-addressed pinning

Contracts

Solidity · ERC-721 · EIP-712 mint authorization

Chain

Robinhood Chain (EVM, chainId 4663, ETH gas)

10 / 11

Roadmap

Phase 1 — The proof (done)

• Rigged subject with named slots and bone-parented parts
• Hash-derived trait sampler with weights and forbidden pairs
• 36-token render, contact sheet, per-token metadata
• 1 geometry · 36 of 36 readback · 36 of 36 pixel-identical re-run

Phase 2 — The studio (in progress)

• Eight library rigs, each with a fitted trait kit
• Web studio: rig preview, trait editor, rarity preview
• Render queue with sample and full-set runs
• ZIP export with art, metadata and per-token GLBs

Phase 3 — The chain (weeks 5–10)

• RenderVault tested against a mainnet fork, then deployed
• StampadCollection reviewed and source-verified
• On-chain credits wired into the render gate
• Proof page, in-browser verifier and live vault reads

Phase 4 — The ecosystem (months 3–9)

• Custom subject route with QA gates
• Sprite-sheet output for 2D games from the same rigs
• Animation clips inside the per-token GLB
• Render API · private rig libraries · community rig marketplace

11 / 11

FAQ

Is this AI-generated art?

Not at the collection step. A model may help create a custom subject once (Route B). After that, every token is a render of that one mesh. Nothing is re-prompted per token, which is exactly why the character cannot drift.

Can I use it without the token?

Yes. The free tier is meant to finish a real collection: full studio, library rigs, a daily render allowance, clean ZIP export and on-chain publishing at the standard fee. The token raises throughput and unlocks custom subjects.

Can the team withdraw the vault?

No. The contract has no owner, no withdraw, no rescue and no upgrade path. ETH can only leave by paying for renders. The address and its verified source will be published before launch so this can be read rather than believed.

What if I re-render my collection later?

Same seed, same subject, same pixels. Published images carry no timestamps, so the content hash of a token's art is stable and a third party can reproduce the pinned file.

Where is the contract address?

Nowhere yet — the token has not launched. When it does, the address is printed on the home page and in the official channels. Until then, any contract using the name is a fake.