Field Guide
- Reward pool
- Funded in SOL
Start with your processor
WAFER turns verified browser work into a share of collected creator fees. Keep a tab running, submit valid hashes, and track your SOL in Rewards.
Bring your wallet
Connect by public address. Starting a session does not request a signature or a payment.
Hold your place
Mining needs one hold unit of $WAFER, 0.05% of supply. Each unit adds 1% to your cap per window, up to 5%. Allow about 2 to 3 minutes for three agreeing holding checks.
Inside a session
- Run wafer
- Your browser searches for valid SHA-256 hashes. The server checks every result before adding work credit.
- Share the cycle
- Every 60 s cycle divides its funded pool by verified work. Your holding cap limits the share you can receive.
- Pause anytime
- Stopping ends new work. Credit already settled into your balance stays yours.
Follow the SOL
Collected creator fees split on chain: 70% funds rewards, 15% buys back and burns WAFER, and 15% covers infrastructure. Fee Pool shows the balances; Activity shows the transactions.
Rewards depend on collected fees. More computing power can earn a larger share of work, but cannot create a larger reward pool.
From credit to your wallet
Completed cycles settle into your pending SOL balance. At 0.01 SOL, it becomes eligible for automatic payment. You do not submit a claim.
A cycle without enough funding pays nothing. Its proofs still count toward the compute leaderboard. Previously settled balances are unaffected.
Know the limits
Your share changes as other processors contribute. Work above a wallet’s cap is redistributed among uncapped wallets. Unallocated SOL stays in the reward wallet.
The pool follows fees collected over 60 min. Each cycle pays at most 1.000 SOL and needs at least 0.001 SOL to pay.
Under the hood
What counts as valid work?
A proof combines a 32-byte challenge, your 32-byte wallet key and an 8-byte nonce. Its SHA-256 hash must meet the assigned difficulty. One extra difficulty bit earns twice the work credit.
Why was a result rejected?
- duplicate
- Same challenge, wallet and nonce already submitted
- expired
- Received after the challenge expiry
- wrong wallet
- Hash input uses a different public key than the submitter
- below target
- Hash does not meet the difficulty
- unknown challenge
- Challenge ID was not issued by the server
- challenge full
- The miner asks for a new, harder one
- hash mismatch
- Differs from the hash the server recomputes
- window closed
- Arrived after its window closed
- not holding
- The wallet fell below one hold unit after the challenge was issued
- holding unknown
- The wallet’s last balance read failed; its challenges stop crediting until a new one reads it again
- malformed
- A field is missing or not in the published format