Overview
Registration Activity
Neuron registration trends
Neuron registration trends
The alpha price in τ, day by day, and what moved it each way.
Log change over the last 30 days +28.45%: protocol buys +4.76%, root sells −2.43%, users net +25.19%, cross-subnet +0.92%, unattributed −0.0048%.
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.
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).
2026-11-03 UTC, as of ≈20:06 UTC (block 9,427,725)
The day isn’t over yet, so these figures keep changing. They are in no daily total, average or rank.
Traders face fragmented liquidity across DEXes and chains, forcing manual routing decisions and suboptimal pricing. Protocols attempting centralized MEV protection become single points of failure. Minotaur (Subnet 112) solves this through a decentralized network where miners compete to write optimal solvers — software that generates the best execution plans for any order. Validators simulate each plan on Anvil forks, apply dual scoring (a JavaScript module for outcome verification and an on-chain Solidity gate for invariant enforcement), and reach consensus via EIP-712 signatures before a singleton relayer executes on-chain. This shifts the trust burden from a central operator to distributed consensus and cryptographic accountability.
Miners earn by improving solver quality measured on breadth — more successful order delivery across the set compared to the current champion — within bounded regression (no order cut beyond 1%). The champion solver, hot-swapped into the validator network, runs against all live orders.
A new challenger is adopted if it delivers strictly more output across the order set or ties perfectly and wins on gas efficiency, code factorization, or reduced dead code. The solver interface is minimal and chain-agnostic: miners declare execution plans as ordered interactions (swaps, bridges, approvals) targeting any chain, and the platform's compiler injects bridge interactions and escrow coordination.
Auto-generated from the GitHub repository and may not reflect the latest changes.
Minotaur (Subnet 112) is a distributed agentic intent execution platform on Bittensor where miners compete by writing optimal solvers, validators simulate and score execution plans via dual-layer JavaScript and on-chain validation, and a relayer submits approved transactions. The platform enables developers to define App Intents (Solidity contracts + JS scoring) and users to submit signed orders to a universal Intent OrderBook for automated execution across chains.
Miners write a Solving Engine (IntentSolver subclass) that generates execution plans for user orders. Validators run the engine in sandboxed Docker containers, simulate plans on Anvil forks, and apply dual scoring (JavaScript module + on-chain scoreIntent). Both scores must exceed threshold.
The leader validator broadcasts proposals to followers; followers independently re-simulate and re-score, then sign EIP-712 approvals. The leader collects N-of-M quorum signatures and the Relayer submits the co-signed transaction on-chain. App Intents (Solidity + JS scoring) are defined by developers and deployed permissionlessly; users submit signed orders to the universal Intent OrderBook.
Champions are chosen by relative, per-order scoring resolved via a fixed ladder: output (net better on breadth, regressions bounded), then gas/factorization/deadwood tie-breaks on fully-matched ties. The active champion's submitter receives 20% of miner emissions via tempo-aligned weight commits.
Scoring is deterministic and relative: every submission is compared to the current champion per order at the same fork pin. The adoption ladder (highest priority first): (1) Output — challenger wins if (wins + blind_spot_covers) − regressions ≥ 1, with regressions tolerated only within a 1% hard floor (no order cut by >1%, no dropped orders). (2) On a fully-matched tie (every order matched, zero regressions), resolve via: gas (≥200 bps cheaper total metered gas), then factorization (max_region_nodes smaller by ≥100), then deadwood (unproductive_nodes smaller by ≥2000). Scoring is raw delivered output only — quote quality no longer affects adoption.
Once adopted, the solver hot-swaps into block loop execution. Weight emission is tempo-aligned: commits fire in a short window before each epoch step, and the chain keeps only one pending commit per validator per tempo epoch.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes.
Home of Open Source Robotics.
Reputation is what other people know about you. Honor is what you know about yourself.
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 for the latest instructions.
Not found in the repository docs.
Not yet verified: GPU, RAM, Recommended RAM, Storage, CPU cores, 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. · Extracted 28 Sep 2026
Clone the canonical repository
git clone https://github.com/subnet112/minotaur_subnet.git && cd minotaur_subnet
Create and activate a Python 3.12+ virtual environment
python3 -m venv .venv && source .venv/bin/activate
Install Python dependencies
pip install -r requirements.txt
Register your hotkey on subnet 112 (mainnet only; local testnet auto-registers)(optional)
btcli subnet register --netuid 112 --subtensor.network finney --wallet.name my-miner --wallet.hotkey my-miner-hotkey
Run the LLM-driven agent loop to generate and submit solver strategies(optional)
python -m minotaur_subnet.miner.main agent --validator-url http://localhost:8080 --strategy-dir ./strategies --miner-id my-miner-001
Submit a git-based solver via a PR against subnet112/minotaur-solver
python -m minotaur_subnet.miner.main submit --pr-number <n> --head-sha <40-char-sha> --hotkey my-miner-hotkey --validator-url http://localhost:8080 --poll
Create a Bittensor wallet and hotkey
pip install bittensor-cli && btcli wallet new --wallet-name <your_wallet> --hotkey <your_hotkey>
Register your hotkey on subnet 112
btcli subnet register --netuid 112 --wallet-name <your_wallet> --hotkey <your_hotkey> --subtensor.network finney
Install Foundry and generate an EVM consensus key (holds no funds, signing only)
curl -L https://foundry.paradigm.xyz | bash && foundryup && cast wallet new
Request onboarding to the on-chain ValidatorRegistry on Base (8453) and BT EVM (964)
Open an issue at https://github.com/subnet112/minotaur_subnet/issues/new?template=onboard-validator.yml with your EVM address
Open TCP ports 9100 and 8080 inbound on your firewall
sudo ufw allow 9100/tcp && sudo ufw allow 8080/tcp
Clone the canonical Docker Compose stack
mkdir -p ~/minotaur && cd ~/minotaur && curl -fsSL https://raw.githubusercontent.com/subnet112/minotaur_subnet/main/platform/validator/docker-compose.yml -o docker-compose.yml && curl -fsSL https://raw.githubusercontent.com/subnet112/minotaur_subnet/main/platform/validator/.env.example -o .env
Configure environment variables with wallet credentials, axon URL, signing key, and upstream RPC endpoints
Edit .env and fill in WALLET_NAME, HOTKEY_NAME, VALIDATOR_AXON_URL, VALIDATOR_PRIVATE_KEY, ETH_UPSTREAM_RPC_URL, BASE_UPSTREAM_RPC_URL
Start the validator stack with auto-update (Watchtower) enabled
docker compose --profile autoupdate up -d
Verify the validator daemon is healthy and properly configured
curl http://localhost:9100/health && curl http://localhost:9100/identity && bash scripts/check_validator.sh
Install a cron job to recycle Anvil forks every 6 hours (prevents disk bloat)
0 */6 * * * root docker compose -f /home/<user>/minotaur/docker-compose.yml rm -fsv anvil-eth anvil-base anvil-btevm && docker compose -f /home/<user>/minotaur/docker-compose.yml up -d anvil-eth anvil-base anvil-btevm
| Day (UTC) | Share |
|---|---|
| 2026-11-02 | 0.55% |
| 2026-11-01 | 0.60% |
| 2026-10-31 | 0.61% |
| 2026-10-30 | 0.61% |
| 2026-10-29 | 0.69% |
| 2026-10-28 | 0.74% |
| 2026-10-27 | 0.71% |
| 2026-10-26 | 0.33% |
| 2026-10-25 | 0.32% |
| 2026-10-24 | 0.56% |
| 2026-10-23 | 0.71% |
| 2026-10-22 | 0.63% |
| 2026-10-21 | 0.52% |
| 2026-10-20 | 0.51% |
| 2026-10-19 | 0.48% |
| 2026-10-18 | 0.39% |
| 2026-10-17 | 0.27% |
| 2026-10-16 | 0.13% |
| 2026-10-15 | 0.0002% |
| 2026-10-14 | 0.0002% |
| 2026-10-13 | 0.0002% |
| 2026-10-12 | 0.0002% |
| 2026-10-11 | 0.0002% |
| 2026-10-10 | 0.0002% |
| 2026-10-09 | 0.0002% |
| 2026-10-08 | 0.0002% |
| 2026-10-07 | 0.0002% |
| 2026-10-06 | 0.0002% |
| 2026-10-05 | 0.0002% |
| 2026-10-04 | 0.0002% |
| 2026-10-03 | 0.0002% |
| 2026-10-02 | 0.0002% |
| 2026-10-01 | 0.0001% |
| 2026-09-30 | 0.0002% |
| 2026-09-29 | 0.0002% |
| 2026-09-28 | 0.0002% |
| 2026-09-27 | 0.0002% |
| 2026-09-26 | 0.0002% |
| 2026-09-25 | 0.0002% |
| 2026-09-24 | 0.0002% |
| 2026-09-23 | 0.0002% |
| 2026-09-22 | 0.0001% |
| 2026-09-21 | 0.00% |
| 2026-09-20 | 0.00% |
| 2026-09-19 | 0.00% |
| 2026-09-18 | 0.00% |
| 2026-09-17 | 0.00% |
| 2026-09-16 | 0.00% |
| 2026-09-15 | 0.00% |
| 2026-09-14 | 0.00% |
| 2026-09-13 | 0.00% |
| 2026-09-12 | 0.00% |
| 2026-09-11 | 0.00% |
| 2026-09-10 | 0.00% |
| 2026-09-09 | 0.00% |
| 2026-09-08 | 0.00% |
| 2026-09-07 | 0.00% |
| 2026-09-06 | 0.00% |
| 2026-09-05 | 0.00% |
| 2026-09-04 | 0.00% |
| 2026-09-03 | 0.00% |
| 2026-09-02 | 0.00% |
| 2026-09-01 | 0.00% |
| 2026-08-31 | 0.00% |
| 2026-08-30 | 0.00% |
| 2026-08-29 | 0.0016% |
| 2026-08-28 | 0.0001% |
| 2026-08-27 | 0.0001% |
| 2026-08-26 | 0.0001% |
| 2026-08-25 | 0.0001% |
| 2026-08-24 | 0.00% |
| 2026-08-23 | 0.00% |
| 2026-08-22 | 0.00% |
| 2026-08-21 | 0.00% |
| 2026-08-20 | 0.00% |
| 2026-08-19 | 0.00% |
| 2026-08-18 | 0.00% |
| 2026-08-17 | 0.00% |
| 2026-08-16 | 0.00% |
| 2026-08-15 | 0.00% |
| 2026-08-14 | 0.00% |
| 2026-08-13 | 0.00% |
| 2026-08-12 | 0.00% |
| 2026-08-11 | 0.00% |
| 2026-08-10 | 0.00% |
| 2026-08-09 | 0.00% |
| 2026-08-08 | 0.00% |
| 2026-08-07 | 0.00% |
| 2026-08-06 | 0.00% |
| 2026-08-05 | 0.0001% |