Timeline

From 2025-01-31 to 2026-10-06, the day this page was built: 12 key milestones, and 30 in the detailed view. Each is dated from a record when the page is built — a commit, a pull request on GitHub, a run directory, a line in a run's own log, a row of a run's own criteria table — except testimony, which is dated by the person who gave it and says so. What is planned comes last, with no date.

Timeline, high-level view, 2025-06-09 to 2026-10-06 12 milestones in order along a vertical line, alternating sides, then what is planned; spaced by order, not by time. A pill marks each new year and a break marks each gap of more than a month. The same list follows as text. 2025 3 months later 7 weeks later 2026 3 months later 5 weeks later 2 months later 3 months later Next ASIC grant request approved · 2025-06-09 · per Ronald Bynoe ASIC grant request approved 2025-06-09 · per Ronald Bynoe Received the grant of 54,000 ASICs · 2025-09-10 · per Ronald Bynoe Received the grant of 54,000 ASICs 2025-09-10 · per Ronald Bynoe Crowdfunding campaign launched publicly, on the 17th Whitepaper Day · 2025-10-31 · per Ronald Bynoe Crowdfunding campaign launched publicly, on the 17th Whitepaper Day 2025-10-31 · per Ronald Bynoe SatoshiStarter's first commit · 2026-02-03 03:52Z SatoshiStarter's first commit 2026-02-03 03:52Z First pull request to upstream Mujina · 2026-03-07 00:10Z · upstream #37 First pull request to upstream Mujina 2026-03-07 00:10Z · upstream #37 Revised pull request · 2026-04-04 05:24Z · upstream #53 Revised pull request 2026-04-04 05:24Z · upstream #53 Restacked as four pull requests · 2026-06-11 05:35Z · upstream #68–#71 Restacked as four pull requests 2026-06-11 05:35Z · upstream #68–#71 First run of Mujina on the RDS · 2026-09-15 03:40Z · MJ-BAUD-01 · run 20260915T034026Z First run of Mujina on the RDS 2026-09-15 03:40Z · MJ-BAUD-01 First single-board run · 2026-09-22 20:53Z · MJ-HASH-01 · run 20260922T204923Z First single-board run 2026-09-22 20:53Z · MJ-HASH-01 First pool-accepted share · 2026-09-23 02:37Z · MJ-HASH-01 · run 20260923T022940Z First pool-accepted share 2026-09-23 02:37Z · MJ-HASH-01 First three-board run · 2026-09-23 15:53Z · MJ-HASH-05 · run 20260923T154655Z First three-board run 2026-09-23 15:53Z · MJ-HASH-05 First two-hour run · 2026-09-28 14:57Z · MJ-HASH-07 · run 20260928T124110Z First two-hour run 2026-09-28 14:57Z · MJ-HASH-07 Today · 2026-10-06 Today 2026-10-06 48-hour run · planned, no date · #82 #137 48-hour run planned, no date · #82 #137 Calibration by Mujina · planned, no date · #158 #87 #147 Calibration by Mujina planned, no date · #158 #87 #147
Spaced by order, not by time: each milestone follows the one before it, on alternating sides of the line. A pill marks each new year, and a break in the line marks a gap of more than a month and says how long it was. Times are UTC. Hollow amber markers are testimony, dated by the person who gave it; dashed rings after today are planned, with no date. The drawing alone is also an SVG file: high-level, detailed.

Milestones, in order

  1. BZM2 ASIC grant program announced — per Ronald Bynoe, given 2026-09-28
  2. Applied for the ASIC grant — per Ronald Bynoe, given 2026-09-28
  3. ASIC grant request approved — per Ronald Bynoe, given 2026-09-28
  4. Hardware development contracted — per Ronald Bynoe, given 2026-09-28
  5. Pitched a co-branded miner to an education partner — per Ronald Bynoe, given 2026-09-28
  6. Artwork development contracted — per Ronald Bynoe, given 2026-09-28
  7. Grant recipients made public — per Ronald Bynoe, given 2026-09-28
  8. Received the grant of 54,000 ASICs — per Ronald Bynoe, given 2026-09-28
  9. Planned an all-or-nothing crowdfunding campaign — per Ronald Bynoe, given 2026-09-28
  10. Approved by a partner to launch a co-branded MiniMiner — per Ronald Bynoe, given 2026-09-28
  11. Initial bill of materials completed for the single-ASIC design — per Ronald Bynoe, given 2026-09-28
  12. Design support agreed for current and future designs — per Ronald Bynoe, given 2026-09-28
  13. Crowdfunding campaign soft launch — per Ronald Bynoe, given 2026-09-28
  14. Crowdfunding campaign launched publicly, on the 17th Whitepaper Day — per Ronald Bynoe, given 2026-09-28
  15. Pitched the campaign to mining networks, events and forums — per Ronald Bynoe, given 2026-09-28
  16. Pitched in a keynote at a mining conference — per Ronald Bynoe, given 2026-09-28
  17. SatoshiStarter's first commit
  18. First pull request to upstream Mujina — upstream Mujina #37
  19. Revised pull request — upstream Mujina #53
  20. Restacked as four pull requests — upstream Mujina #68, #69, #70, #71
  21. RDS enablement work begins — the first commit of the RDS work (ee4ca8a), before the first run a case record claims (2026-09-15)
  22. First run on the unit — MJ-OBS-02, run 20260915T014110Z
  23. First run of Mujina on the RDS — MJ-BAUD-01, run 20260915T034026Z
  24. First contact: Mujina observes a live chain — MJ-OBS-01, run 20260915T051503Z
  25. First bring-up: Mujina takes over an energised board — MJ-BRING-01, run 20260922T191903Z
  26. First single-board run — MJ-HASH-01, run 20260922T204923Z
  27. First pool-accepted share — MJ-HASH-01, run 20260923T022940Z. Mujina's first pool-accepted share on BZM2 silicon
  28. First three-board run — MJ-HASH-05, run 20260923T154655Z
  29. First thermal steady state — MJ-HASH-06, run 20260923T162332Z
  30. First two-hour run — MJ-HASH-07, run 20260928T124110Z. Mujina mines on all three RDS hashboards for two hours
  31. Planned, no date 48-hour run — roadmap item endurance, tracked privately as #82 #137
  32. Planned, no date Calibration by Mujina — roadmap item operating-point, tracked privately as #158 #87 #147

Mining runs, and the blocks each covered

Every run in which Mujina received work from the pool: the day it ran, the span it mined over, and the blocks found in that span, each of which it was mining toward when it was found. Read from each run's own record of the chain tip at the start and the end of that span, looked up once from two independent public block explorers, which agree on 14 of these 26. Tips are placed by block header time, which miners set; ≈ marks a run where the pool's own new-block notices count differently, so a block at one edge of the span may sit on the other side of it.

Case, runDay, span (UTC) Blocks covered
MJ-HASH-0120260922T204923Z2026-09-22
20:53–21:03Zthe hold		≈ 968,182
MJ-RUN-0120260923T005501Z2026-09-23
01:01–01:02Zthe hold		none; mining toward 968,204
MJ-HASH-0120260923T020342Z2026-09-23
02:10–02:20Zthe hold		968,214
MJ-HASH-0120260923T022940Z2026-09-23
02:36–02:46Zthe hold		968,216–968,217
MJ-HASH-0220260923T142124Z2026-09-23
14:30–14:40Zthe hold		968,283–968,284
MJ-HASH-0320260923T145454Z2026-09-23
15:04–15:14Zthe hold		≈ none; mining toward 968,286
MJ-HASH-0420260923T151958Z2026-09-23
15:26–15:36Zthe hold		968,287
MJ-HASH-0520260923T154655Z2026-09-23
15:53–16:03Zthe hold		968,289–968,290
MJ-HASH-0620260923T162332Z2026-09-23
16:30–17:05Zthe hold		≈ 968,294
MJ-POOL-0120260923T212946Z2026-09-23
21:38–21:58Zthe hold		≈ none; mining toward 968,324
MJ-HARN-0120260924T123917Z2026-09-24
12:50–12:55Zthe hold		≈ none; mining toward 968,396
MJ-HARN-0220260925T011219Z2026-09-25
01:23–01:28Zthe hold		none; mining toward 968,479
MJ-HASH-0720260925T014028Z2026-09-25
01:52–02:29Zthe hold's start to the stop; it did not complete		968,481–968,482
MJ-HASH-0720260928T124110Z2026-09-28
12:57–14:57Zthe hold		969,000–969,011
MJ-HASH-0820260928T155333Z2026-09-28not looked up yet
MJ-HASH-0920260929T231425Z2026-09-29not looked up yet
MJ-HASH-0920260930T003548Z2026-09-30not looked up yet
MJ-HASH-1020260930T042854Z2026-09-30not looked up yet
MJ-HASH-1020260930T143900Z2026-09-30not looked up yet
MJ-HASH-1020260930T153155Z2026-09-30not looked up yet
MJ-HASH-1120261001T014554Z2026-10-01not looked up yet
MJ-HASH-1220261001T085812Z2026-10-01not looked up yet
MJ-HASH-1320261001T192725Z2026-10-01not looked up yet
MJ-STOP-0120261006T014121Z2026-10-06not looked up yet
MJ-HASH-1420261006T023659Z2026-10-06not looked up yet
MJ-STOP-0120261006T054041Z2026-10-06not looked up yet

How each date is found

RDS enablement work begins
RDS enablement work begins: the earlier of the first commit of the RDS work (under docs/rds or tools/rds, by author date) and the first run any case record claims. Here: the first commit of the RDS work (ee4ca8a), before the first run a case record claims (2026-09-15).
Testimony
Testimony: no commit, run or log records it. It is dated by the person who gave it and shown as theirs; an entry with no date is listed as awaiting one and never drawn.
SatoshiStarter's first commit
The first commit of SatoshiStarter, a private repository, so it is named here and not linked. Read from GitHub once by tools/rds/timeline-github.py and kept in docs/rds/timeline-github.tsv; the page build never asks GitHub.
First pull request to upstream Mujina
The first pull request of this work to upstream Mujina, at its creation time on GitHub. Read from GitHub once by tools/rds/timeline-github.py and kept in docs/rds/timeline-github.tsv; the page build never asks GitHub.
Revised pull request
The revised pull request to upstream Mujina, at its creation time on GitHub. Read from GitHub once by tools/rds/timeline-github.py and kept in docs/rds/timeline-github.tsv; the page build never asks GitHub.
Restacked as four pull requests
The four pull requests the work was restacked into upstream, at the earliest of their creation times on GitHub. Read from GitHub once by tools/rds/timeline-github.py and kept in docs/rds/timeline-github.tsv; the page build never asks GitHub.
First run on the unit
The earliest run directory any case record claims: a run under a case's own evidence directory, or one a record cites by path.
First run of Mujina on the RDS
The earliest run in which Mujina's own log records its daemon starting on the unit, at that line's time, whether or not it then reached a board.
First contact: Mujina observes a live chain
The earliest run of MJ-OBS-01 whose own window log reports a board attached to Mujina, at that line's time. A run in which no board attached (a busy port, a gate that refused it) is passed over.
First bring-up: Mujina takes over an energised board
The earliest run of MJ-BRING-01 whose own window log reports a board attached to Mujina, at that line's time. A run in which no board attached (a busy port, a gate that refused it) is passed over.
First single-board run
The earliest run in which Mujina held exactly one chain and received work from the pool, dated at the start of its hold.
First pool-accepted share
The earliest “First share accepted.” in any run's own Mujina log, at that line's time (the log's clock, dated by the run's window log).
First three-board run
The earliest run in which Mujina held all three chains, received work and had a share accepted, dated at the start of its hold.
First thermal steady state
The earliest run whose own criteria table judges its steady-state criterion (H3) a pass, dated at the end of the hold it is judged over.
First two-hour run
The earliest mining run whose window log reports a hold of two hours complete, at that line's time.
Planned
A roadmap item that has not happened yet. It is drawn after today with no date, and names the roadmap item, epic and issues it is tracked under.

Generated 2026-10-06T06:39:25Z from commit d73caa5. Status, dates and case ids only.