First batch = the only tasks PRISM speed counts: they run on the servers in each miner's order below.
Later batches only need to finish: send them to servers or to a DigitalOcean function region (falls back to the servers when the region is busy).
loading…
Servers
Routers
loading…
Function regions (DigitalOcean)
loading…
Control
Miner priority
#1 gets the fastest servers and races its first batches on a second server (the planners apply it).
loading…
Per-miner settings
Applied live by each orch box's planner (within ~30 s) -- no restarts.
Racers: connections per task (blank = the box default). Planner: the per-wave server allocation by priority (off = only logged).
Discovery: new kinds are tried on a different region per miner, then everyone uses the best.
loading…
My PRISM rank
UID
loading…
Wallet & SN105
loading…
Epoch trend
loading…
Recent transfers each wave is a new task · scroll · click a row
loading…
Recent alerts
loading…
Slowest task per wave a batch scores its slowest chunk
loading…
Compare miners
vs
loading…
Expected PRISM (rebuilt)
loading…
Rebuilt from BeamCore's own transfer records with the published formula: one speed sample per transfer = your first batch's slowest task, averaged with a 1-hour half-life (the last hour carries ~50%, the hour before ~25%); speed score = 0.2–1.0 between the network's slowest and fastest miner; final = (0.4 × speed + 0.6 × reliability) × readiness × penalty (those three taken from BeamCore). BeamCore's own figure in brackets — if they match, the formula is the one we are playing.
Batch health
loading…
A batch's verified bandwidth is its slowest chunk — one throttled chunk sinks the whole batch. "Chunks on shared transfers" = how many chunks BeamCore gave each miner on the same transfers (share follows PRISM). Last 10 transfers, refreshed every 5 min.
Per-task comparison
pick a transfer above
PRISM's speed score uses only your first batch of each transfer, at its slowest task (later batches count only with 10+ tasks), averaged over transfers with a 1-hour half-life — so the first row matters most; the average does not count directly. Verified bandwidth lands a few minutes after a task completes — raw figure until then.
Router health
loading…
Dashboard serverthis box, not the miners
loading…
Router utilization — all miners
open the Fleet tab to load
Fleet (12h rolling)
–
tasks
–
passed
–
late
–
failed
–
avg wire mbps
–
avg prism mbps
Regions
Provider
Best & worst performers (all kinds)
loading…
Failed tasks — all miners
loading…
Task kinds — tap to edit servers
loading…
Load by region
loading…
Inspect a miner
Pick any UID on SN105: chain data, BeamCore's PRISM numbers, recent transfers and its epoch MiB history.
Settings
Miners
The name shown for each miner (hotkey) in the switcher at the top, and the miners' priority: #1 gets its region's fastest routers and races its first batches on a second router (the planner on each orch box applies it before the next wave). Needs the admin login.
loading…
Server labels
Give a server a name — it replaces the IP everywhere on this page. Reset clears just that server's stats.
loading…
Alerts on this device
Get a notification when a router goes down, tasks fail, a wave is throttled far more than the top miners, or your tier changes. On iPhone, first add this page to the home screen (Share → Add to Home Screen) and open it from there.
Admin log
log in to see the admin log
Danger zone
Clears all recorded speed/fail-rate stats and starts fresh counts. Does not touch which servers are live for each task.