Skip to content
NewTHOR launches Talo Robotics, a human demonstration and labelling firmVisit Talo

Documentation / Start here

03 / 19

How SN112 works

Buyers commission labelling, qualified workers produce it, and verification and buyer acceptance decide what is paid.

On this page

SN112 is THOR's subnet on Bittensor. THOR Data takes a buyer's brief, splits the work into units, funds the full worker reward from treasury-held alpha before production starts, and pays workers in two stages: when a unit passes verification and when the buyer accepts it. The buyer pays for the units they finally accept. This page is the reference summary; each section links to the full explanation.

Who does what

  • Buyer: agrees the brief (source material, permitted use, output schema, acceptance criteria and commercial terms), reviews delivered batches and pays for the units finally accepted.
  • THOR Data (operating as Talo Robotics): scopes the order into batches, reserves the full budgeted worker reward from treasury-held alpha, coordinates production and verification, and delivers accepted output. It earns a commercial spread for qualifying suppliers, coordinating production and assuring quality.
  • Workers and labelling firms: complete leased assignments against the fixed specification. A firm can operate several miner UIDs; each worker's assignments and earnings stay with their worker account, even if an operator's UID changes.
  • Verification: structural gates, a vision-language model (VLM) content score against a frozen rubric, hidden gold tasks with human-checked answers, and overlapping cross-checks between workers. Authorised validators will have sample access under each project's permissions.
  • SN112: the network layer, intended to coordinate and reward useful contribution. Commercial acceptance and network incentives follow separate rules.

How an order moves

  • 1. Agree the brief. Buyer and THOR fix the source material, schema, delivery format, acceptance criteria and commercial terms. The specification and review rubric stay fixed for assigned work.
  • 2. Calibrate. A small calibration batch lets the buyer check the task and output before main production.
  • 3. Reserve the reward. THOR sets aside the job's full budgeted worker reward from treasury-held alpha, including planned cross-checks. A job waits if its budget cannot be fully reserved.
  • 4. Produce. Work is split into units and leased to workers with a completion window. Workers label the material or correct model-generated pre-labels.
  • 5. Verify. Structural gates run first, then the VLM content score (q) against the frozen rubric. Hidden gold tasks and cross-checks add quality signals. Repeated or copied submissions earn nothing extra.
  • 6. First payment. The verification-linked portion is earned when a unit passes its checks. The worker keeps it even if the buyer later rejects the unit.
  • 7. Buyer review. The buyer accepts a batch, accepts part of it or returns units for correction within the review window. Rejections must cite the specification; disputed rejections receive sample review.
  • 8. Second payment. The acceptance-linked portion follows final buyer acceptance, and the buyer pays for the units accepted.
  • 9. Deliver. The buyer receives accepted labels with their verification and provenance records: the verified unit.

Who can take part

The current stage is a private beta with qualified, whitelisted labelling firms. After beta, labelling opens to permissionless participation within the Data stage. Future work is allocated by gold-task accuracy, buyer acceptance history and declared capacity; the first round is shared equally among qualified workers, and later rounds keep opportunities for newcomers.

Status

  • In place: SN112 on Bittensor, the private beta with qualified firms, and the contract reserve, whose balance is published on the revenue dashboard.
  • Planned: permissionless labelling after beta, published eligibility rules and whitelist review, and sample access for authorised validators.

Read more