HashToken × EPOCH Miner
One GPU, two coins. HashToken: brutally hard, and every mint makes it harder. EPOCH: easy. For now.
HashToken (HTK) is a proof-of-work token deployed on June 17, 2016. Every mint shrinks the target ~1%, so its difficulty ratchets up forever. The same hashes quietly accumulate EPOCH (EPC): 10 EPC per share, and shares come easily. In the beginning. What EPOCH is will be revealed in August. How it works ↓
FAQ
How does HTK mining work?
The GPU searches for a 32-byte nonce with
keccak256(nonce ‖ prev_hash) ≤ max_value; a hit mints HTK. Every mint
shrinks max_value ~1%, so difficulty rises forever. The ETA is a statistical
average; luck swings both ways.
What is EPOCH (EPC)?
More will be revealed in August. Until then: shares come easily, each pays 10 EPC, and one address can collect at most 10,000 EPC through this site.
Can I claim manually, e.g. via Etherscan?
Yes, connecting a wallet to this site is never required. In the epoch
list, click the epoch's hash to copy the full prev_hash and the ⧉ button
to copy the sorted nonce array. On Etherscan, open
the claim contract →
Contract → Write Contract → connect the payout wallet → claim: paste the
prev_hash and the nonce array, then write. checkpoint() can be called the same
way (no arguments, any wallet). Your shares live in this browser's localStorage; copy them
out before clearing it.
Why add a payout address?
Mining works without one; HTK solutions are valid either way. But the address is baked into every EPC share at hash time, which makes shares theft-proof: only that address can claim them. Shares mined without an address are bound to nobody and can never be claimed. Use a different address per machine, or your machines can invalidate each other's shares. Switching the address later is fine: already-mined shares stay in the ledger bound to their original address (epoch rows show them separately). Switch back, or connect that wallet, to claim them.
Do I need a wallet?
No, mining only needs an address. A wallet is used only to submit
mint(), checkpoint epochs and claim EPC. Solutions and shares are always
shown and stored locally, so you can act on them with your own tooling.
How do I submit an HTK solution safely?
HTK nonces are not bound to your address: in the public mempool anyone can copy yours and mint first. Click 🛡 Add Flashbots Protect RPC, make sure your wallet has that network selected, then submit, or copy the nonce into your own private-transaction tooling.
Can I trust the results?
Every GPU hit and share is re-verified on the CPU against freshly fetched chain state before it is shown. Each session searches its own region of the nonce space, so concurrent miners don't overlap.
Mining seems slow?
Keep this tab in the foreground (browsers throttle background tabs), check the GPU name chip (integrated vs discrete), and run ⏱ Benchmark under GPU tuning. Auto-tune targets ~200 ms batches; untick it to pin workgroups × iterations yourself. If the driver resets ("device lost"), lower the values.