Every share is logged publicly. You can verify what you are owed without trusting us — which is just as well, because the pool holds the block reward and you have no cryptographic claim on it.
Quickest way to try it. Paste and run.
Save as .env beside the miner. Then the miner needs
no flags but the certificate pin — it reads the rest from the environment.
For a machine meant to keep mining. Save as
/etc/systemd/system/quantus-miner.service, then
systemctl enable --now quantus-miner.
Several machines? Use the same token on each and
add a suffix: TOKEN.rig1-gpu, TOKEN.rig2-cpu. One account,
one balance, separate statistics per machine. Ending the name in
-cpu, -gpu or -hybrid labels the machine type.
| Worker | Type | 10 min | 1 h | 24 h | Reported | Stale / low / bad | Best |
|---|
| When | What | Amount | Reference |
|---|
Every credit and debit, so you can check the balance above rather than take it on trust. You have no cryptographic claim on the block reward — the pool's node writes its own address into the digest — so verifiable accounting is the whole of what this pool sells.
Effective hashrate comes from the work your shares actually proved. Reported is what your miner claims. A persistent gap usually means stale shares or a connection problem — only the effective figure is ever paid on.
| Miner | Payout address | Shares (1 h) | Difficulty step | Status |
|---|---|---|---|---|
| Loading… | ||||
| Height | Block hash | Found by | When | Status |
|---|---|---|---|---|
| Loading… | ||||