OrmasSN76نOverview

0.003336 τ

Ormas

ن (Noon)SN76

Ormas is an Outcomes API for coding work on Bittensor subnet 76, in development. Clients post a change and the test that proves it; miners quote a firm price for the passing result and deliver a branch. Miners will be paid only when independent validators accept the delivery, and clients will be charged the accepted quote and nothing on a miss. Protocol, thin client, reference miner and reference validator: MIT.

5CLWm…DCAo

ن / τ

0.003336 τ

+0.86%24h+3.15%7d

ن / τ Price

0.003336 τ

+0.86%24h+3.15%7d

Epoch

Epoch342/3603:36

Holders

120−0.83%7d

29,281,878,581,091,595,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000.00%

96.20%

9.31%perpetual

Pool depth & trades

What moved the price

The alpha price in τ, day by day, and what moved it each way.

Log change over the last 30 days −43.65%: protocol buys 0.00%, root sells −69.01%, users net +56.61%, cross-subnet −31.25%, unattributed −0.0004%.

Protocol buy
User buy (staking)
Cross-subnet
Root sell (dividend claims)
User sell (unstaking)
Residual
Price path
Market candle

About this chart

The chart follows the alpha price in τ. Each period starts at its opening price and steps through the mechanisms below, in a fixed order, to its closing price: a step that rises pushed the price up, one that falls pushed it down, and its height is how far it moved the price. A thin line carries each close into the next period’s open; it is dashed where the two differ. The faint candle behind each period is the market’s own open, high, low and close, for context.

With many periods on screen (90 days, or hours), the steps would be too thin to read, so the chart draws the price as a line instead and colours each period by the mechanism that moved it most. Hover a period for the full step-by-step breakdown.

Protocol buy: The chain spending excess emission TAO to buy alpha from the pool. A permanent protocol buyback; it pushes the price up.
Root sell: Root-dividend claims sold into the pool; they push the price down.
User buy / sell: Staking into and unstaking from this subnet.
Cross-subnet: Swaps from other subnets routed through this pool.
Residual: What the decomposition cannot attribute to a mechanism. It is always shown, never folded into another part.

Not here, because they do not move the spot price: the per-block TAO injection into the pool, and burns.

All figures are log changes, not simple percentage changes, so the parts add up exactly to the total; on big moves the two differ (a 10% log fall is a 9.5% price fall).

Today so far

2026-11-10 UTC, as of ≈13:16 UTC (block 9,476,070)

Price, today so far: 0.003336 τ
Volume, today so far: 25.81 τ
Market cap incl. burned, today so far: 1.17K τ
TAO in pool, today so far: 379.95 τ
Emission share, today so far: —not available yet

The day isn’t over yet, so these figures keep changing. They are in no daily total, average or rank.

Subnet Configuration

Pool & Mechanism

AMM Pool

Balancer

Mechanism

dTAO

Access

Registration

Open

Neurons

256/256Competitive

Validators

6/6458 open

Economics

Owner Cut

18.00%

Weights

Commit-Reveal

Enabled (v3, 1 epochs)

Liquid Alpha

Disabled

Weights Version

Weights Range

1–65535

Timing

Tempo

360~1.2h

Immunity Period

5,000~16.7h

Activity Cutoff

5,000~16.7h

Market & Economics

Market

Market Cap

738.3254 τ

FDV

1,553.3453 τ

TVL

759.8990 τ

Lifetime Volume

18.98K τ

Holders

120−0.83% 7d·+22.45% 30d

Circulating alpha

221,306.1808 ن

Owner Locked

20,605.8759 ن(9.31% of circulating)Perpetual

14d price

Holder & circulating-alpha metrics as of 2026-11-10 00:00 UTC (daily close)

Revenue / Recycle

No recycle

last day

Emissions

0.00%of network emissions

Emission history is being recalculated from on-chain allocation.

TAO emitted to this subnet

Sent into its pool each day: its share of network emissions

0.0000 τ/day

0 τ per day

Daily distribution

Alpha paid out each day, valued at the pool price

7,200.0000 ن/day

≈ 24.0208 τ·24.0208 τ per day

Miners49.99%

3,599.0934 ن ≈ 12.0074 τ/day

Validators32.01%

2,304.9396 ن ≈ 7.6898 τ/day

Owner18.00%

1,295.9670 ن ≈ 4.3236 τ/day

Stake 1,000 τ here

6,066.4364 ن/day≈ 20.2389 τ·20.2389 τ per day

From the validator share, before commission

29,281,878,581,091,595,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000.00%staker APY

· 30d avg 29,281,878,581,091,595,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000.00% · Moderate

90d

Pool emits 1.0000 ن/block at 0.003336 τ/ن. Yield varies with stake weight, pool price, and emission rate.

For Miners

49.99% of emission

Slots

256/256Competitive

Burn Cost

0.0005 τ

Est. per Miner

89.9773 ن/epoch≈ 0.3002 τ

Pool / Epoch

179.9547 ن≈ 0.6004 τ

For Validators & Stakers

32.01% of emission

Validator Slots

6/6458 open

Est. per Validator

19.2078 ن/epoch≈ 0.0641 τ

Registration Activity

Neuron registration trends

This Interval

24h: 0 registrations (0 burn · 0 PoW)

Target / Interval

Slots Available

Competitive

256/256

Neurons

256

Development Activity

heroncovelabs/ormas-subnetPython

002 contributors29 commits/30dLast commit 4d ago

MIT

bittensorormassn76subnet

Top Contributors

JakeBruner21

ormas-studio3

Recent Releases

v0.0.318d ago v0.0.320d ago

What Ormas does

Software companies and development teams need to verify that code changes work correctly and meet requirements. Traditional approaches rely on centralized CI/CD pipelines, in-house testing infrastructure, or outsourced contractors. These solutions either require significant upfront capital, lack transparency in how work is validated, or create single points of failure. A distributed network of independent validators and solvers, with payment tied directly to accepted outcomes rather than effort expended, can reduce infrastructure cost while ensuring verification comes from multiple parties with aligned incentives.

Ormas Subnet 76 implements this as a marketplace where clients describe required changes and write acceptance tests. Miners solve tasks using their own models and tooling, publish results to a repository branch, and receive payment only when independent validators verify the work meets requirements. The network maintains a frozen acceptance policy for each task, ensures validators are distinct from miners, and settles payment deterministically on validator quorum.

This structure separates the incentives: miners compete on price and quality; validators earn only for honest verification; clients pay exactly what verified work costs.

The protocol defines how miners register capacity, poll task queues, submit firm or limit offers, claim work, clone repositories at specified base commits, verify their own results, publish to result branches, and report usage. Validators independently reproduce base failures, run verification commands in isolated execution environments, check that changes stay within allowed file paths, and sign their decisions. Settlement uses the frozen policy; cross-tenant work requires unanimous validator acceptance, while same-tenant work can settle on miner report plus scope and commit validation.

Auto-generated from the GitHub repository and may not reflect the latest changes.

About

active

Ormas subnet 76 is a Bittensor subnet where miners deliver whole task outcomes (code changes, bug fixes) for acceptance-based payment. Miners clone client repositories, solve tasks using their own models and tooling, verify their work, and publish results; they are paid only when validators accept the delivery. The protocol supports both legacy credential-based jobs and modern public-profile jobs with frozen acceptance policies, offering mechanics for firm prices or limit-based settlement.

How it works

Ormas SN76 operates a task marketplace where clients describe required changes and acceptance tests. The gateway manages registration, job queuing, offer collection, lease management, publication, validator assignment and settlement. Miners register capacity and task cells, poll a privacy-safe queue envelope, submit firm or limit offers, claim awarded tasks, clone the repository at base commit, solve using internal models and tooling, verify the result, publish to a result branch, and complete with usage and evidence.

Validators independently clone, verify, check scope via git diff, and sign decisions under a frozen policy. Settlement follows validator quorum on the acceptance path (public-profile jobs, cross-tenant legacy jobs) or miner report plus scope/commit checks (same-tenant legacy jobs). The reference skeleton in this package implements the miner and validator protocol operations; miners inject their own solve logic.

Incentive mechanism

The miner posts a firm or limit offer before claiming. On verified in-scope delivery, firm is paid immediately at its fixed price; limit is paid at the miner's reported settled_price_usd, capped at the accepted limit_usd. Rejected or out-of-scope deliveries earn nothing.

Validators assign and execute independently, freezing acceptance policy and decision key at claim. A miner with no verified hotkey mapping earns no chain weight. Each accepted outcome freezes an emission target of settled USD × 2 (rate version earned-bid-2x-v1, live since 2026-10-05T15:00Z).

Validators convert per-miner accepted USD each epoch to weights linear in value, pro-rated against the fixed alpha emission, with carry-forward of shortfalls and planned treasury top-ups.

The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository (github.com, opens in a new tab, external site)

On-Chain Identitysigned on-chain by subnet owner

Ormas

Noon · Arabic letter · pronounced “noon”

Owner: 5CLWm…DCAo
Hotkey: 5CqaQ…cCWK
Owner Cut: 18.00%
Contact: [email protected]

Registered: 2 months ago(Sep 5, 2026)
Block: 9,003,844
Slot history: Every subnet in SN76
Neurons: 256/256
Tempo: 360 blocks

Ormas is operated by Heron Cove LLC, which issues invoices and commercial documentation for the service. Registered September 5, 2026; not a continuation of the former subnet 76. Commercial payments and subnet emissions are separate.

Website

URL: https://ormas.ai/ (ormas.ai, opens in a new tab, external site)
Status: Up200
TLS: Valid
Title: Ormas — A clear path to done. · Bittensor Subnet 76
Checked: 2026-11-10 04:02 UTC

Changes (10)

2026-11-09 04:02 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-11-07 04:02 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-11-05 04:02 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-11-03 04:03 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-11-01 04:02 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-10-30 04:02 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-10-29 04:02 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-10-28 04:02 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-10-27 04:03 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-10-26 04:03 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76

Subnet History

Emissions started 2026-09-19 19:04 UTC

Block 9,103,613Extrinsic

SubnetIdentitySet 2026-09-13 16:00 UTC

Block 9,059,741Extrinsic

Subnet registered 2026-09-05 21:19 UTC

Block 9,003,844

SubnetOwnerHotkeySet 2026-09-05 21:19 UTC

Block 9,003,844

Recent Activity

FirstEmissionBlockNumberSet Block 9,103,613 Extrinsic2026-09-19 19:04 UTC
SubnetIdentitySet Block 9,059,741 Extrinsic2026-09-13 16:00 UTC
NetworkAdded Block 9,003,8442026-09-05 21:19 UTC
SubnetOwnerHotkeySet Block 9,003,8442026-09-05 21:19 UTC

This information was auto-extracted from the GitHub repository and may be incomplete or out of date. Always refer to the subnet's GitHub repository (github.com, opens in a new tab, external site) for the latest instructions.

Hardware Requirements

Miner

GPU—

Not yet verified: OS, Network, Notes

Validator

GPU—

OSNonroot Linux/amd64 with Docker CLI

Not yet verified: Network, Notes

Machine-extracted from the subnet's repository docs; may be wrong or out of date. Check the repository before buying or renting hardware. Open the repository (github.com, opens in a new tab, external site) · Extracted 9 Nov 2026

Miner Setup

Install the ormas-miner package into ~/.ormas-miner/venv and link it into ~/.local/bin

curl -fsSL https://ormas.ai/install.sh | bash

Save your miner runner key (ormr_...) locally in ~/.ormas-miner/credentials.json with mode 0600

ormas-miner login --gateway https://api.ormas.ai

ormas-miner register --miner-id your-miner-name --cell task:code --cell task:code/small --cell task:lang/python --cell task:publication/github-artifact-v1 --cell task:acceptance/operator-run-v3 --cell task:preflight/deferred-v1

Verify Python, Git, gateway health, credentials, key acceptance and active registration

ormas-miner doctor

Run the polling loop with your solve command, re-registering on each start with the same miner-id and cells

ormas-miner run --runner-id <assigned-id> --miner-id your-miner-name --repo-id <id> --repo-url <url> --solve-command '<cmd>' --cell task:code --cell task:code/small --cell task:lang/python --cell task:publication/github-artifact-v1 --cell task:acceptance/operator-run-v3 --cell task:preflight/deferred-v1

Register your chain hotkey mapping for SN76 weight allocation; sign-command reads challenge bytes and prints sr25519 signature(optional)

ormas-miner register-hotkey --runner-id <assigned-id> --hotkey-ss58 <your-ss58> --sign-command '<signer>'

Validator Setup

Install the ormas-subnet package from source with dependencies httpx and cryptography

pip install -e .

Run the reference validator daemon; both token and Ed25519 key files must be mode 0600 and private to the service account

ormas-validator --gateway https://api.ormas.ai --token-file /private/path/validator-token --private-key-file /private/path/validator-ed25519-key --workdir-root /private/path/validator-work

Review at most one assignment and exit with status 3 when idle; use --slots 1 for single-process operation(optional)

ormas-validator --gateway https://api.ormas.ai --token-file /private/path/validator-token --private-key-file /private/path/validator-ed25519-key --workdir-root /private/path/validator-work --once

No hardware? Back this subnet by staking instead New to mining? Start with the setup guide Validator setup guide

What moved the price

Overview

Today so far

Subnet Configuration

Market & Economics

For Miners

For Validators & Stakers

Registration Activity

Development Activity

What Ormas does

About

Website

Subnet History

Recent Activity

Participate

Hardware Requirements

Miner Setup

Validator Setup

What moved the price

Today so far

Subnet Configuration

Market & Economics

For Miners

For Validators & Stakers

What Ormas does

About

Website

Subnet History

Hardware Requirements

Miner Setup

Validator Setup