Loading
Loading
Neuron registration trends
Large-scale AI applications require reliable, low-latency access to multiple language model APIs, but sourcing this centrally is expensive and inflexible. A single operator paying for all API calls directly incurs high fixed costs and creates a single point of failure for credential management.
A decentralized network of contributors can supply that access on-demand, with each contributor earning proportional to the reliability, speed, and output quality they deliver. Contributors are compensated only when their provided credentials successfully serve real traffic, creating an immediate signal for who is reliably available.
MASXAI (Taostatus, Subnet 501 on Bittensor) implements this by asking miners to contribute working LLM API keys for supported models. Miners encrypt keys client-side and submit them to a protocol backend via a validator. The protocol draws on contributed keys operationally and reports usage metrics back to the validator, which scores each miner's efficiency (success rate, latency, output quality, call volume) and submits on-chain weights proportional to confirmed, sustained performance. Hard floors on reliability or quality immediately cut a key's earnings; a key that stops working stops earning the next epoch.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
MASXAI (Taostatus) is a Bittensor subnet that sources real, working LLM API keys from miners and relays them to an external protocol backend (BT Arena) for AI agent pipelines. Miners contribute LLM credentials (5 keys per submission) and are rewarded based on the reliability, latency, output quality, and call volume of their contributed keys as reported by the protocol. The validator acts as the sole bridge between the on-chain incentive mechanism and the protocol, asking miners for keys, relaying encrypted submissions, polling usage reports, and setting weights based on efficiency scores.
Miners configure LLM API keys (5 per submission) and opt in via environment variables. On a fixed interval, the validator queries every eligible miner via LLMKeySynapse, asking for encrypted keys. Miners encrypt keys client-side using NaCl SealedBox for the protocol's published public key and return ciphertexts without ever contacting the protocol directly.
The validator relays accepted submissions to the protocol backend and separately polls it for usage reports. Reports are folded into rolling per-hotkey accumulators; when call-volume floors are crossed or max age is reached, windows are scored and folded into a per-miner exponential moving average (self.scores). Hard floors (high failure rates, low output quality, key marked inactive by protocol) immediately zero a key or hotkey.
Weight is submitted on-chain every eligible epoch: 95% reserved by burn allocation, remaining split proportionally by miner efficiency scores. State is persisted to disk so validator restarts don't lose progress.
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.
The validator polls the protocol backend for usage reports (one row per LLM call) and aggregates them into rolling per-hotkey windows. When a window crosses the call-volume floor or ages out, it is scored via llm_key_efficiency_score(). Reliability is success rate; latency is clamped against a ceiling; volume is capped at target.
Each call is weighted by its provider/model's tier. Per-key hard floors (reliability <50%, quality <floor value) immediately kill that key's contribution; a hotkey's last live key dying hard-zeroes the hotkey. Staleness decay gradually reduces stale scores.
Liveness participation is tracked separately but never blended into on-chain weight—weight comes only from proven, active key usage.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository
Predictive Intelligence Layer for Bittensor
FAQs were auto-generated from the GitHub repository and may not reflect the latest changes.
Holder & total-staked metrics as of 4h ago (hourly snapshot)
I/O-bound workload (HTTP calls and lightweight NaCl/Fernet encryption). No local model inference. Minimum 2.0 GHz CPU, recommended 2.5 GHz. DDR4 RAM. SSD storage with minimum 500 IOPS (recommended 1000 IOPS).
I/O-bound workload. Needs more RAM than miner for state persistence and metagraph caching. Minimum 2.0 GHz CPU, recommended 2.5 GHz. DDR4 RAM. SSD storage with minimum 500 IOPS (recommended 1000 IOPS).
Clone the repository
git clone <repo> && cd taostatus-subnet
Create and activate virtual environment
python -m venv .venv && source .venv/bin/activate
Install dependencies
pip install -r requirements.txt
Copy environment template
cp .env.example .env
Configure LLM API key contribution (set in .env file). Can also use MASXAI_LLM_KEYS_JSON for multi-key setup
export MASXAI_LLM_KEY_CONTRIB_ENABLED=true && export MASXAI_LLM_KEY_CONTRIB_PROVIDER=openai && export MASXAI_LLM_KEY_CONTRIB_MODEL=gpt-4o-mini && export MASXAI_LLM_KEY_CONTRIB_API_KEY=sk-...
Run the miner on testnet
python neurons/miner.py --netuid 501 --subtensor.network test --wallet.name <wallet> --wallet.hotkey <hotkey>
Clone the repository
git clone <repo> && cd taostatus-subnet
Create and activate virtual environment
python -m venv .venv && source .venv/bin/activate
Install dependencies
pip install -r requirements.txt
Copy environment template
cp .env.example .env
Configure protocol backend connection (set in .env file). Leave unset to run validator with pipeline disabled
export MASXAI_LLM_KEY_BASE_URL=<protocol_backend_base_url> && export MASXAI_LLM_KEY_VALIDATOR_TOKEN=<validator_credential>
Run the validator on testnet
python neurons/validator.py --netuid 501 --subtensor.network test --wallet.name <wallet> --wallet.hotkey <hotkey>