Epoch
230

Latest epoch with ingested solutions

Solution Threshold
4,000

Epoch 230, read from our node (GetSystemInfo). A solution is valid when its error score ≤ threshold.

Solutions Collected
271,916

Epoch 230 so far · ingestion in progress

Unique Submitters
1,518

Distinct identities that submitted a scored solution

Best Claimed Score
3,545

Lowest error count seen so far (lower is better); miner-declared, node-verified

Solution Ingestion by Epoch

Mining solutions are transactions to the zero address (inputType 2, 1M+ qus deposit). The claimed error score is part of the transaction payload. BPP-9000 scoring is active since epoch 224 — earlier epochs use a different algorithm and are intentionally not collected.

Epoch Solutions Submitters Best claimed score Tick range scanned Scan lag (ticks) Last update (UTC)
230 271,916 1,518 3,545 79,300,042 – 80,041,942 676 2026-09-14 08:42:42
229 400,001 1,552 3,460 77,700,365 – 79,146,843 895,775 2026-09-09 12:01:47
228 155,625 3,052 3,508 76,551,064 – 77,560,787 2,481,831 2026-09-02 23:19:14
227 3,255 1,356 3,695 75,241,785 – 76,481,998 3,560,620 2026-08-26 12:18:53
226 5,937 1,228 3,696 73,857,166 – 75,241,779 4,800,839 2026-08-26 16:19:28
225 52,482 1,240 3,713 72,065,100 – 73,857,160 6,185,458 2026-08-28 05:01:57
224 21,855 1,144 3,725 70,642,220 – 72,065,095 7,977,523 2026-08-28 19:42:09

Epoch Boundary Balance Snapshots

Per-computor reward payouts are protocol-level balance emissions and are not exposed by any public API. We reconstruct them as the balance difference of all 676 computors across each epoch boundary (net of visible transfers). pre = last snapshot before the boundary, post = first snapshot after it. History starts 2026-08-25 — earlier boundaries cannot be backfilled.

Epoch Phase Rows Computor seats Balance valid at ticks Taken (UTC)
230 pre 676 / 676 676 79,303,498 – 79,305,075 2026-09-09 13:01:10
229 pre 676 / 676 676 79,132,225 – 79,143,567 2026-09-09 11:35:39
229 post 676 / 676 676 79,302,102 – 79,305,089 2026-09-09 13:01:16
228 pre 676 / 676 676 76,552,886 – 76,555,184 2026-08-26 13:03:08
228 post 676 / 676 676 77,768,523 – 77,771,103 2026-09-02 21:06:35
227 pre 676 / 676 676 76,365,686 – 76,478,254 2026-08-26 11:29:37
227 post 676 / 676 676 76,552,124 – 76,572,824 2026-08-26 15:44:44

Solution Threshold History

The validity threshold is a per-epoch value set by network operators and can change mid-epoch. It is read hourly from our own node; every observed change gets its own row.

Epoch Threshold First seen (UTC) Last confirmed (UTC)
230 4,000 2026-09-09 13:52:12 2026-09-14 07:52:12
229 4,000 2026-09-02 21:52:12 2026-09-09 11:52:12
228 4,000 2026-08-26 13:50:24 2026-09-01 03:29:51
227 3,838 2026-08-25 20:04:09 2026-08-26 11:50:24

Data Provenance

All figures on this page are derived exclusively from data we ingest ourselves: solution transactions from the public Qubic archive (rpc.qubic.org), the solution threshold from our own Qubic lite node, and balance snapshots from the public balance API. Claimed scores are declared by miners and verified by network nodes before the submission deposit is returned; independent re-scoring of a sample with the canonical scorer is planned. Solution data covers epoch 224 onwards (BPP-9000 activation) — older epochs used a different scoring algorithm and are not comparable.