SPEARMINT SPMTC

Spearmint/Developer docs/Dashboard

Developer documentation · Spearmint Mining

Mining dashboard wireframe

One screen, keyed by payout address, showing what the hardware is doing and what the pool has calculated and paid. Every label is mining vocabulary. The controls a financial account would have are absent because the things they would control do not exist.

Pre-launch · design document Figures illustrative
SPEARMINT MINING · payout address spmtc1q4x…9k2v · worker filter [ all ▾ ] [ export CSV ]
Hashrate
1.42 TH/s
5 min 1.42 · 1 h 1.39 · 24 h 1.40 TH/s
Valid shares · 24 h
8,214
stale 41 (0.5%) · rejected 3
Workers online
3 / 3
last share 12 s ago
Pending mining reward
3.8172 SPMTC
This figure is an accounting estimate of mining rewards awaiting distribution. It is not a deposit account and not a hosted cryptocurrency wallet.
Last payout
5.2041 SPMTC
txid 7f3a…c91e · 2026-09-12 00:00 UTC · paid
Estimated reward per day · estimate
≈ 6.1 SPMTC
From current hashrate and 7-day pool luck. Not a promise; varies with network difficulty and blocks found.
Workers
namehashratelast sharevalidstalerejected
rig-010.48 TH/s12 s2,790141
rig-020.47 TH/s20 s2,731152
desk0.47 TH/s9 s2,693120
Recent blocks · pool
heightstatusyour share
418,220pending 37/1000.2130
418,104mature0.2087
417,991orphaned
417,880mature0.2144
Payout history
run time (UTC)amountnetwork fee sharetxidstatus
2026-09-12 00:005.2041 SPMTC0.00047f3a…c91epaid
2026-09-11 00:006.0388 SPMTC0.0004b21d…0a77paid
2026-09-10 00:005.9902 SPMTC0.0005e9c4…51f0paid
Spearmint Mining will never ask for your private key or recovery phrase.

Wireframe. Figures are illustrative; the pool is not open. No login, no balance, no withdraw, no send, no address-change control — see sections 01 and 02.

01 Labels and why

Each label, and what it deliberately is not
LabelNot calledReason
Payout addressAccount, username, walletIt is an address the miner controls; the pool holds nothing for it.
Hashrate / Valid shares / Workers onlinePlain mining statistics.
Pending mining rewardBalance, available, fundsAn allocation awaiting the next run, with the standing explanation in the tile.
Last payoutLast withdrawalThe pool sent it; the miner did not request it.
Estimated reward per day · estimateEarnings, income, yield, ROIA projection from hashrate and luck, labelled as such in the label itself.
Recent blocks · your shareTies every reward to a block the pool found.
Payout historyTransactions, withdrawals, statementA list of distributions with txids the miner can verify on-chain.

The full vocabulary is on the terminology page. "Balance", "Withdraw", and "Send" do not appear anywhere on this screen.

02 What is intentionally absent

  • No withdraw button. Payouts are automatic on the published schedule. A button would imply the miner can pull value out on demand from something the pool holds.
  • No transfer or send. There is no way to move an allocation to another address or person.
  • No address change. Rewards go to the address the shares were mined under. To use a different address, mine with it.
  • No login. The screen is a public read by address. Registered emails are not shown.
  • No fiat figures. Amounts are in SPMTC. No price feed, no conversions.
  • No deposit address. Nothing on this screen accepts anything.

03 Data sources per tile

Where each figure comes from
TileSourceRefresh
Hashrateshares: difficulty-weighted valid shares over 5 min / 1 h / 24 h windows30 s
Valid / stale / rejectedshares.result counts, 24 h30 s
Workers onlineworkers.last_seen within 10 min30 s
Pending mining rewardΣ reward_allocations.net where block status = mature and not yet in a payouts rowOn block maturity and after each run
Last payoutMost recent payouts row for the address, joined to payout_runs.txidAfter each run
Estimated reward per dayAddress hashrate ÷ network hashrate × expected daily block rewards × 7-day pool luck × (1 − fee)5 min
Recent blocksblocks joined to the address's reward_allocationsOn block find / status change
Payout historypayouts for the address, newest firstAfter each run

All tiles are served by the read-only stats API from a node and database replica; nothing on this screen can write. Schema on the architecture page.

04 Empty and error states

  • Address never seen. "No shares have been received for this address. Check the worker login is <address>.<worker> and that the address passes checksum." Link to the mining page. No tiles shown.
  • Invalid address. "That is not a valid spmtc address." Checked client-side and again by the API.
  • Pending mining reward decreased. When an orphan reverses allocations, the tile shows a line: "Decreased by 0.2130 SPMTC — block 417,991 was orphaned by the network. Nothing from an orphaned block is paid." The block row shows "orphaned".
  • Payout failed. Status "failed — retrying" with the next run time; never a silent gap.
  • Payout run paused. A banner: "Payout runs are paused while the node resolves a chain reorganisation. Allocations are unaffected." Link to the network page notice.
  • API unavailable. Cached figures shown with an "as of" time, greyed; never a blank zero that could be misread as a reset.
  • Blocked jurisdiction. A plain page stating the service is unavailable from that location, linking the Sanctions Policy.

05 Accessibility notes

  • Tiles are <section>s with headings; tables have <caption> and scoped headers; the address is in a landmark labelled "Payout address".
  • Live figures update via aria-live="polite" regions, throttled so screen readers are not flooded by 30-second refreshes.
  • Status is never colour-only: "pending", "mature", "orphaned", "paid", "failed — retrying" are text.
  • Contrast meets WCAG AA on the light theme; the standing explanation is body text, not small print.
  • Everything works without JavaScript for a one-off render; JavaScript only adds refresh and the CSV export.
  • Keyboard: worker filter and export are real controls; tables scroll horizontally in their own container at narrow widths.