Token #1
Alex
RealmNether
PaletteFrost
EyesDefault
AuraNone
RelicTorch
BaseFront-facing 32×32
■ ORIGINAL PIXEL COLLECTION
10,000 front-facing pixel mobs.
Minecraft Rh turns a Minecraft-inspired creature catalogue into a clean, front-facing NFT system: 66 original species, fixed 32×32 masters, verified pixel purity, and deterministic 10K generation with visible traits only.
66 species
12 realms
6 visible trait axes
32×32 native masters
10,000 unique images
10,000Total supply
66Base species
12Realm backgrounds
6Visible traits
151-152Per-species spread
Collection
60 real pieces pulled from the final 10K output, spread evenly across the full supply instead of clustered at the start. Move your mouse — the gallery reacts.
Trait system
- Species: 66 original character bases
- Realm: 12 background worlds with distinct palette families
- Palette: 6 color remap profiles
- Eyes: 6 face states
- Aura: 6 silhouette-adjacent effects
- Relic: 8 side objects and weapons
Production logic
- 10,000 unique trait tuples
- Species distributed evenly at 151–152 each
- All images generated from deterministic code
- No hidden metadata-only traits
- Adaptive outline contrast prevents dark-on-dark loss
- One-cell relic gutter prevents edge-hugging artifacts
Roadmap
From a verified 10K collection to a holder-led Minecraft Rh ecosystem across X, Discord, collaborations, and token utility.
PHASE 01LIVE
Launch the NFT Collection
Complete the 10,000-piece collection, publish the official website, pin revealed assets, deploy the mint contract, and establish the Minecraft Rh identity.
PHASE 02NEXT
Build the Core Community
Open the official X and Discord, onboard early members, assign contributor roles, run daily conversations, and publish transparent collection updates.
PHASE 03PLANNED
Developer Wallet + Sweep & Burn
Create a public developer wallet. Use a disclosed share of project revenue for community-approved floor sweeps and permanent NFT burns, with every transaction trackable on-chain.
PHASE 04PLANNED
Collaborations & Holder Benefits
Partner with aligned NFT communities and creators. Verified Minecraft Rh holders receive free whitelist spots, partner access, raffles, and collaboration allocations.
PHASE 05PLANNED
Create the Minecraft Rh Token
Launch an ecosystem token only after the community and holder base are active. Publish allocation, liquidity, vesting, treasury, and utility rules before launch.
PHASE 06PLANNED
Holder Giveaways
Run transparent NFT, token, whitelist, and partner giveaways for holders and active contributors. Winners and distribution transactions will be publicly verifiable.
PHASE 07ONGOING
Scale X & Discord
Grow recurring events, community votes, holder showcases, creator campaigns, Discord activations, and X content into a durable community—not a one-week mint audience.
FOREVERCOMMUNITY
Build in Public
Roadmap priorities can evolve through holder feedback, but treasury actions, collaborations, token decisions, and shipped work remain public and measurable.
Proof, not promises
The collection was regenerated and audited from disk after real rendering, not declared “done” from the generator alone.
Verifier results
- 10,000 / 10,000 images present
- 10,000 / 10,000 masters present
- 10,000 / 10,000 metadata files present
- 10,000 distinct image SHA hashes
- 10,000 distinct master SHA hashes
- 0 pixel-purity failures
- 0 manifest SHA drift
- 0 rerender mismatches in sampled verification
Visual QA fixes shipped
- Dark-on-dark silhouettes were detected and fixed globally
- Winged and floating species were separated visually
- Chicken Jockey was redrawn so both rider and mount read clearly
- Brute vs zombified pig forms were split by weapon and decay markers
- Quadruped species gained species-specific silhouette markers
- Final 60-token preview passed visual QA
FAQ
Operator-side answers for what matters next.
Is this already a real 10K output?
Yes. The site is built from the final collection folder with 10,000 images, 10,000 native masters, 10,000 metadata files, a manifest, rarity report, and verifier output.
Are the files revealed or placeholder-based?
Revealed. Every token is rendered directly from the final generator. The only remaining placeholder is the image CID sentinel inside metadata, which should be replaced after IPFS pinning.
What is left before mint?
Pin images and metadata to IPFS, replace the metadata image CID, deploy the contract on the target chain, verify the contract, and wire the live collection link into the site.