Once the miner runs, open the dashboard at http://localhost:8881/. It shows what this rig is doing, what the DagCore pool counts and pays for it, and the rig's own hardware, log and settings. Set OPEN_BROWSER=1 in config.env to have it open by itself when the miner starts. Reading needs no token; changing a setting needs the control token (see below). By default the page is on localhost only.
C:\DAGCore. Everything stays in that folder.config.env.example in Notepad, set WALLET to your payout address, and save it as config.env (no .txt).start.bat. It runs the miner as administrator, which the GPU power limit needs. A console window opens and mining begins.autotune.json, and later starts use it at once. If you close the window before it ends, nothing is saved and it starts again next time. AUTOTUNE=0 in config.env turns it off.OPEN_BROWSER=1 in config.env to have it open by itself at each start.api-token in the folder, and printed in the console the first time. See Settings below.Open http://localhost:8881/. Reading needs no token; changing a setting needs the control token.
Top left is the pool and chain. Top right are two buttons.
Settings jumps to the Settings card and opens it.
Pause / Start pauses or resumes mining. On pause the pool connection is closed and the card turns green with a Start button; Start reconnects. It needs the control token; without one it sends you to Settings to paste it. On Windows it needs no administrator rights (only the power limit does).
Now — the rig's own current hashrate, the same figure the miner prints and the Settings hardware card shows. Under it, in small print, the pool's own 10-minute estimate for your address, marked est.
Last 1 h — the rig's own hashrate averaged over the last hour, from samples this page keeps (one every 30 s, kept 24 h in your browser). It needs about 20 minutes of the page being open before it first appears; after that it survives a reload.
Pool · last 24 h (est.) — what the pool estimates for your address over a day, from accepted shares. This is an estimate and noisier over short spans; over a day it settles, and it is the figure your pay follows.
Block height — the current chain height, from rpc.dagcore.net.
Why Now and the pool estimate differ: the miner measures the hashes it computes (steady); the pool estimates from accepted shares (statistical, noisy over minutes). Over a day the two are close.
A folded card with the pool-wide figures, the same as on dagcore.net: pool status, pool hashrate, miners online, blocks found and BDAG paid. Its summary line carries the headline numbers while it is closed.
Inside are two charts: the pool's hashrate over time (1h / 24h / 7d), and BDAG paid to all miners per hour over the last day.
The address this rig mines to, with a link to the block explorer.
Unpaid balance — BDAG earned and not yet paid: what is carried from earlier windows, plus your estimated share of the payout window still open (marked est. while it is an estimate). A line under it says what will happen next (paid shortly, kept because it is under the minimum, or nothing due yet).
Status — Mining when the pool has seen a share from you in the last 5 minutes; the card's border then pulses green. Otherwise it shows how long since the last share.
Total paid, PPLNS share (your weight in the last block), Next payout window (when it closes and your share so far), Last accepted share, Last active (when the pool last heard from the rig).
A chart of the pool's hashrate estimate for your address, over 1h / 6h / 12h / 24h / 7d (12h by default). The 6h and 12h views are cut from the 24h series.
The bars are the shares the pool counted in each interval: accepted, with any stale ones stacked on top. Stale shares earn nothing; a few are normal, many point to a slow link to the pool.
The dashed line is the rig's own reading over the same span, from the samples this page keeps while open — so you can see the miner's steady rate against the pool's noisier estimate.
Every payout to your address, ten to a page. The List tab shows the amount, your weight in that payout, its state (confirmed once it has the pool's required confirmations) and a link to the transaction. Use From / To to filter by a date range.
The By day tab summarises payouts per day as a bar chart and a table; click a day (bar or row) to open that day's payouts in the list. The same data, page by page or by day, is also on dagcore.net.
A folded card with the pool's terms: the scheme (PPLNS), the fee, how often it pays, the minimum payout (smaller amounts are carried, not lost), and the stratum address. The login there is the bare payout address; address.worker is rejected.
A folded card, opened by the Settings button. It holds the rig's hardware and its own controls.
Hardware cards — one per GPU (its hashrate, temperature, load, power draw and efficiency), one for the CPU, and one for the miner (version, mode, difficulty, current job, wallet). These are measured on this machine; the pool never sees them.
Controls (need the control token, pasted once and kept in this browser): the wallet, pool, port and CPU threads; GPU power limit; core and memory clock locks and offsets; GPU intensity; and Pause/Resume. Changing wallet/pool/threads saves to config.env and restarts the miner.
On Windows: the power limit needs the miner started as administrator (use start.bat), or its control shows a note instead. The driver refuses clock offsets from the miner on Windows — the card points you to MSI Afterburner (NVIDIA) or AMD Adrenalin instead. These are not faults; they are how Windows works.
A folded card with the miner's latest console lines on a black console, newest last. The summary line shows how many lines and when the newest one was written.
The page is one framed column on a darker backdrop, with a faint fractal texture behind it. Cards pulse gently while the rig is mining. It reads the same on a phone. Nothing here is a promise of earnings; the pool's figures are the ones your pay follows.