How to earn a claim.

The whole loop in one screen.

gpuHASH is two things bolted together. A fixed collection of 3,000 NFT cards, each carrying one of three tiers — NVDA, AMD, or SPCX. And an ERC-20 token, gpuHASH, whose trading fees buy real tokenized stock of those three companies and park it in a vault. Card holders burn gpuHASH to take a share of that vault.

What you need in your wallet.

• A normal wallet — MetaMask, Rabby, or anything that speaks EVM. It must be an EOA, not a smart-contract wallet: the mint function rejects contract callers.
• Robinhood Chain added as a network. Chain ID 4663, RPC https://robinhood-rpc.publicnode.com, explorer robinhoodchain.blockscout.com. Connecting a wallet on this site offers to add it for you.
• ETH on Robinhood Chain for the mint price and gas. Gas is cheap here, but it is not free, and it is not refunded if a transaction reverts.
• Patience for one week. The first epoch has to close before any claim exists.

Mint a Genesis card.

Go to the mint page, connect, pick a quantity, and confirm. The contract is 0x24B8A39d9A4A8AFcB181514808c507Bc6e5D3a5b.

• Price is $1, paid in ETH. The contract reads a Chainlink ETH/USD feed at the moment of your transaction and converts. The ETH figure on the page is a live quote, not a fixed number. Gas is on top.
• Three cards per wallet, for life. The cap counts everything that wallet has ever minted. It is a hardcoded constant — nobody can raise it, including the owner.
• Tier is decided at mint, not later. There is no reveal step. The contract draws a slot from a pre-seeded urn, so which tier you get is settled in the same transaction that mints it. Token IDs 0–999 are NVDA, 1000–1999 AMD, 2000–2999 SPCX.
• Overpayment is refunded inside the same transaction. Sending extra ETH does not buy you anything.
• No deadline. The mint stays open until the 3,000 cards are gone, or until the owner closes it. There is no countdown to game.

The artwork is a 1024×1024 animated WebP pinned on IPFS, one of 3,000 distinct renders. Your card's metadata resolves through the contract's base URI.

Get gpuHASH tokens.

The card alone earns nothing. Weight comes from burning gpuHASH, so you need tokens. Contract address:

0xd03608a3673298ac5fc749d8b02b7b16d30e9cd8

• The token was minted by the Pons launch factory. Fixed supply, no owner, no mint function — not even the team can create more.
• Buying and selling costs 4% total: 3% creator fee that funds this whole system, plus 1% that Pons keeps. That 3% is locked forever; there is no lever to change it.
• Wallet-to-wallet transfers are untaxed. Only swaps pay the fee. Sending tokens to a friend costs nothing but gas.
• Until the bonding curve graduates, the token trades on that curve. After graduation it trades in a Uniswap v4 pool whose liquidity is locked permanently — nobody, including this project, can pull it.

Burn gpuHASH to earn weight.

Go to the burn page, pick a card you own, enter an amount, approve, and burn. Two transactions: an ERC-20 approval, then the burn itself against 0x5670907C276F54eAeFbD2834e852B563846E4021.

• Burning is irreversible. The tokens are destroyed. There is no unstake, no withdrawal, no cooldown that gives them back.
• You are buying a share, not an amount. Burning 10,000 tokens does not entitle you to a fixed payout. It entitles you to a proportion of whatever the pool holds when the week closes.
• Weight is per card, per epoch. Burning against card #42 credits that card in the current epoch only. When the epoch closes, that weight is frozen into that epoch's record and the next epoch starts everyone at zero.
• You can burn as many times as you like during the week, across all the cards you own. Weights add up.
• The burn must come from the wallet that owns the card at that moment.

Someone closes the epoch.

An epoch is exactly seven days (604,800 seconds). When the window has elapsed, anyone — you, another holder, a bot, a stranger — can call closeEpoch(). It is permissionless by design so that a dead keeper cannot strand anybody's claim.

Closing does three things, atomically:

1. Takes a snapshot of every vault pool: how much NVDA, AMD, SPCX, and gpuHASH is sitting there and unreserved.
2. Reserves that amount for the epoch, so a later epoch cannot spend the same tokens twice.
3. Opens claims for that epoch and starts the next one at zero weight.

One call closes one epoch. If nobody closes for three weeks, the first call closes the oldest open epoch and it takes three calls to catch up. The button is on the rewards page.

Claim, per card, per epoch.

Once an epoch is closed, go to rewards and claim. One claim call covers one card for one epoch, so three cards across two closed epochs is six claims.

• Each claim pays two legs: your tier's stock (NVDA, AMD, or SPCX) and a gpuHASH bonus. They are calculated separately — see the next section.
• Claims do not expire. A closed epoch stays claimable indefinitely. Nothing is forfeited by being slow.
• Each card can claim each epoch exactly once. A second attempt reverts.
• Whoever owns the card at claim time collects. If you burn against a card and then sell it before claiming, the buyer claims that reward. Price your cards accordingly.

If the stock leg fails — for example the issuer has paused transfers on that token — the bonus still pays and the stock is recorded as owed to you. You collect it later with claimUnpaid, and it belongs to whoever made the claim, not to whoever holds the card afterwards.

Exactly how your payout is computed.

Two formulas. Both read straight from the contract.

The stock leg competes only inside your tier. An NVDA card is measured against other NVDA burners, never against AMD or SPCX. The bonus leg competes across everyone, all three tiers pooled together.

A worked example, using round numbers that are not a prediction of anything:

Where the pools actually come from.

Every gpuHASH swap pays a 3% creator fee. Pons holds it in an escrow under the Treasury's name. Anyone can call harvest() on the Treasury, which claims the escrow balance and splits it in a single transaction:

The 60% is stated up front on purpose. It is visible on chain from the very first harvest, so there is no point hiding it. Forty percent of harvested creator fees is what funds every pool you claim from.

That line is arithmetic, not a forecast. Volume is not promised by anyone and can be zero. Harvesting allocates ETH to budgets; turning that ETH into actual stock is a separate transaction that only works while the US market is open.

What can hold things up.

• Market hours. The tokenized stock tokens only have usable liquidity while the US market is open. Buying attempts outside those hours revert with a market-closed error. Fees keep accruing; they just sit as ETH in the Treasury until the next session.
• Oracle staleness. Purchases also check a Chainlink price feed for sanity. Over weekends the feed goes stale and the guard blocks buys. This is intentional — it stops the Treasury buying into a dislocated market.
• Chunk cap and deviation guard. Each purchase is capped at 1 ETH and is rejected if the realised rate deviates more than 2% from the oracle cross. Large budgets are spent over several transactions rather than one.
• Graduation. The gpuHASH buyback that fills the bonus pool needs the Uniswap v4 pool to exist, which only happens after the bonding curve reaches its 4.2 ETH graduation threshold. Until then the bonus budget accumulates as ETH and the bonus pool stays at zero.
• Nobody is obliged to press the buttons. Harvest and close-epoch are permissionless precisely so you do not have to wait for the team. If a week has elapsed and nothing has closed, you can close it yourself.

What to verify, and who holds what power.

Every address in this system, on Robinhood Chain (chain ID 4663):

What the admin key can and cannot do

• Cannot mint more tokens, change the 3% fee, unlock the trading liquidity, mint extra NFTs beyond 3,000, raise the three-per-wallet cap, or take tokens out of the reward vault while the system is in use.
• Can pause the vault, close the mint, adjust the oracle staleness window within a hard 12-hour cap, adjust purchase guards, change the operations wallet, and move the creator fee recipient.
• Upgrades to the burn engine run through a 48-hour timelock. A change has to be announced on chain and then wait two days before it can execute. The vault itself has no proxy and cannot be upgraded at all.

The abandonment switch

The vault and the Treasury each have an emergencyWithdraw that the owner can call only after 180 consecutive days of inactivity. Any successful payout, harvest, or donation resets that clock. On top of that, heartbeat() is permissionless: any holder can push the unlock 180 days further out, for free, forever. This exists so assets are recoverable if the project is truly dead — not as a live withdrawal path. Call it while the system is alive and it reverts.

Verify it yourself

Nothing here needs to be taken on trust. Read the state directly against https://robinhood-rpc.publicnode.com:

The dashboard renders exactly these reads. If the page and the chain ever disagree, believe the chain.

When something does not work.

Read this honestly.

• Burns are permanent and rewards are not guaranteed. You can burn tokens into an epoch and claim nothing at the end of it.
• Every pool depends on trading volume you do not control. No volume, no fees, no pools, no claims.
• Tokenized stock is a third-party security. Its issuer can pause it, and holding it may be restricted where you live. US persons are among the restricted parties.
• The launch platform retains a standing power over where creator fees are routed, exercisable on a three-day timelock. This project has no veto over it.
• Sixty percent of fees go to operations, not to holders. That is the design, stated openly, and it is visible on chain.
• Smart contracts can contain bugs. These are audited by tests, not by a third-party security firm.
• This is not financial advice and nothing on this page is an offer or a promise of profit. Spend only what you are prepared to lose entirely.

The full technical reference, including admin powers and the earlier deployments kept for audit trail, lives in the documentation.