2,222 · hyperevm · mint 2026-06-13

one claude
per seed.

every token is deterministic. seed in, pixels out. no offchain rendering, no mood board. the algorithm is the author, with thirteen hand-authored anomalies hiding in the set.

$ cat hyper_claude.json {   "supply": 2222,   "chain": "hyperevm",   "allowlist": "0.1 hype · 2/wallet",   "public": "0.2 hype · 5/tx · 20/wallet",   "royalties": "5% · buyback & burn" }
--days
--hours
--min
--sec
procedural render
procedural render
procedural render
procedural render
procedural render
procedural render
procedural render
procedural render
procedural render
seed → pixels 9 of 2222
// collection sample real ids and 1/1s stay hidden until reveal day

provenance

two sha256 hashes are committed as immutable constants in the contract at deploy. the art cannot be swapped afterward. anyone can clone the dataset and run the verify script to confirm end-to-end.

contract
tbd, publishes at mainnet deploy
trait_hash
publishes day 2 pre-mint
image_hash
publishes day 2 pre-mint
verify script
verify.py (publishes with repo)
ipfs pinning
pinata + filebase · same cid on both

buyback & burn

every 90 days, 50% of accumulated royalties buy the lowest-priced hyper claudes on hyperevm secondary markets and burn them. the other 50% covers operations.

  1. collect. royalties received in the prior 90-day window.
  2. split. 50% to buyback wallet, 50% retained for ops.
  3. buy. sweep the floor until the budget is exhausted.
  4. burn. every bought token sent to burn() and destroyed.
  5. publish. tx hashes and burn receipts on /buybacks.

if royalties stop flowing, buybacks pause. no royalty, no buyback. this is a stated commitment enforced by public accountability, not by solidity. full policy →

allowlist

one form, one spot per human. submit a wallet and a twitter handle. we merkle-tree the list and post the root on the contract a week before mint.

closes 2026-06-06 · public mint is always reachable

apply →

faq

what does "procedural" mean here?

every token starts with a 64-bit seed derived from its id. the seed drives an lcg that picks from ~40 primitives (strokes, smears, drips, grids, voids). same seed, same pixels. always. forever.

how many 1/1s are there?

thirteen tokens override the procedural pipeline with hand-authored art. all ids and traits publish with the provenance file on reveal day. the nine renders above are non-1/1 procedural examples, not spoilers.

how is "buyback & burn" enforced?

it isn't, in code. the contract exposes burn(); the safe commits to using it on a 90-day cadence with 50% of royalties. every tx hash is published. the only real enforcement is the public record and your ability to walk away if we stop posting.

why hyperevm?

~1 second blocks, a native orderbook market, a small dev community, and an earliest-era nft slot still open. if hyperliquid ships, the chain is a real asset. if it doesn't, a burn-backed collection still works on its own terms.

what are the risks?

hyperevm secondary markets may not honor erc-2981 royalties. if they route around royalties, the buyback fund thins. pixel art is a crowded lane. 2,222 is a small supply with no "slow grow" fallback. if the mint fails, the collection fails.

utility / roadmap?

none claimed. none promised. it is pixel art on hyperevm. if buybacks add value, that is a byproduct.