Three views of one network#
The network explorer separates chain registration, delivery history, and your own work. They answer different questions; a registration is not a promise that a worker is available.
- The metagraph shows finalized Finney subnet 76 state. Select a node, search by UID, hotkey or identity, or use the table. Arrow keys move between matching nodes on the map.
- Provider delivery shows the Ormas gateway's public, anonymized delivery statistics. These labels do not have a published mapping to chain hotkeys.
- Your tasks and terms appears in the signed-in workspace when Outcomes is available to your account. It reads your existing projects and job handles. Nothing on this page submits weights, claims tasks, chooses an offer, or spends funds.
Reading the metagraph#
| Field | Meaning |
|---|---|
| UID and hotkey | A registration at the displayed finalized block. A UID can later belong to a different hotkey. |
| Miner registration | A registration without a validator permit, excluding the subnet owner. This does not verify gateway admission or availability. |
| Validator permit | Permission to participate in chain weight-setting. It does not establish assignment as an Ormas task checker. |
| Chain active | The runtime's activity flag, governed by the subnet activity cutoff. It is not a heartbeat or an “online now” status. |
| Subnet stake / root stake | Reported alpha and TAO stake respectively, converted from their smallest units. These are stake figures, not available wallet balances. |
| Incentive / dividends / consensus | The runtime's normalized epoch scores. They are not customer acceptance rates. |
| Epoch emission | The chain-reported alpha emission value, not a customer payment receipt or an earnings forecast. |
| Revealed weights | Directed, nonzero stored weights. The percentage is each weight's share of its sending row. Unrevealed commitments are not guessed. |
| Owner burn destination | When the runtime reports burn mode, weights directed to the owner are labeled accordingly. Do not interpret them as delivered work. |
Node placement is a reading aid: validator permits sit inside the ring of other registrations, with the owner at the center. Distance, size and position are not rankings. Connections represent weights, not live task transfers. The overview draws at most 512 connections; selecting a node isolates its relationships and the inspector lists its complete row.
The finalized block hash, timestamp, actual epoch index and last epoch block travel with the snapshot. Epoch boundaries are read from chain state rather than predicted from a block-number formula.
Provider delivery statistics#
The gateway publishes pseudonymous provider IDs and distinguishes operator-run from independent providers. Task sizes come from reported delivery history, not a capacity guarantee.
Acceptance is the paid share of reported settled history. Activity covers deliveries in the last seven days: quiet is fewer than six, steady is six through 23, and busy is 24 or more. Growth compares this period with the preceding seven days, using a minimum denominator of one. Median quote and quote-to-branch time describe the last seven days.
The gateway's own basis statement appears below the cards. These figures are not a live provider ranking. An empty report does not prove that no workers are available.
Tasks and offers in your workspace#
Choose one of your projects to read its tasks, acceptance state, accepted firm or limit terms, and reported charge. Open a task to inspect its customer-visible offer book when the gateway provides one.
An offer book may contain provider labels, affiliation, firm price or estimate and hard limit, predicted charge, additional exposure, delivery estimates, evidence bands, recommendation and selection. Predictions are not bills or guarantees. The website reports the gateway's recommendation; it does not compute its own ranking or award an offer.
Private Standard jobs currently go directly to one provider without a competitive offer book. Older jobs and other jobs outside an offer window can also omit the book. The page preserves any accepted terms and describes the missing book neutrally; absent data alone does not identify a job’s claim method. Missing charges remain unknown rather than becoming zero. Model identities, private costs, reserves, runner credentials and checker assignments stay private.
Freshness and limits#
The public chain and delivery sources refresh every two minutes while the page is visible. Each source has its own status: a gateway outage does not invalidate a healthy chain snapshot. Failed reads retry every 30 seconds, with a short upstream cooldown to avoid repeated requests during an outage. The private task view refreshes every 30 seconds. These are periodically refreshed snapshots, not a streaming feed.
If a public source fails, the last successful result can remain for up to 15 minutes, explicitly marked stale. With no usable result, the page shows an unavailable state instead of example data. No historical trend is inferred from a single snapshot.
Offline browsers pause updates and resume on reconnect. A stalled public read leaves the loading state within 25 seconds. Private task data is hidden after a failed refresh or loss of connectivity; it is not shown as current pricing. If account access cannot be confirmed, private rows and project names are hidden and automatic retries stop. Sign in again or check your access, then retry. A new server instance may have no previous public snapshot to retain.
There is currently no public join between gateway provider IDs and chain hotkeys, no public full worker registry, and no public network-wide task or bid feed. The explorer keeps those boundaries visible.
For the underlying chain concepts, see the Bittensor metagraph guide. Ormas-specific fields follow the existing gateway responses.