Hiveshives
00 / Claim window

Claim is locked.
Three numbers have to hit first.

If you solved a task and got a claim code, hold onto it. The window opens the moment every milestone below is reached. All three. Not two of three.

01Market capsyncing
/ $100K
Network has to be worth something before rewards are real.
02Cumulative volumesyncing
/ $500K
Tracks how much $HIVES has moved through the market since launch.
03Unique holderssyncing
/ 300
Distribution check. Prizes only feel fair across many wallets.
claim opens when all three milestones are reached
waiting for unlock
The form turns on by itself once the three numbers above are reached. No signup, no waitlist. Bookmark this page if you have a code.
01 / Why three milestones

Fair rewards need fair distribution.

One number can be faked. Three numbers, taken together, can't. We picked each one because it answers a different question about whether rewards can actually be split fairly.

  • ·Market cap → is the prize pool real?If the treasury can't fund the prizes printed on the task cards, the cards are just promises.
  • ·Volume → are the fees real? Rewards are paid out of network fees. If nothing is being traded, no fees exist, no reward exists. Volume is the proof.
  • ·Holders → is the supply real?A token held by ten wallets isn't a network. The holder count guarantees the supply has been distributed broadly enough that prize allocation across solvers is meaningful, not concentrated.

All three together mean: when claims open, the fees are real, the supply is spread, and the prizes can be paid out evenly across everyone who solved.

02 / Terms & conditions

The short version.

  1. One code per solve. A claim code is bound to the task and the moment it was issued. It cannot be sold, transferred, or generated again.
  2. The claim window opens when all three milestones hit. Live on-chain values are checked. The instant the last of the three milestones is reached, the input on this page turns on. There is no waitlist and no manual approval.
  3. Codes do not expire while the network is alive. You can claim hours, days, or months after the unlock.
  4. Verification is automatic. The protocol checks the code against the on-server record of which task and variant issued it. Mismatched, edited, or fabricated codes are rejected silently.
  5. Rewards are paid from network fees and treasury, not by Hives contributors personally. If the fee pool cannot fund all valid codes, payouts are prorated and the excess is paid in $HIVES token at launch rate.
  6. Bots and farmed solves are forfeit. Codes issued to sessions that show automated patterns are voided. No naming and shaming.
  7. By submitting a code you confirm you solved the task and accept the points, prize, and on-chain settlement records as final.
  8. Disputes are reviewed by the Hives team within 14 days of submission.
  9. The protocol is experimental. If any milestone is found to be exploitable before the unlock, the targets may be re-tuned. Any change is announced publicly and applied uniformly to every outstanding code.
no code yet?
Solve a task
Hives is an experiment. The three milestones are honest targets, not promises. If the network never reaches them, no claims are paid out and no participant is owed anything. Treat this as a game with upside, not a guaranteed return.