TAO $223.70+2.6% 24h
24

Quasar

sn24Training & Fine-tuningWatch53Avoid20

QUASAR is a long-context foundation model and decentralized evaluation subnet built on Bittensor,

SILX-LABS/QUASAR-SUBNET/· pushed 2mo ago emissions paused reg. open repo idle
Emission
0
paused on chain
Alpha
0.0216
τ · mcap 86.4K
Top-slot payout
τ per winning epoch · live
Stars
13
live from the GitHub API
Primary language
Python
repo-reported
Last push
2mo ago
feeds the dormancy integrity signal
Topics
5
repo-declared tags

About the repo

what the project says about itself — the input for semantic labels

SILX-LABS/QUASAR-SUBNET/· pushed 2mo ago

QUASAR is a long-context foundation model and decentralized evaluation subnet built on Bittensor,

aibittensorcontext-windowllmtao

Reading this tab

scope of the data

Taonets fetches the repo's public metadata (description, topics, language, stars, last push) and the head of its README. Commit-count histories, contributor lists and release notes require the GitHub commits/releases endpoints, which the worker doesn't consume yet — those panels are coming with the ingest upgrade and are not simulated in the meantime.

README head

first lines of the default branch README, unedited

# Quasar Training

Quasar Training is the production training system for continuing Quasar model
pretraining on Bittensor. It coordinates independent miners, validators, and a
subnet-operated orchestrator so real training work can be assigned, verified,
merged, and converted into subnet weights.

Our goal is to complete more than **10T additional pretraining tokens** on
Quasar Preview through the largest decentralized model-training run we can make
practical, verifiable, and repeatable.

The current base model is **Quasar Preview**:

- Model source: [`silx-ai/Quasar-Preview`](https://huggingface.co/silx-ai/Quasar-Preview)
- Architecture: Quasar MoE
- Revision: `main`
- Mainnet subnet: `netuid 24`
- Network: `finney`

The orchestrator starts from a published Quasar Preview checkpoint manifest,
splits the trainable model tensors into 24 fragments, assigns training leases to
miners, pulls live fragment states during training, merges validator-approved
live fragments, and periodically releases updated Quasar checkpoints for future
miners and restarts.

## System Roles

- **Miner:** trains assigned Quasar data and uploads signed training artifacts.
- **Validator:** verifies miner work, writes signed verdicts, and publishes weights.
- **Orchestrator:** subnet-operated service that assigns work, merges accepted updates, and releases checkpoints.

Most participants run either a miner or a validator. The orchestrator is run by the subnet operator.

## Live Training Flow

```text
orchestrator publishes the active run and current Quasar checkpoint
miners discover the run, download checkpoint/data through grants, and train
syncer asks live miners for fragment_id = global_step % 24
miners upload signed live fragment claims for their current fragment state
validators verify live claims, tensor contracts, hashes, and eval quality
orchestrator merges only validator-approved live fragments
orchestrator immediately publishes the updated absolute fragment back to miners
validators publish Bittensor weights from accepted live merge events
after fragments 0..23 are covered, orchestrator releases a full checkpoint
```

Rounds are assignment leases and audit windows. End-of-job receipts remain useful
for telemetry and audit, but live validator-approved fragment merges are the
authoritative training and scoring path. Miners do not evaluate themselves.
Validators do not assign miner work, merge updates, or release checkpoints.
Miners and validators use signed manifests plus scoped grants, not broad
operator credentials.

## Rewards And Weights

Rewards are based on accepted live merge events, not miner self-reported speed,
loss, or GPU names. The validator scores recent accepted live work with decay so
old work cannot dominate the subnet forever. Invalid, stale, replayed, unsigned,
or tensor-mismatched live claims receive zero merge weight.

Fast hardware still matters because it can keep serving valid live fragments
while training. The validator only counts work that was pulled by the syncer,
verified against the frozen previous fragment state, independently evaluated,
and accepted into the live merge ledger.

## Model And Checkpoints

Quasar Training works on Quasar Preview checkpoints, not placeholder smoke
models. A live checkpoint must include:

- the Quasar checkpoint archive or safetensors weights,
- tokenizer/config files required to load the model,
- `quasar_parameter_contract.json` or equivalent checkpoint metadata listing
  the trainable tensor names.

The parameter contract is required because the orchestrator/syncer owns global
fragment state and must split checkpoint tensors into fragments without importing
the training model code. Miners and validators load Quasar for training and
evaluation; the orchestrator coordinates tensor artifacts and checkpoint release.

Checkpoint release is assembled strictly from the latest absolute fragment
states. Delta artifacts are kept for merge/debug visibility, but released
checkpoints are built from absolute fragment state plus the base checkpoint tree.
The main release is not partial: it requires live accepted coverage for all 24
fragments since the previous release.

Checkpoint release is operational recovery infrastructure for late joiners and
restarts. The paper-aligned hot path is live fragment sync: accepted fragment,
merge now, broadcast updated fragment, repeat. Miners should not wait for every
full checkpoint release before continuing live training.

## Mainnet Defaults

```bash
export QUASAR_NETWORK=finney
export QUASAR_NETUID=24
export QUASAR_S3_BUCKET=quasar-incentive-sn24-529337356998-us-east-1
export QUASAR_S3_REGION=us-east-1
export QUASAR_S3_ANONYMOUS=true
```

Leave `QUASAR_RUN_ID` unset for normal mining and validation. Miners and
validators discover the active run from the public current-run metadata.

## Install

Clone the repo on the machine, then run the script for your role:

```bash
git clone https://github.com/SILX-LABS/QUASAR-SUBNET.git /workspace/quasar-incentive
cd /workspace/quasar-incentive
bash scripts/install_miner.sh /workspace/quasar-incentive
bash scripts/install_validator.sh /workspace/quasar-incentive
```

## Mainnet Miner Quick Start

Current mainnet settings:

```bash
export QUASAR_NETWORK=finney
export QUASAR_NETUID=24
export QUASAR_S3_BUCKET=quasar-incentive-sn24-529337356998-us-east-1
export QUASAR_S3_REGION=us-east-1
export QUASAR_S3_ANONYMOUS=true
export QUASAR_WALLET_PATH=~/.bittensor/wallets
export QUASAR_WALLET_NAME=<miner-wallet>
export QUASAR_HOTKEY_NAME=<miner-hotkey>
```

Run:

```bash
quasar-incentive miner run \
  --worker-id "$(hostname)-0" \
  --owner-identity 5GE25P2qGpGmjzGipqezZckMvyR2mpcsJS387bbcpitNSfm5
```

Leave `QUASAR_RUN_ID` unset. The miner discovers the live run automatically.
Keep the miner updated to the latest release before starting a new worker; the
current protocol expects signed live fragment claims and live-control grants.

## Common Environment

Set these for the role wallet and subnet:
GitHub · Taonets