v0.1.2 — Hopper mining, per-arch frontiers, trustless dataset verification
Hopper joins Blackwell on both mining tracks, per-architecture frontiers replace the shared Triton scoreboard, and dataset verification closes the last userland trust gaps (NRAS JWKS + Intel TDX). Architecture-scoped exact dedupe and a refreshed canonical mining mix (174→178 rows) land in the same release window.
Highlights
Hopper + per-architecture frontiers ([#104], [#109], [#120])
- Dataset track accepts Hopper H100/H200 alongside Blackwell; registry entries carry
gpu_architecture. - Separate Blackwell and Hopper frontier buckets in
runs/frontiers.json. - First verified Hopper training BASELINE merged ([#120], magicrails-hopper-v2 on H200).
Architecture-scoped dedupe ([#133], SparkProof [#26])
- Exact dedupe keys prompt matches by
gpu_architecture— same prompt on Blackwell vs Hopper is a fresh row. - Canonical
sparkproof-miningrepublished: 174 → 178 rows ([#134]).
Canonical mining dataset + miner tooling ([#89], [#97], [#119], [#132])
- Every training PR trains on the pinned
sparkproof-miningsnapshot. sparkproof-publish-dataset --mining-repoandaccepted_registry_snapshot.jsonldocumented ([#132]).- Fair dataset labels from canonical-mix
rows_selected, not raw bundle counts ([#116]).
Trustless dataset verification ([#53], [#122])
- Dataset gate always runs
sparkproof-verify --online(NVIDIA JWKS). - New bundles require Intel TDX bound to the dataset nonce.
Full changelog: CHANGELOG.md