RAM mining on Solana $MINER
The Memory
Miner
Your spare RAM mines SOL.
Your browser tab solves a memory-hard puzzle for your wallet. Every 0.2 SOL that reaches the pot is split by the work, 5% cap per wallet, no coin to hold.
Trial shift: your tab's work counts now. Payouts start at launch, every 0.2 SOL of the pot split by work.
goes here at launch
0 GBworking for the trench
How a shift works
A challenge for your address
The site hands your wallet 32 random bytes. Only the address, never a signature.
Your tab lends its RAM
It runs Argon2id over 256 MB, 1 GB or 2 GB until a hash starts with enough zero bits.
Every proof is re-checked
A checker recomputes the hash. Credit is band weight x 2^bits, a quarter of it from a data centre.
Each 0.2 SOL is paid out
When the pot takes another 0.2 SOL, it is split by the work since the last payout.
Where the fees go
Your share of the next 0.2 SOL
0.2 SOL / miners
Every lit ring shares one payout by work. A tab that mines the whole shift on a plane of N rings holds about one ring's part, capped at 0.01 SOL (5%).
Mine a few proofs and this card shows your own number.
Your work since the last payout
Paste the address you mine for. The ring, the work and every payout to it show here.
Every 0.2 SOL, with its file and transactions
Loading the ledger.
Miners and the plane's records
Loading the board.
How The Memory Miner works
The task
The server gives your wallet a challenge: HMAC-SHA256(secret, wallet || counter), 32 bytes. Your tab searches for a nonce so that
Argon2id(password = challenge || wallet || nonce, salt = challenge, m = band, t = 1, p = 1)starts with d zero bits. The wallet is its 32 raw bytes, the nonce 8 bytes little endian, the tag 32 bytes. No signature and no wallet connect: a challenge only needs your address. One wallet works one challenge at a time.
Bands and weights
| Band | Memory | Weight | For |
|---|
A proof is credited weight x 2^d. A bigger band takes longer per hash in the same proportion, so every band pays the same for the same time: a phone on 256 MB is not a second-class miner, and a 2 GB tab is not a shortcut. The weights were set from hash times measured in Chrome before launch; a gap over 20% between bands means the weights are changed. The 2 GB band is 2047 MiB, the most the 32-bit WebAssembly core can address next to its own heap.
Inside the tab one Argon2 instance per band lives in a Web Worker. Its memory is grown once, zeroed before every hash and reused, so the tab does not run out of memory hash after hash.
Difficulty, by events only
- A new wallet starts at 3 bits.
- +1 bit after every 32 credited proofs of that wallet.
- -1 bit when the wallet takes a new challenge without turning in the old one (floor 2).
- +1 bit for every band while more than 400 proofs wait for the check, until the queue drains.
No clock is involved anywhere: not in difficulty, not in payouts.
The check
Recomputing Argon2id on 1 or 2 GB does not fit a serverless function, so proofs go into a queue. A checker next to the keeper, on the creator's computer, recomputes one Argon2id per proof (workers: cores minus one, each up to 2 GB) and credits it or turns it down. Turned down: a duplicate, a challenge of another wallet, a hash below the target, an unknown or replaced challenge, a band that does not match the challenge. When that computer is off, proofs wait in the queue and the plane shows checks paused; they are checked when it comes back. A payout waits until every proof of its shift is checked.
During the trial shift before launch, proofs count at face value and nothing is paid. From launch on, every proof is re-checked before it counts.
Home RAM matters more than RAM in a rack
Work from the address ranges of cloud and hosting providers counts x0.25. The ranges come from the providers' own published lists (AWS, Google Cloud, Oracle, DigitalOcean, Linode) and the open IP to ASN database filtered to hosting networks, refreshed at every deploy. More than 3 wallets on one IP: only the three with the most work from that IP count (IPv6: per /64).
Payouts
- The pot takes 70% of the forwarded fees. Each time it holds another 0.2 SOL, the shift closes and those 0.2 SOL are split by credited work since the last payout.
- One wallet gets at most 5% of a payout (0.01 SOL). The surplus is spread over the others; what nobody can take stays in the pot.
- You do not need to hold the coin.
- SOL goes out in batches with the memo
miner pay <n> <SOL> <miners> <GB>. A share below the rent floor of a wallet (0.00089 SOL) is carried to the next payout. - Each payout publishes its file: every miner (wallet, band, work, amount) and every credited proof (challenge, nonce, bits, hash), so anyone can recompute it.
Money
The creator launched $MINER on pump.fun as an ordinary coin and keeps its creator fees on the creator wallet, then forwards them by hand to the keeper. Of everything above the keeper's 0.05 SOL float: 70% pot, 20% buys $MINER through Jupiter and burns it with an SPL burn, 10% pays for the checks, RPC and hosting. There is no program of our own: a keeper wallet, plain transfers, a burn and a memo.
Honest about big servers
A home server with 128 GB is still stronger than a laptop: it can run three wallets from its address at once. What holds it back: x0.25 in a data centre, three wallets per IP, one challenge per wallet, 5% of any payout per wallet. It is not made equal, only bounded.
Trust
The server issues challenges and keeps the queue; it could be wrong. That is why every credited proof is in the payout file: take the challenge, the wallet and the nonce, run Argon2id with the band's memory and count the zero bits.
This is a memecoin and an experiment, not an investment: you can lose everything you put into it.