Account
P-00 Operator console — account lookup no login · your address is your account
No login needed — your Grin address is your account. Enter the address you mine with to see balance, hashrate and payout history.
P-01 Chart recorder — your hashrate history kept 100 days
P-02 Share quality live · connected workers
A healthy rig is >98% valid. High stale% = latency or too-aggressive overclock; high reject% = bad config / failing hardware. Live only — counters reset when a worker disconnects; they are not stored.
- Valid shares—
- Stale shares—
- Rejected shares—
No live worker sessions on this server right now — share-quality counters are in-memory and reset when a worker disconnects. Your hashrate history is persistent and unaffected.
P-03 Workers — per-rig breakdown stale/reject % = live sessions
| Worker | 10 min | 24 h | Shares · 24h | Stale % | Reject % | Last share |
|---|---|---|---|---|---|---|
| — | ||||||
online · dropped <24h — check the rig · offline
P-04 Payout controls one gate · amount · Tor or slatepack
Why does my rig password matter?
It can't be used to steal your coins. A Tor payout goes only to this address's own wallet and a slatepack is encrypted to this address, so there is nowhere else for the money to go. What the gate stops is a stranger reading the public leaderboard and triggering payouts you never asked for — each one burns a pool-paid network fee and force-moves coins you meant to leave alone.
A password is your backup when your IP changes. IP proof breaks quietly: an ISP re-lease, a router reboot, switching to mobile data, or moving the rig all give you a new one. Only your last two are kept, so once yours has rotated twice you cannot prove ownership until you mine a fresh share from the new address. A password you chose survives all of that.
Why factory defaults are refused. A default like x,
xxxx or 123 isn't a secret — thousands of rigs ship with the
same value, so accepting it would hand one skeleton key to every account using it. Same
for a single repeated character of any length, and for anything under 8 characters
(short enough to guess offline). Those are never recorded, and the address keeps working
on IP proof alone.
Setting one. Put any private 8–128 character string in your miner's pool password field, use the same one on every rig, and it is recorded on your next accepted share. Changing it is safe — the last two are both accepted, so a rotation never locks you out.
Withdraw
Withdrawal fee — ツ · you receive — ツ
Sends the amount straight to this address's wallet over Tor — keep a wallet listener running. The pool checks your wallet is reachable before sending; if it isn't, the payout is declined and you can use Slatepack instead. Wallet reachability: checking… re-check
Generates a slatepack encrypted to your address — only your wallet can open it.
Steps: 1) generate, 2) receive it in your wallet, 3) paste the response to finalize.
Delivers the payout straight into your Goblin wallet over Nostr — no Tor listener, no copy/paste. Because this rail pays a username (not this address's own wallet), you must register the destination once and wait out a short security window before the first payout. This gives you time to notice and undo a hijack: if someone who guessed your gate registers their own Goblin name, re-registering yours resets the clock and evicts theirs.
A flat withdrawal fee of — ツ is deducted from the amount you request, on every method. It covers the Grin blockchain transaction fee, which on Grin is paid by the sender and is charged by transaction size rather than by the amount sent — so it costs the same whether you withdraw 25 or 2500 ツ. Fewer, larger withdrawals therefore cost you less in total. It is a flat rate, not a pass-through of the exact chain fee: the real fee paid on every payout is published on the payments page. One payout at a time — while one is in flight it shows above with its status. Nothing gets stuck: a payout that can't be delivered returns to your balance automatically once its retry or expiry window passes. There's no manual cancel (a payout that looks failed can still land), and after one is returned a short cooldown applies before your next request on any method.
P-05 Account details
- Status—
- First seen—
- Member for—
- Last seen—
- Total shares submitted—
- Blocks found—
- Last share—
- Pending withdrawal—
- Payouts made—
- Minimum payout (pool)—
- Withdrawal fee—
| Period | GRIN | BTC | USD |
|---|---|---|---|
| Last 60 minutes | — | — | — |
| Last 24 hours | — | — | — |
| Last 7 days | — | — | — |
| Last 30 days | — | — | — |
P-06 Ledger — money in row detail kept 60 days ·
Block rewards (PPLNS), contest bonuses, giveaways and returned payouts. 20 entries per page — full history is kept forever.
| When | Event | Amount | Balance after |
|---|---|---|---|
| — | |||
P-07 Ledger — money out row detail kept 60 days ·
Payouts to your wallet, voluntary donations (donateNN worker tag) and orphan clawbacks. 20 entries per page — full history is kept forever.
| When | Event | Amount | Balance after |
|---|---|---|---|
| — | |||
P-08 Withdrawal history every payout, kept forever ·
Your payout requests only — no donations or clawbacks. Unlike the ledgers above (row detail kept 60 days), this list goes back to your first payout. Export the full history as CSV for your records.
| Requested | Method | Status | Amount | Fee | Confirmed | Proof |
|---|---|---|---|---|---|---|
| — | ||||||