Miner-side accepted-registry snapshot download + publish integration#25
Merged
Conversation
SparkDistill publishes accepted_registry_snapshot.jsonl on sparkproof-mining with sha256 pins in mix_manifest.json. Miners can now download and verify that snapshot in SparkProof (sparkproof-download-registry-snapshot) and pass it to the release gate via --registry-snapshot or --mining-repo on publish.
- Mock huggingface_hub via sys.modules so CI passes without publish extra - docs/MINER_GUIDE.md with registry dedupe workflow - README links to miner guide; CHANGELOG [0.1.2]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SparkDistill #119 publishes
accepted_registry_snapshot.jsonlongittensor-model-hub/sparkproof-miningand pinsaccepted_registry_snapshot_sha256inmix_manifest.json. SparkProof already accepted--registry-snapshotat release-gate time, but miners had to manuallyhuggingface-cli downloadand verify the sha256 themselves.This PR adds the miner-facing half of that workflow directly in SparkProof:
sparkproof/triton_dataset/registry_snapshot.py— download mix_manifest + snapshot from HF, verify sha256/row pinssparkproof-download-registry-snapshot— CLI +scripts/download_registry_snapshot.shsparkproof-publish-dataset --mining-repo— auto-download verified snapshot and pass to release gate (bare flag → canonical mining repo)--registry-snapshot+--mining-repotogether verifies a local file against live pinsBuilding the snapshot from
datasets/registry.jsonlstays in SparkDistill (eval.export_registry_snapshot) — maintainer/CI only.Miner usage
Test plan
uv run pytest tests/test_registry_snapshot.py— 5 passeduv run ruff checkon changed files — clean