Hoodlrz Gen Kids
Fully On-Chain3,333 generative pieces. Not a picture stored somewhere — a rendering engine written into the blockchain itself. Every Kid redraws itself from its own seed, live, forever. Minted on Robinhood Chain — not on Ethereum.
The collection
Every piece, drawn by the engine stored in the contract. Filter by trait, sort by rarity, open one to see it live — animated and interactive, exactly as it renders on OpenSea.
Loading the collection…
How It Works
The engine lives in the contract
The rendering program — the whole thing, roughly 116 KB of it — is split into chunks and written into the chain with SSTORE2. When a marketplace asks for your token, the contract reassembles the program, injects your token's hash into it, and hands back a complete page. No IPFS, no server of mine, nothing to keep paying for. If this site disappears, your Kid still renders.
Your traits are computed, not stored
Nothing about your piece is written down anywhere. The contract derives all nine traits from your token hash using the same arithmetic the JavaScript engine uses — the same pseudo-random generator, reproduced in Solidity down to its 32-bit overflow behaviour. Both sides were run over all 3,333 pieces and compared one by one before anything was deployed.
Nobody knew what they were minting
Token hashes come from a single seed that did not exist while minting was open. It was fixed once — irreversibly — after the pieces had already found their owners, and the mint cannot reopen. Until then every token showed the same placeholder. Nobody, including me, could look at the art and decide which token to keep.
Nobody picked the seed either
The reveal takes two steps, and anyone can trigger both. First a call commits to a block that does not exist yet, ten parent-chain blocks ahead. Then, once that block is there, a second call reads its hash and fixes the seed from it. Whoever presses the button cannot know the outcome, and a reveal abandoned to try again leaves a public trace on-chain. The remaining trust sits with the chain's sequencer, which produces those hashes — the same trust you already place in it for every transaction here.
Where it lives
Robinhood Chain. That chain is young: its sequencer is centralised and its system contracts remain upgradable by its operator. So the honest claim is this — the work is entirely on-chain, which anyone can verify, rather than immutable forever, which nobody could promise here. The engine and its SHA-256 fingerprint are archived off-chain as well, which means the piece can be redeployed identically elsewhere if it ever needs to be.