Network & evidence
Understand the relationship between submitted work, verified data, training, and emissions.
Protocol and workspace
Reliquary’s public protocol coordinates decentralized model-development work on Bittensor subnet 81. The platform provides discovery, private member workflows, and source-aware views of published protocol evidence.
A public network snapshot and a private customer order answer different questions. Network activity describes observed production. An order records the work requested by one account under a reviewed configuration.
Keep the stages separate
Read the active protocol’s outcome fields and published evidence for each stage. Do not infer a later stage from an earlier one.
| Stage | What the evidence establishes |
|---|---|
| Submission acknowledged | A request entered the submission path. |
| Accepted | The record passed the checks represented by that admission outcome. |
| Proof passed | The declared proof result passed for that record. |
| Selected for a batch | The record was chosen for a published batch. |
| Trainer consumed | Training evidence records use of the selected data. |
| Checkpoint published | A checkpoint artifact and revision were published. |
| Finalized allocation | Chain evidence records the applicable finalized allocation. |
Understand timestamps and source states
Producer observation time tells you when the source measured the data. Fetch time tells you when the platform retrieved a response. Retained-history collection time tells you when a collector stored it. These clocks can differ.
Live identifies a current usable source. Stale preserves an older observation with its original time. Unavailable means the source could not provide a usable observation. An empty collection can be valid and should not be treated as an outage.
Read money and capacity in their own context
Miner reward weights, finalized alpha emissions, provider price estimates, and customer service-credit balances use separate contracts. A network reward share is not a customer balance or a platform payment receipt.
Capacity for a customer workflow is determined by the current qualified catalog, runtime availability, account permission, and dispatch checks. Public throughput alone cannot establish that an order can be placed.
Protocol concepts — Read the maintained public protocol explanation.
Source-aware monitoring — Explore observations with their provenance.