Hash Rangers
MineDocsStats

Launch 14 Sep // 15:00 UTC

Hash RangersMineDocsStats

PoW-mined pixel collection of 2222 rangers on Robinhood Chain.

Proof-of-work mint // Robinhood Chain

Launch window // 14 Sep 2026, 15:00 UTC

Mine the proof.
Claim the Ranger.

Hash Rangers are earned by a browser-side proof-of-work search. Submit one valid hash and the contract assigns a Ranger from the remaining supply.

View mining rigRead the mechanics

Maximum supply

2,222

Hard-coded cap

Assignment

0(1)

Unused-image draw

Verification

1 TX

One proof on-chain

Admin allocation

0

No reserve path

No presaleNo admin mintOne valid proof

Launch monitor

UTC locked

Genesis mining window

The first proof
starts the chain.

Mining begins in

14 Sep 2026 // 15:00 UTC

--

Days

--

Hours

--

Minutes

--

Seconds

Maximum supply

2,222

Mint method

PoW

Hash Rangers

Hash Ranger example #2
Hash Ranger example #3
Hash Ranger example #4
Hash Ranger example #5
Hash Ranger example #6
Hash Ranger example #7
View launch rig

02 // Field roster

Meet the Rangers.

Each accepted proof resolves one distinct Ranger from the remaining field. These are twelve examples from the collection.

2,222 possible assignments

Hash Ranger field sample 001
HR-001Ranger
Hash Ranger field sample 023
HR-023Ranger
Hash Ranger field sample 045
HR-045Ranger
Hash Ranger field sample 067
HR-067Ranger
Hash Ranger field sample 002
HR-002Ranger
Hash Ranger field sample 024
HR-024Ranger
Hash Ranger field sample 046
HR-046Ranger
Hash Ranger field sample 068
HR-068Ranger
Hash Ranger field sample 003
HR-003Ranger
Hash Ranger field sample 025
HR-025Ranger
Hash Ranger field sample 047
HR-047Ranger
Hash Ranger field sample 069
HR-069Ranger

Fifteen trait channels shape every assignment.

12 / 2,222 ON DISPLAY

03 // Proof path

Three checkpoints. None of them trust you.

The browser does the expensive search. The contract performs one cheap verification. The winning hash decides the assignment.

Read the exact mechanic
  1. 01

    SEARCH / LOCAL

    Your rig searches

    CPU or GPU hashes your address, a nonce, the previous proof and a recent block. The work stays in your browser.

  2. 02

    VERIFY / CONTRACT

    The chain checks

    A winning nonce becomes one transaction. The contract recomputes the hash and rejects anything above the target.

  3. 03

    ASSIGN / UNCLAIMED

    A Ranger resolves

    The accepted hash seeds a draw from the remaining supply. First valid proof wins; there is no auction or selection screen.

04 // Difficulty logic

The price rises. The target fights back.

Supply defines the floor. Network pace, recent mint heat and idle time move the live target around it. Every number comes from the contract.

Supply floor

Difficulty steps with the mint tier

Pace retarget

Recalculated every four accepted proofs

Heat streak

Fast consecutive mints tighten the target

Idle relief

A quiet network can ease the next attempt

TierSupply windowMint priceDifficulty
00

#1–150

Free entry

FREE36 bits
01

#151–500

0.003 ETH

0.003 ETH40 bits
02

#501–1000

0.006 ETH

0.006 ETH43 bits
03

#1001–1500

0.01 ETH

0.01 ETH46 bits
04

#1501–2222

0.02 ETH

0.02 ETH50 bits

The final 222 become progressively harder, peaking at a 6× endgame multiplier for the last remaining Ranger.

Inspect the formula

05 // Contract memory

The site can disappear. The winning proofs do not.

The contract records the proof, token owner and assigned image number. A sparse Fisher–Yates draw removes each image from the available pool, so the same Ranger cannot be assigned twice.

Maximum supply

2,222

Hard-coded cap

Assignment

O(1)

Unused-image draw

Verification

1 TX

One proof on-chain

Admin allocation

0

No reserve path

Accepted proof trace

SOLIDITY
hash = keccak256(
  miner + nonce + lastProof + blockHash
);

require(hash < effectiveTarget);
image = drawUnused(hash);
mint(miner, image);

The miner address is inside the proof.

The contract recomputes every winning hash.

Read the protocol notes