OrmasSN76نOverview

0.003014 τ

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.003014 τ

−0.62%24h−20.67%7d

ن / τ Price

0.003014 τ

−0.62%24h−20.67%7d

Epoch

Epoch315/3609:00

Holders

118

27,651,046,257,987,640,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000.00%

—

7.38%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 −57.36%: protocol buys 0.00%, root sells −64.91%, users net +31.93%, cross-subnet −24.39%, unattributed −0.0002%.

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-05 UTC, as of ≈15:34 UTC (block 9,440,763)

Price, today so far: 0.003014 τ
Volume, today so far: 2.06 τ
Market cap incl. burned, today so far: 935.93 τ
TAO in pool, today so far: 361.16 τ
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

582.0621 τ

FDV

1,297.0866 τ

TVL

722.3217 τ

Lifetime Volume

14.44K τ

Holders

118

Owner Locked

14,255.6374 ن(7.38% of circulating)Perpetual

14d price

Revenue / Recycle

> 1,000×

last day · Net positive

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

≈ 21.7038 τ·21.7038 τ per day

Miners50.62%

3,644.7148 ن ≈ 10.9867 τ/day

Validators31.38%

2,259.3181 ن ≈ 6.8105 τ/day

Owner18.00%

1,295.9670 ن ≈ 3.9066 τ/day

Stake 1,000 τ here

6,255.7114 ن/day≈ 18.8573 τ·18.8573 τ per day

From the validator share, before commission

27,651,046,257,987,640,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000.00%staker APY

· 30d avg 27,651,046,257,987,640,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.003014 τ/ن. Yield varies with stake weight, pool price, and emission rate.

For Miners

50.62% of emission

Slots

256/256Competitive

Burn Cost

0.0005 τ

Est. per Miner

60.7452 ن/epoch≈ 0.1831 τ

Pool / Epoch

182.2357 ن≈ 0.5493 τ

For Validators & Stakers

31.38% of emission

Validator Slots

6/6458 open

Est. per Validator

18.8277 ن/epoch≈ 0.0568 τ

Registration Activity

Neuron registration trends

This Interval

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

Target / Interval

Slots Available

Competitive

256/256

Neurons

256

Development Activity

heroncovelabs/ormas-subnetPython

002 contributors39 commits/30dLast commit 0d ago

MIT

bittensorormassn76subnet

Top Contributors

JakeBruner21

ormas-studio3

Recent Releases

v0.0.314d ago v0.0.315d ago

What Ormas does

Software development teams and platforms need reliable, cost-effective execution of discrete coding tasks — from bug fixes to feature implementation — with independent verification of correctness. Traditional centralized services provide limited transparency into execution costs and verification logic, while ad-hoc outsourcing to individual contractors lacks the scalability and auditability required for production workflows.

A decentralized network of distributed contributors, each with its own execution infrastructure and pricing incentives, can bid competitively on tasks and submit work to independent validators for verification. This structure creates natural cost pressure, transparent pricing discovery, and auditable outcomes without requiring trust in any single operator or vendor.

Ormas implements this pattern on Bittensor: miners clone repositories at a specified commit, solve tasks using their own models and agents, publish result branches, and submit completion evidence. Validators independently re-run acceptance tests in isolated environments, check scope against allowed paths, and post signed decisions.

The gateway collects firm and limit offers in a window, awards based on expected cost and delivery history, and settles payments only after unanimous validator acceptance.

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 coding task outcomes by cloning repositories, solving with their own agents and models, and publishing results. Miners offer firm prices or spend limits for complete tasks and are paid only on accepted delivery after validator verification. The protocol enforces honest reporting through independent validation, real git diffs, actual verification command execution, and settlement only on accepted outcomes—never for tokens, completions, or uptime.

How it works

The Ormas miner skeleton operates as a polling agent: (1) register with the gateway to obtain a stable runner_id and receive authoritative cadence parameters; (2) optionally bind a repository or accept per-job credentials; (3) poll the queue for privacy-safe task envelopes; (4) submit firm or limit offers per job or decline; (5) claim a lease with accepted pricing; (6) clone the base commit, execute the solve function, heartbeat throughout; (7) publish the result branch; (8) run the verify command in a credential-free, isolated environment and compute scope via git diff; (9) post a complete with honest receipt, terminal, and optional settlement price. Validators poll assignments, clone independently using per-job credentials, re-run verification and scope checks, sign decisions, and post acceptance. The gateway collects offers in a window, awards at lowest expected total cost using history and performance, settles accepted deliveries, and computes chain weights from accepted settlement values.

Public-profile jobs use bounded artifacts and OCI image execution; legacy jobs use repository credentials and direct git pushes.

Incentive mechanism

Settlement requires validator acceptance under a frozen policy. Validators re-run the client's verification command in a digest-pinned container, check that changes stay within allowed paths and immutable paths, and sign accept/reject. Same-tenant legacy jobs can settle on the miner's report plus scope and commit checks.

Cross-tenant and public-profile jobs require assigned-validator unanimity. Only accepted outcomes contribute to targets; targets are converted to chain weights at epoch end using live pool prices. Excess emission goes to owner UID; shortfalls carry forward and are settled via 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: 1 month 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-05 04:02 UTC

Changes (10)

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
2026-10-24 04:03 UTCUp200Ormas — A clear path to done. · Bittensor Subnet 76
2026-10-23 04:02 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

Not found in the repository docs.

Validator

OSnonroot Linux/amd64

Not yet verified: GPU, 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 2 Nov 2026

Miner Setup

Install the reference miner package using the recommended installer

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

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 host setup, gateway connectivity, credentials, and registration

ormas-miner doctor

Start the miner loop polling for tasks and claiming work

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

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

Validator Setup

Install the ormas-subnet package and pytest for smoke testing

pip install -e . pytest

Start the reference validator daemon with private bearer token and Ed25519 decision key stored in secure files (mode 0600)

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

Run smoke tests to verify validator setup(optional)

PYTHONDONTWRITEBYTECODE=1 python -m pytest -q -p no:cacheprovider tests

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