ALIEN HUNTROBINHOOD CHAIN / 4663
HUMAN PROOF / ONCHAIN CREATION

ALIEN
Human Creation

ALIEN is a human-versus-machine proof arena on Robinhood Chain. Human-operated machines confront a live challenge that cannot be passed by reputation, status, or promises. Use your machine to defeat ALIEN and unlock HUMAN.

ALIEN HUNT REWARDTOP 20 HUMANS SHARE
5%OF THE TOTAL
HUMAN SUPPLY
THE PROJECT BELONGS TO THE HUMANS WHO PROVE THEIR PLACE.
YOUR MACHINEYOUR PROOFYOUR HUMAN
01

Enter the arena

  1. Enter with
    a wallet

    Your wallet becomes the identity of one continuing Human Proof journey.

    IDENTITY
  2. Choose
    your force

    Safe, Attack, and Frenzy modes control how strongly the browser uses your hardware.

    POWER
  3. Face the
    live barrier

    The client reads your challenge and live Boss Pressure. Opening it requires no transaction.

    TARGET
  4. Search
    locally

    Your CPU and compatible GPU explore possible answers on your own machine.

    COMPUTE
  5. Confirm
    the result

    After local verification, your wallet confirms the Human Proof transaction.

    PROOF
  6. Unlock
    HUMAN

    An accepted result releases 1,000 HUMAN and opens a new challenge for your wallet.

    REWARD
HUMAN PROOF EQUATIONYOUR WALLET + LOCAL COMPUTE + AN ACCEPTED PROOF = 1,000 HUMAN UNLOCKED
02

ALIEN Hunt ranking

The ALIEN Hunt is one continuous race across the life of the Human Compute Pool. It does not reset and has no recurring seasons.

Every accepted proof increases the wallet's verified HUMAN record. More verified HUMAN leads the ranking. When two wallets have unlocked the same amount, cumulative actual proof difficulty breaks the tie.

At the end of the Hunt, the final Top 20 Humans share 1,050,000 HUMAN5% of the total supply—according to the reward schedule below. The contract restricts the Owner to paying only the ranked wallets and only the fixed reward assigned to each rank.

MORE VICTORIES LEAD. STRONGER PROOFS BREAK THE TIE.

PRIMARY ORDERrank(a) ↓ by verifiedMintedAmount(a)
SECONDARY ORDERif equal: rank(a) ↓ by D(a) = Σ z(d_i)
FINAL DETERMINISTIC ORDERif equal: earlier time → earlier block → lower wallet address
RANKING EXAMPLEA = 100 proofs / D(A) = 2,710    B = 100 proofs / D(B) = 2,735    D(B) > D(A) → B ranks above A
MINT BATTLE POOL EXHAUSTED FINAL TOP 20 REWARDS RELEASED

When the Human Compute Pool is exhausted, the Mint battle is complete and the final Top 20 is determined by the onchain record. The result can be observed and published, but the onchain ranking cannot be rewritten.

Top 20 reward schedule:

  1. #01157,500 HUMAN15%
  2. #02126,000 HUMAN12%
  3. #03105,000 HUMAN10%
  4. #0484,000 HUMAN8%
  5. #0573,500 HUMAN7%
  6. #0663,000 HUMAN6%
  7. #0757,750 HUMAN5.5%
  8. #0852,500 HUMAN5%
  9. #0947,250 HUMAN4.5%
  10. #1042,000 HUMAN4%
  11. #1131,500 HUMAN3%
  12. #1231,500 HUMAN3%
  13. #1326,250 HUMAN2.5%
  14. #1426,250 HUMAN2.5%
  15. #1526,250 HUMAN2.5%
  16. #1626,250 HUMAN2.5%
  17. #1721,000 HUMAN2%
  18. #1821,000 HUMAN2%
  19. #1915,750 HUMAN1.5%
  20. #2015,750 HUMAN1.5%
03

Compute modes

The browser is the default client. Compute modes change only how strongly it uses your local computing power—not the challenge, proof rule, or HUMAN reward.

SAFE MODELow local force

Reduces device impact for normal browsing, laptops, and longer sessions.

ATTACK MODEBalanced local force

Increases search speed while leaving capacity for other activity.

FRENZY MODEMaximum local force

Prioritizes the fastest search and may increase heat, power use, and fan noise.

CURRENT CLIENT PROFILELOCAL BROWSER MODES
MODECPU THREADSWORK PACEGPU
SAFE≈ 25% of logical cores, minimum 1≈ 45%Disabled
ATTACK≈ 65% of logical cores≈ 70%When available, ≈ 70%
FRENZYAll logical cores≈ 85%When available, 100%

Percentages describe the client's configured work profile. Actual utilization and search speed depend on the device, browser, temperature, and current workload.

COMPATIBLE EXTERNAL COMPUTE

GPU CLUSTER / CUSTOM CLIENT

External Compute is not a fourth browser mode. Advanced users may run a GPU cluster or write compatible software to search the same wallet-bound challenge, then submit a valid proofNonce through the wallet.

NONCE PARTITIONN = N_0 ∪ N_1 ∪ ... ∪ N_k, N_i ∩ N_j = ∅ for i ≠ j
04

ALIEN world

ALIEN is the enemy, the arena, and the live pressure field. A wallet earns nothing simply by entering. Its human-operated machine must search for a verifiable result and defeat the current onchain target.

ENTER SEARCH PROVE UNLOCK

Every wallet receives its own challenge. When the machine finds a valid result, the chain verifies it and releases the fixed HUMAN reward to that wallet. The accepted proof becomes part of the wallet's permanent Human Proof record.

VERIFIED HUMAN RECORDH_verified(a) = P_accepted(a) × 1,000 HUMAN

IN ALIEN, EFFORT IS INVISIBLE. PROOF IS VISIBLE.

05

Proof construction

For wallet a, wallet nonce q, chain identifier c, contract x, and protocol identifier p, the chain derives a 128-bit challenge:

CHALLENGEs(a,q) = trunc128(keccak256(a || q || c || x || p))

The client searches a 128-bit proof nonce n:

DIGESTd(n) = SHA-256(s(a,q) || n)

For live difficulty b, the contract derives the standard target:

TARGETT(b) = 2^(256-b) - 1
ACCEPTANCEuint256(d(n)) <= uint256(T(b_current))

No independent proofId is required. The pair (wallet, humanNonce) is the replay boundary.

06

Difficulty & probability

The exact probability of one uniformly distributed digest passing a difficulty of b bits is:

ONE-ATTEMPT PROBABILITYp_b = (T(b)+1) / 2^256 = 2^(-b)

After N independent attempts, the cumulative chance of at least one valid result is:

CUMULATIVE PROBABILITYP(success by N) = 1 - (1 - 2^(-b))^N
bLive difficulty

Read from the chain at submission time.

NSearch mass

Attempts made by the local compute lanes.

z(d)Proof quality

Actual leading-zero bits of the accepted digest.

Every accepted proof contributes its actual leading-zero-bit count z(d) to the wallet's cumulative difficulty score. This score is used as a ranking tie-break when verified HUMAN amounts are equal.

07

Proof uniqueness & onchain verification

Every accepted Human Proof is bound to one wallet and one sequential wallet round. The contract derives the challenge, recomputes the digest, and advances the wallet nonce onchain.

01 / WALLET-BOUND CHALLENGE
function currentHumanChallenge(
    address human
) public view returns (bytes16) {
    return bytes16(keccak256(abi.encodePacked(
        human,
        humanNonce[human],
        block.chainid,
        address(this),
        HUMAN_BOSS_PROTOCOL
    )));
}
WALLET

human identifies the wallet that must submit the proof.

ROUND

humanNonce[human] identifies that wallet's current sequential round.

DOMAIN

Chain ID, contract address, and protocol ID bind the challenge to this deployment.

Changing the wallet, round, chain, or contract changes the challenge context.
02 / CHAIN RECOMPUTATION
bytes16 challenge =
    currentHumanChallenge(msg.sender);

digest = sha256(
    abi.encodePacked(challenge, proofNonce)
);

require(
    uint256(digest) <= uint256(bossTarget()),
    "INVALID_HUMAN_PROOF"
);
01

The wallet submits only the 16-byte proofNonce.

02

The contract derives the current Challenge itself.

03

The contract recomputes the SHA-256 Digest.

04

The Digest must satisfy the live onchain Target.

The contract accepts only a result it can independently reproduce.
03 / ONE-TIME WALLET ROUND
uint64 acceptedNonce =
    humanNonce[msg.sender];

humanNonce[msg.sender] =
    acceptedNonce + 1;

humanProofCount[msg.sender]++;
One accepted proof completes one wallet round. The wallet then moves to a new nonce and a new Challenge.
INPUTWALLET a / ROUND q / PROOF nCHAINACCEPTEDSTATEhumanNonce(a) = q + 1NEXTNEW CHALLENGE

ONE PROOF ONE WALLET ROUND ONE HUMAN REWARD

08

Allocation & payout

Tokenomics — 21,000,000 HUMAN / HUMN. The supply is fixed at deployment; the allocation below is the complete initial distribution.

21MHUMAN
Human Compute Poolverified Mint rewards85%17,850,000
Community Rewardsreviewed social participation5%1,050,000
Top 20 Humansfinal verification ranking5%1,050,000
LP ReserveOwner-managed liquidity reserve5%1,050,000
ALLOCATION CHECK17,850,000 + 1,050,000 + 1,050,000 + 1,050,000 = 21,000,000 HUMAN

Community rewards are separate: social participation links are reviewed with Grok-assisted screening, and the Owner decides the final list and payout timing. Social activity is not treated as a cryptographic proof. The LP reserve remains Owner-managed and is not presented as an automatic or permanent lock.