Mine in your browser.
Earn MH.

The short version

1. Mine in your browser to find valid proofs.
2. Submit (settle) them on-chain. Only settled proofs count.
3. Each hour is a round. Your XP set your share of that round's MH.
4. After the round, claim your MH by paying ETH.
5. Optional: spend MH on RIGs to mine more efficiently, or use it in Mint Central.

Connect to Robinhood Chain

MemeHash runs on Robinhood Chain mainnet, an Ethereum-compatible Arbitrum Layer 2. Use an EVM wallet and hold ETH on Robinhood Chain for gas and MH claims. ETH held on another chain is not automatically spendable here.

The wallet button can request the correct network. Adding a network and connecting a wallet do not themselves transfer funds. Mining settlement, claims, approvals and NFT actions are separate wallet-confirmed transactions. The address receiving a mined allocation is the wallet whose proofs were settled.

For deposits, use a route listed in Robinhood’s official bridge guide. The canonical Arbitrum bridge connects Ethereum and Robinhood Chain; other supported routes can have different fees and settlement times. Use the destination network and asset shown by the bridge. Wallet network settings are documented in Robinhood’s official wallet guide.

Manual wallet setup can use the public RPC above. Production services use provider infrastructure rather than relying on a rate-limited public endpoint. MemeHash is a separate application; using Robinhood Chain does not mean a brokerage-account balance is an on-chain wallet balance.

Your route through the app

Choose a visual theme from the header. Minimal simplifies the mining/claim interface while retaining the selected theme; switch back to the full view for NFT and protocol tools. Theme selection, header navigation and footer links are shared across the site. ENS names are display labels; the wallet address remains the on-chain identity.

The Spend area is marked coming soon. Its placeholder is not a live MH redemption feature.

What you earn, and what it costs

You earn MH, not ETH. When you claim, you pay ETH for the MH you earned, plus the normal network gas fee. Claims stay open for 72 hours after a round ends; after that, the allocation expires and that MH is never minted.

How mining and settling work

Press Hash. Your browser tries SHA-256 hashes on your device. When it finds a proof that meets your target, the proof appears in the UI.

A proof found locally is not settled XP yet. Submit it on-chain with Settle proof. The mining contract verifies it, and a valid settled proof earns XP.

Session XP counts XP found during your current hashing session. Settled epoch XP is verified on-chain and determines your MH allocation. After the epoch finishes, Check + sync all XP adds eligible unsynced XP to your selected MemeHasher or active RIG.

Difficulty rules

The epoch sets the base settlement difficulty. Local shares are progress indicators; only a proof accepted by the mining contract earns XP. Your active RIG reduces the expected work needed to meet your wallet’s settlement target.

Rarer higher-bit proofs can earn more XP. A RIG changes the work needed to find an accepted proof; it does not change your device's raw hashrate.

Proof targets, scoring and nonce lanes

The starting and minimum base settlement difficulty are 34 bits, with a target of 10,000 accepted proofs per epoch. Difficulty is a network rule; buying an NFT does not rewrite it. The active RIG changes your wallet’s acceptance target as described in the RIG section.

At rollover, more than 150% of the target proof count raises base difficulty by one bit; fewer than 50% lowers it by one bit, within the 34–48-bit bounds. Otherwise it stays unchanged. One additional bit roughly halves the frequency of qualifying hashes, before any RIG target adjustment.

A RIG-adjusted target can accept some hashes in the next-lower integer-bit bucket. Those additional accepted proofs earn the base 1 XP; higher-bit accepted proofs keep the scoring ladder above. Local shares below the actual settlement target are progress indicators and cannot be turned into paid claims.

Proofs are bound to the chain, Mining contract, epoch challenge, wallet and nonce lane. Nonce cursors and ordered submissions prevent replaying settled work. When mining with one wallet on several devices, use distinct nonce lanes/ranges through the miner’s device controls so devices do not repeatedly search or submit the same work.

Settlement supports batches of up to 250 proofs per contract call. The browser can collect and queue work, but the contract limit still applies to each transaction. Finding a proof is not a transaction; settling it is.

Epochs and XP

An epoch is a 1-hour mining round. Each round shares about 4,166.67 MH. Your percentage of all settled XP determines your percentage of that round's reward.

The reward pot does not grow when more people mine. More miners compete for shares of the same fixed emission.

Claim MH — why ETH is involved

You first earn an MH allocation through settled mining XP. You cannot pay ETH to create an arbitrary mining reward.

The reason ETH is required is that MemeHash uses paid claims to build protocol-owned liquidity while distributing newly mined MH. The ETH payment is part of the claim design; it is separate from the network gas fee.

Find and claim other rounds

FIND OTHER ROUNDS refreshes the connected wallet’s eligible rounds through the backend. The page shows when it is checking, finished or unavailable. A failed refresh is not proof that you have zero claimable MH. Review the selected rounds and ETH quote before signing; the contract rechecks eligibility and price. A claim-many transaction supports up to 72 rounds.

How the claim price is set

The contract charges 85% of a guarded price: it never goes below the launch minimum and, once trading is live, it checks current and recent market prices so a brief manipulated dip cannot make claims artificially cheap.

The minimum claim price is 0.001 ETH per 1,000 MH (0.000001 ETH per MH). The price can rise with the guarded market reference and fall again toward that minimum. The amount of MH in circulation does not directly set this price.

The mainnet launch reference is approximately 0.001176470588236 ETH per 1,000 MH, giving a minimum claim cost of 0.001 ETH per 1,000 MH. The minimum is enforced by the Mining contract. Token circulation is not a direct input to the formula.

The 85% multiplier is relative to the guarded reference, not always the latest trading price. When a recent time-weighted price is higher than spot, a claim can cost more than buying the same MH at the current market price. Review the ETH quote and gas before deciding whether to claim. A transaction has a maximum ETH-cost guard so an unfavourable price change can make it revert instead of silently charging more.

The Claim page shows the current quote before you confirm the transaction. Buying MH on Uniswap is a separate action from mining and claiming.

How claim-funded liquidity starts

MemeHash uses a protocol-owned MH/WETH Uniswap V3 pool. Initializing a pool price is not the same as funding it. The protocol does not require a team-funded genesis ETH deposit: the first successful paid mining claim provides the first protocol liquidity funding.

Within that claim transaction, the Mining contract mints the claimant’s MH, splits the paid ETH and calls the vault’s bootstrap path. The vault pairs the claim-liquidity ETH with its budgeted protocol-reserve MH, and the adapter mints the protocol LP position to the vault. These actions are atomic: a failed required bootstrap reverts the claim rather than leaving a partly completed first claim.

The oracle’s trusted market history starts with that protocol-created liquidity, not with the time an empty pool was initialized or arbitrary external dust liquidity. Claims use the launch minimum before activation and throughout the 24-hour long-TWAP warm-up. After warm-up, live spot, 30-minute and 24-hour TWAP data feed guarded claim pricing.

Once the market is ready, missing, stale or invalid oracle data can make protected actions unavailable until valid data is available. The system does not silently fall back to a cheap launch quote after an established market’s price feed fails.

Where the money goes

These are separate flows. They should not be read as one combined split.

ERC-2981 communicates the requested NFT royalty. A marketplace can choose whether it actually collects and pays that royalty.

Reserve budgets, LP fees and ownership

The protocol reserve is 500,000,000 MH, held separately from the 500,000,000 MH mining allocation. A miner receives only the MH earned and successfully claimed; protocol-reserve tokens used for LP pairing are not extra miner rewards.

78.285% is a token-budget ratio, not the claim ETH split. Across the full mining allocation, the maximum claim-pairing reserve is 391,425,000 MH. The remaining 108,575,000 MH is an auxiliary reserve budget, including the royalty-liquidity path. Source-separated accounting prevents a royalty or fee path from silently spending tokens reserved for future claims.

The ETH that goes to liquidity is still 92.1% of claim ETH. If the guarded reference is above market spot, not all received ETH necessarily pairs immediately: excess ETH may remain in the vault rather than forcing it to exceed the hard MH pairing budget. The reserve ratio is not a fixed claim that all money is deployed in the same block.

Protocol LP position NFTs are owned by the vault. It has no generic owner withdrawal function. Collected V3 trading fees are measured and accounted separately; WETH fees can be unwrapped into native ETH and fees may be reinvested through the adapter. Fee reinvestment is not a dividend payable to every MH or NFT holder.

Switching the vault’s liquidity adapter requires a visible 180-day delay. That delay is a governance delay for an adapter change; it is not a promise that LP principal becomes withdrawable after six months. RIG and MemeHasher price timelocks are separate 24-hour controls.

MH supply and emission

The reserve is separate from rewards earned by miners. A round’s reward is shared between settled participants, not added for every miner. Unclaimed expired allocations are never minted. Burning MH through RIG actions reduces supply; it does not change the claim-price formula into a supply-based price or reset the lifetime mining mint cap. The reward schedule covers 120,000 reward-bearing epochs, nominally 5,000 days at 24 completed rounds per day. Delayed round starts can extend calendar time. Unclaimed allocations and integer rounding mean a supply cap is not a promise that every allocated token will circulate.

What RIGs do

A RIG does not mine for you and does not create passive MH. Your browser still does the hashing. A RIG lowers the expected work needed to find an accepted proof.

The active RIG applies the following reductions to expected settlement work. The panel shows the on-chain effect for your wallet.

RIGs do not have a fixed collection-size cap. New IDs are issued for direct mints and evolved RIGs; burned source IDs are not reused. Only one RIG can be active at a time, and boosts do not stack. Every device mining with the same wallet benefits from its active RIG. Owning extra RIGs does not increase the boost.

Mint/evolution fees are 500 / 500 / 1,000 / 2,000 / 4,000 MH. The frontend reads current prices from the contract. Owner price updates have a 24-hour delay.

Only OLD can be minted directly. To upgrade, burn two matching RIGs, pay the current MH upgrade fee, and meet the combined XP requirement. Only the active RIG earns XP when you sync finished mining rounds. Use CHECK + SYNC ALL XP: the backend checks completed history and the wallet confirms one sync transaction for eligible unsynced rounds. A history refresh alone does not change on-chain XP.

*Using the fee schedule above: every OLD mint plus every upgrade fee needed to reach the tier. XP is separate.

Mint Central

Mint Central is where MH gets utility beyond claiming.

Example: mint two OLD RIGs, then burn those two plus the current upgrade fee to create one TURBO.

Mint more than one NFT

Both mint buttons open a review modal before any approval request. Use − / quantity / + to choose how many to mint. RIG quantity is limited by your MH; MemeHasher quantity is also limited by available mint credits and remaining supply. Review the total cost, approve the required MH allowance if requested, then confirm one separate mint transaction per NFT.

The modal shows wallet requests, confirmation progress and the exact confirmed token IDs. Stopping or rejecting a later mint keeps earlier confirmed NFTs. Each transaction has its own network fee. If artwork loads slowly after a confirmed mint, use its artwork retry; the confirmed mint is still valid.

MemeHashers

MemeHashers are a 5,555-piece ERC-721 collection tied to your mining history. Each robot keeps the same permanent DNA; evolution changes its skin palette. MemeHashers do not reduce mining work or multiply MH emissions; RIGs provide mining-work utility. The 5,555 cap is a lifetime token-ID cap: burning an unstaked token does not reopen a mint slot or refund MH or credits.

The MH mint price adapts to recent network participation and your recent earned MH. The mint price is bounded between 500 MH and 2,500 MH under the production price schedule. The UI reads the exact current price, credit requirement and any pending price update from the contracts before minting.

Progression and evolution

Select one active MemeHasher for mining progression. CHECK + SYNC ALL XP checks eligible completed rounds through the backend and submits one XP sync transaction after wallet confirmation. Session XP found locally must first be settled on-chain; it cannot be synced directly from your browser counter.

Evolution advances one stage after the required XP and MH payment. The review modal shows progress and confirms the unlocked stage after its receipt. Artwork follows the new stage; a slow image fetch does not undo the evolution. XP is a progression threshold, not a balance spent by evolving.

Staking is optional. The 7 / 14 / 30-day choice is a minimum commitment, not a single-draw entry. Your MemeHasher remains entered in every weekly draw while it stays staked. When the minimum lock ends it does not unstake automatically; it keeps participating until you explicitly unstake it. Transfers remain blocked while staked.

How MemeHasher mint pricing works

Mint eligibility and mint price are different rules. A wallet earns permanent credits from lifetime active epochs; the price uses the most recent 24 completed epochs.

Gross allocation includes earned MH whether or not it was claimed. A wallet with little recent activity still pays at least the 500 MH minimum and still needs a permanent credit. The price calculation does not create credits and does not let a wallet bypass the mining requirement.

For example, 100 average participants gives a 500 MH global price. If a wallet recently earned 300 MH gross, its 50% personal calculation is 150 MH, but the minimum raises that cap to 500 MH. The final price is 500 MH. Read the MINT quote for the current on-chain price.

Price bounds, budget and the personal-earned percentage can change through a 24-hour on-chain price timelock. The UI displays current settings and pending values. A credit-policy change applies to future epochs; previously earned credits and fractional progress are preserved.

Sync XP and record mining history

There are three useful numbers: Session XP found locally, settled epoch XP credited by Mining, and the XP recorded on an NFT. Only accepted on-chain proofs create settled XP. NFT syncing copies eligible completed-epoch progression; it does not mint extra MH or alter a past round’s reward share.

In Mint Central, choose the active MemeHasher or RIG, then use CHECK + SYNC ALL XP. The backend discovers completed unsynced rounds and the wallet confirms a single syncEpochs transaction for the selected set. A manual single-round sync remains available when needed. A failed history lookup is not zero earned XP.

For each NFT collection, a miner’s epoch can be synced only once. Choosing another NFT later does not let you reuse those same epochs on it. RIG and MemeHasher sync accounting are separate, so mining can progress both collections without double-counting within either collection. Only the active RIG receives newly synced RIG XP.

Use the proof-record action to record a qualifying best settled proof on an NFT. Its record is tied to the original miner/epoch/lane/nonce and verified by the contracts. The NFT detail page exposes its best proof and verified history. Transfers retain the token’s recorded XP, stage and permanent traits; a buyer does not receive the seller’s unspent wallet mint credits.

Stake and unstake multiple MemeHashers

Open 05 MH Utils → Staking + Jackpot. You may stake multiple owned MemeHashers at the same time; your active mining NFT does not restrict which ones you can stake.

1. Click SELECT MEMEHASHERS TO STAKE.
2. Choose a 7, 14 or 30-day minimum lock, then click NFT cards to select them. Selected cards are highlighted. Selection stays when you change pages.
3. Review the selected IDs and confirm one wallet transaction per NFT. No MH or NFT approval is required for staking.
4. After an NFT’s own lock ends, open SELECT MEMEHASHERS TO UNSTAKE, select unlocked staked NFTs and confirm each unstake.

The stage multiplier is 1.00× / 1.25× / 1.50× / 2.00× / 3.00× across the five MemeHasher stages. These draw points are separate from mining XP. Every staked NFT has its own weighted entry. The page’s ACTIVE NFT WEIGHT describes the selected mining NFT, not a total for your wallet.

A lock ending does not automatically unstake the NFT. It remains entered in future weekly draws until manually unstaked. The selector shows each NFT’s lock status; locked and ineligible NFTs cannot be selected. Artwork being unavailable does not block selection. Confirmed results stay visible if you stop the queue or reject a later transaction.

When a jackpot draw blocks stake changes

A weekly draw simply being due does not prevent staking or unlocked unstaking. After someone requests a draw, drawPending freezes staking, unstaking and evolution until the draw is finalized. This is a contract rule. The winner claims the recorded ETH prize separately.

If available, press FINALIZE JACKPOT DRAW. If the 256-block finalization window expired, press REFRESH EXPIRED DRAW BLOCK, wait for the new future draw block, refresh the display, then finalize. Each action needs explicit wallet confirmation. Finalizing a draw never bypasses an NFT’s own minimum lock.

How the weekly staker jackpot runs

The jackpot receives 1% of paid claim ETH. Each round lasts 7 days from its recorded start. A positive prize and positive staked weight are required to request a draw. If no NFTs are staked, the prize remains in the jackpot rather than being paid to an arbitrary wallet.

Every staked MemeHasher contributes its lock points multiplied by its current evolution-stage multiplier. A wallet may hold several entries. Its combined probability is the sum of those entries’ weights divided by the total draw weight; the app’s ACTIVE NFT WEIGHT panel describes one selected NFT. Evolving a staked NFT updates its weight when no draw is pending.

Once due, anyone may request the draw. The contract commits the prize and weighted participant set, then targets a block 5 blocks in the future. Stake-weight changes are frozen during that pending phase. Anyone may finalize after the target block and within its 256-block blockhash window. The winner is resolved from the weighted ticket tree using that future block’s hash; the caller does not choose the token.

If the window expires, anyone may refresh the future draw block and later finalize; the participant set and committed prize stay frozen. ETH arriving while a draw is pending funds the next round. The selector and main draw controls expose the recovery actions.

There is one winning NFT per draw. The contract records its owner as the winner. That wallet claims the recorded ETH prize separately; the prize is not automatically transferred during finalization and cannot be claimed twice. Claiming a prize does not unstake the NFT.

A 51-bit JACKPOT proof badge and the weekly staker jackpot are different features. A proof badge does not select a weekly winner or add a separate multiplier. Weekly entry weight comes from the stake’s lock points and evolution stage.

Gallery, latest mints and NFT details

The public gallery shows the latest minted MemeHashers and RIGs without requiring a connected wallet. Use the collection tabs, token search and older/newer controls. LATEST MINTS in Mint Central links to the same public details.

Click an NFT’s image or SHOW DETAILS to open its full page. Details show the current owner, XP, evolution, best recorded proof, staking status, art traits and verified block, with large square artwork. Use Share NFT to copy or share the link. MemeHasher pages use /nft/{tokenId}; RIG pages use /nft/rigs/{tokenId}. A wallet is not required to read them.

Proof rarity is based on recorded proof bits: RARE from 30, ELITE from 40, JACKPOT from 51 and MYTHIC from 55. This is not a collection-wide art-trait rarity rank. A burned or unminted token has no current NFT detail record.

XP and ownership can load before artwork. RETRY ARTWORK retries an unavailable image or metadata response. The image link may use IPFS through 4everland; the choice of gateway does not move the NFT. Share links retain the collection and token identity.

Dynamic NFT metadata and artwork

Ownership, XP, stage, staking, permanent genome and recorded proof data live on-chain. Metadata JSON and image files are delivered off-chain. The metadata service reads the configured mainnet contracts and returns the token’s current state, including the block used for verification.

RIG JSON uses https://metadata.memehash.fun/rigs/{tokenId}.json; MemeHasher JSON uses https://metadata.memehash.fun/memehashers/{tokenId}.json. The five RIG PNGs are hosted on Cloudflare under /images/rigs/. The service selects the correct image from the actual on-chain tier rather than guessing a tier from the token ID.

MemeHasher templates and images use immutable IPFS content. The configured HTTP image gateway is https://ipfs.4everland.io/ipfs/. Their palette folders progress through base-silver, base-green, base-blue, base-red and base-gold. Evolution keeps the generated anatomy and accessories while changing the robot’s base palette.

An ipfs:// image URI identifies content; a gateway is one HTTP route for reading it. A different or unavailable gateway does not change NFT ownership. The public profile can show verified chain data before optional art finishes. Use RETRY ARTWORK when available; a failed image fetch does not undo a confirmed mint, stake or evolution.

Secondary sales, royalties and transfers

Both NFT collections report a 6.9% requested creator royalty through ERC-2981. When a marketplace collects and pays it, the royalty route splits that royalty 20% to the team and 80% toward protocol liquidity. This is a split of the royalty, not a second charge on the full sale value.

For a 1 ETH NFT sale, a 6.9% royalty is 0.069 ETH. Its 20/80 split is 0.0138 ETH to the team and 0.0552 ETH to the protocol-liquidity route, before any separate marketplace terms. Royalty-funded liquidity has separate vault accounting from paid mining claims.

ERC-2981 communicates royalty information. Actual enforcement depends on the marketplace and the collection’s compatible transfer-validator configuration; reporting ERC-2981 does not itself make every peer-to-peer transfer pay a fee. The contracts expose transfer-validator support, but the page does not promise that every marketplace enforces creator earnings.

Unstaked NFTs can be transferred by the owner or an approved operator. Staked MemeHashers cannot transfer or settle a sale until the minimum lock has ended and the owner manually unstakes; a pending draw must also be resolved. Cancel marketplace listings before staking. Transfer restrictions are on-chain even if a marketplace still displays an old listing.

Market, leaderboard and page refreshes

05 MH Utils → Market shows the ETH/MH swap interface, price, liquidity and market history. Buying or selling on the market is a separate transaction from claiming a mined allocation. Review the quote, price impact, slippage and network fee before signing; an approval may be needed when selling MH.

04 Leaderboard shows current-round, earlier-round and all-time mining results through the backend. Rankings use settled mining records. New settlements may appear after the indexer catches up, rather than immediately after a local proof is found.

Claim-round discovery, XP history checks and public NFT browsing use backend responses. Loading and unavailable states are not zero balances or zero XP. Use the visible refresh/retry control when a read fails. Wallet transactions still need fresh network checks and confirmations; using backend display reads does not make signing instant or remove gas fees.

Can I mine on my phone?

Yes, on supported browsers. Keep the page open because locking the screen or putting the browser in the background may pause or throttle mining. Expect more battery use and heat than normal browsing.

What the browser, backend and contracts do

The API reduces repeated page reads and historical scans. It cannot award a proof, shorten a lock, change ownership or authorize a signed transaction. The contracts recheck state. Indexed displays may lag recent confirmations; transaction receipts and explorer records identify what actually executed.

The interface invalidates relevant snapshots after confirmed writes. Pending, unavailable or catching-up data is not a verified zero balance, zero XP or an empty wallet. Use a visible refresh/retry control rather than repeating a transaction that may already have succeeded.

Maintenance and protocol controls

Mining can be paused for maintenance. Pausing stops the mining epoch engine and proof submission; claim functions remain available subject to their normal eligibility and deadlines. When a live round is resumed, its remaining mining time is preserved by extending its end time and a new challenge invalidates unsubmitted work for the old challenge.

Already settled XP remains on-chain. Already completed rounds retain their recorded claim deadlines; do not interpret a maintenance banner as a blanket extension of every older claim. The app shows the current round status and starts fresh work after resume.

RIG fees and MemeHasher mint-price settings use 24-hour schedule/execute controls. Changes to the mint-credit requirement apply to future epochs while preserving previous credit contribution. Liquidity-adapter and Mining-oracle replacements have separate 180-day controls. Ownership handoffs use pending-owner acceptance rather than changing control to an arbitrary address in one unnoticed step.

The deployed contracts, published configuration and emitted events define the active rules. Updating a page or metadata service does not rewrite a contract’s recorded locks, balances, proofs or ownership. The interface’s optional access restrictions are separate from the underlying permissionless contract methods.

Official mainnet contracts

What lives on chain

The contracts verify settled proofs and track epoch XP, MH claims, NFT ownership, RIG upgrades and MemeHasher stages. Hashing runs on your device. The configured metadata Worker reads the current NFT state on-chain and returns metadata at the tokenURI. The five RIG PNGs are hosted on Cloudflare; MemeHasher art templates and images stay on IPFS and use the configured 4everland gateway. Metadata and image hosting are separate from NFT ownership.

Use the published Robinhood mainnet contract links to inspect ownership, transactions and active parameters. A token with the same name on another network is not this mainnet deployment.

Official contract links are published with the production configuration.

FAQ