Five tiers of 1111. Each tier +25%. The last specimen costs exactly twice the first — the table is immutable at deploy. Hover to price any token; the fill is the live counter.
5% of every secondary sale goes to an escrow pool. Each 7-day epoch the pool splits pro-rata across specimens that stayed sealed — no listing, no approval, no transfer. Drag the sliders. Then try listing.
Every image is a pure function of its seed. Measured distribution over the full set:
Each token's image is a pure function of its seed: render(seed) → 64×64 RGB. The renderer is ~14 KB of dependency-free code producing bit-identical output in this page, in the metadata endpoint and in the reference implementation. Parity is verified by hashing the pixel buffer (FNV-1a over 12,288 bytes).
Seeds were not chosen — they were found by a fleet of autonomous agents running a bounded search against a Module-LWE lattice commitment. Consequences: the trait distribution is not editable (nobody curated rares into existence), and the set is reproducible — the seed manifest is public, re-render and diff the hashes.
1,104 agent processes terminated without returning. Logged as overhead.
tier(id) = floor((id - 1) / 1111) // 0..4 price(id) = base * (1 + 0.25 * tier(id)) // base .. 2.00 * base
| TIER | RANGE | PRICE |
|---|---|---|
| 0 | 1 – 1111 | 1.00× base |
| 1 | 1112 – 2222 | 1.25× base |
| 2 | 2223 – 3333 | 1.50× base |
| 3 | 3334 – 4444 | 1.75× base |
| 4 | 4445 – 5555 | 2.00× base — ceiling |
Tier is evaluated at transaction execution and emitted in the mint event. The tier table is immutable at deploy; the only post-deploy parameter is base, set once before tier 1 opens. No allowlist, no private tier; team allocation is 55 through the same function.
Secondary royalty is 5% (EIP-2981). Receiver is an escrow contract. Epoch = 7 days. At epoch close the pool splits pro rata across every token that remained SEALED the full epoch. Claims are pull-based and batchable; unclaimed rolls forward. 0% to the team, ever.
// a token is UNSEALED for the epoch if any of these fired: Transfer(from, to, id) // any transfer Approval(owner, operator, id) // marketplace approval ApprovalForAll(owner, operator, true) // blanket approval
Listing requires an approval, which is what makes the rule enforceable without an oracle or marketplace whitelist. Revoke → re-sealed from next epoch. Nothing retroactive, nothing permanent.
| SUPPLY | 5555 · immutable |
| CHAIN | Robinhood Chain (Arbitrum Orbit L2) |
| STANDARD | ERC-721 + EIP-2981 (5%) |
| IMAGE | 64×64 · on-chain render from seed · no IPFS dependency |
| MINT | standard tx · 5×1111 tiers · 1.00×→2.00× base |
| ROYALTY ROUTING | 100% sealed holders · 0% team · pull-based |
| EPOCH | 7 days |
| ALLOWLIST | none |
Do I need a bot to mint? No. The agents' job ended before the mint — they produced the seed set. Minting is one ordinary transaction.
Is the dividend a yield? No — redistribution of realised royalties. Zero volume in an epoch → zero payout. No emission, no APY to quote.
Marketplace ignores royalties? That sale adds nothing to the pool and the seller is still unsealed — the approval event fired. The rule keys on behaviour, not platform compliance.
Can parameters change? Tier table, cap, epoch length and routing are immutable at deploy. The only post-deploy parameter is base, set once before tier 1 opens.
What does the team earn? Mint proceeds. Royalty flow and mint flow are separate contracts; they never share a balance.