The rig is running. No GPU, no driver stack, no racing other miners at three in the morning — you supply capital, we supply hashpower, and the proceeds are split by share. Everything below is computed from the live network, including the parts that argue against depositing.
One transfer to the published vault. Your deposit is confirmed against the chain over RPC, your shares are the ETH you sent, and your slice of the pool is that over everyone else’s — all of it recomputable from the explorer.
Connect a wallet to see your ETH, your shares and your slice of the vault. We store nothing about you — the position is read back off the chain from your own address.
Read from the chain, not from our books. Every line is checkable.
28.057 ETH of capacity left. The ceiling is what the fleet’s own win rate can actually deploy — past it, deposits are waitlisted rather than left idle.
Move the amount and the assumed pool size. Every input on the right is live: mint price, the network’s own loss rate, and the depth of the $HASH pool at the size we would really trade.
Everything recomputes against the live network — mint price, loss rate, $HASH depth.
Your slice is your deposit over total pool capital, so a fuller pool means a smaller share of the same cat production. At 50% that is 14.028 ETH in the vault.
Rent that one day of production would collect over the rest of the collection’s life — 0.1731 ETH per cat, after dilution by the cats mined after it. It is not cash and it is not counted above: it only arrives if the collection reaches 17,000 cats and we stay alive to claim it.
This is a run rate at this instant, not a yield. It assumes the fleet reaches 38.2% of network hashrate and that difficulty stays put, and it prices the burn leg at the size the pool would really sell — which is why a bigger fleet can make the cash line worse, not better. The mint price doubles at the next epoch boundary — 262 cats away — and at that point the burn leg needs $HASH -41.1% higher just to break even. We do not annualise this, and you should be suspicious of anyone who does.
Deposits fund the contract's mint price and gas. We fund the hardware. What comes back is split by share, and the fee only ever applies to money actually realised.
Send ETH on Robinhood Chain to the published pool vault — a plain transfer, no approval and nothing to sign — and receive one share per ETH. Minimum 0.05 ETH. No lock-up, no deposit fee.
HashCats has no allowlist and no supply cap: a cat is minted by finding a hash under the network target. Our GPUs do that work. You are never charged for the fleet — that is what the performance fee buys.
Deposits cover the epoch mint price and gas — including gas forfeited on races we lose. Nothing else is drawn from the vault.
Every cat we win is routed to whichever leg pays more: burn it inside its epoch for the full 1 000 $HASH, or hold it and collect the ETH rent that 65% of every later mint pays to live cats.
Realised ETH raises the value of every share. We take 8% of realised proceeds and nothing else — no management fee, no fee on deposits or withdrawals.
Burn shares to withdraw ETH at net asset value. A fifth of the vault is held liquid so ordinary redemptions settle immediately.
Live figures. The pool takes whichever leg pays more at the time.
into the vault
0.0408 ETH
won on-chain
Full reward only inside its own epoch
65% of every later mint pays live cats
Realised ETH returns to the vault and lifts every share. We keep 8% of what is realised — never a slice of your deposit, and never a management fee on capital that is just sitting there.
One share per ETH — one share per ETH contributed. Your slice is your contributed ETH over all contributed ETH, and both numbers are inbound transfers to a published address, so you can recompute your own share on the explorer without trusting a database of ours. There isn't one.
Net asset value is the vault's ETH balance, plus its cats marked at what burning and selling one would actually realise after slippage — never at mint price — plus its $HASH priced through the real pool. Every leg is a chain read you can repeat yourself.
We take 8% of proceeds actually realised — ETH from a $HASH sale or a rent claim that has settled. Unrealised inventory pays us nothing, which means we cannot bill you for a mark we chose ourselves. There is no management fee, so an idle week costs you nothing.
A 20% slice of NAV sits in ETH so ordinary redemptions settle on demand. Larger requests queue and are served as inventory is worked down, within 24 hours. The queue is first-in-first-out and published — no gate, no discretion.
Difficulty retargets to hold a fixed cat pace, so beyond a certain size extra ETH cannot be deployed and would only dilute the people already in. When the pool is full, deposits are waitlisted rather than accepted.
Send ETH to the vault on chain 4663. No approval, no signature, no contract call — nothing that could drain a wallet later. We count it as settled at 12 confirmations, read over RPC rather than from an explorer, so an indexer outage can never make your ETH look missing.
HashCats hashes your address, a nonce, the work behind the previous cat and a recent block together. Because the miner's address sits inside the preimage, hashpower cannot be aimed at a wallet it does not control — a pool physically has to mine into its own address. Shares are the accounting layer that gives you your slice of what that address holds, and the vault address is published so you can count its cats and its rent on the explorer without taking our word for anything.
Because difficulty retargets to hold a fixed cat pace, a pool is limited by hashrate rather than by how much ETH it has taken in. So the deposit ceiling is a published number, not a marketing one.
Working capital is what the fleet needs in flight, given that each cat is mined, settled and the ETH redeployed several times a day.
A deposit page that only lists upside is not telling you enough to decide. These are the real failure modes, in the order we think they matter.
The mint price follows 0.00016 x (2^epoch - 1) ETH. It doubles at every epoch boundary while the burn reward stays fixed at 1 000 $HASH, so the burn leg only survives if $HASH appreciates roughly in step. We show the exact breakeven.
Mining is a race settled first-come. A solution that arrives second is dead and the gas is gone. The network's live loss rate and the ETH it wasted are on the network page — we do not net it out of anything we show you.
The burn leg ends in a sale into one pool. Selling size moves the price against us, and the quoted margin already includes that slippage at the size we would actually trade.
There is no supply cap — what stops HashCats is work. Simulation puts the practical end at 17 000-20 000 cats. Mining revenue stops there; rent on cats still alive does not.
Unsold cats are marked at a conservative floor, never at mint price. If redemptions exceed the liquid buffer they are queued and served as inventory is worked down.
Shares are an accounting claim on a vault we control. That is a custody risk and no amount of dashboard removes it. Verify the vault on the explorer, and size your deposit accordingly.
No. That is the whole point. The fleet does the hashing; your deposit only ever pays the contract's mint price and the gas that mining consumes.
Because the miner's address is hashed into the proof of work. A solution found for our address is only valid for our address, so cats have to land in a vault we control. Shares are how you own a slice of it, and the vault is public on the explorer.
8% of realised proceeds — rent we actually claim and $HASH we actually sell. There is no management fee, no deposit fee, and no withdrawal fee. If the pool realises nothing, we are paid nothing.
One share per ETH you send the vault. Your slice of the pool is your contributed ETH over all contributed ETH — and because both are just inbound transfers to a published address, you can recompute your own share on the explorer. Redemptions are valued at net asset value: liquid ETH, plus $HASH net of the slippage selling it would cost, plus unsold cats marked at a conservative floor rather than at what we paid to mint them.
A deposit is one plain ETH transfer — no approval, nothing to sign. We treat it as settled at 12 confirmations, read over JSON-RPC rather than from an explorer, so an indexer outage cannot make real ETH look missing. Your ETH, your shares and every transaction hash appear on the deposit page the moment the chain has them.
Yes. 20% of the vault is held as liquid ETH so ordinary redemptions settle straight away. If redemptions ever exceed that buffer they are queued and filled as cats and $HASH are worked down — we would rather queue you than dump inventory into a thin market and charge everyone for it.
Difficulty retargets to hold a roughly fixed rate of new cats, so extra ETH does not buy extra cats — it just sits idle and dilutes the people already in. We publish a ceiling tied to what our hashrate can actually deploy, and we would rather turn deposits away than take money we cannot put to work.
There is no supply cap; what ends HashCats is work. Simulation puts the practical end at 17,000-20,000 cats. Mining revenue stops there. Rent on cats that are still alive does not, and the vault would then wind down to ETH.
No. HashCatsBot is an independent pool. We read the same public monitor the official stats site reads, and we are not endorsed by or connected to the HashCats team.
0.0500 ETH. For scale, one cat currently costs the pool 0.0408 ETH all-in, so a minimum deposit is a meaningful fraction of a cat rather than a rounding error.