Loading
Loading

Neuron registration trends
Organizations developing voice AI models face a fragmented evaluation landscape. Training teams lack standardized benchmarks for measuring whether generated speech matches requested voice characteristics—gender, tone, emotion, pitch, and accent. Quality assessment remains subjective, reliant on in-house panels, and difficult to compare across competing model architectures. Deploying and evaluating models at scale requires infrastructure investment that smaller research teams cannot justify. The status quo creates inefficiency: good models go unrecognized because evaluation is localized and non-comparable.
A distributed evaluation network solves this by creating open, measurable standards. Instead of isolated evaluations, multiple independent assessors run identical quality checks on all submitted models. Each evaluator scores models on content accuracy, audio quality, and adherence to voice trait specifications. Results are aggregated across evaluators to identify which models perform best, creating a transparent, reproducible leaderboard. This approach removes central gatekeeping and surfaces genuine improvements in model performance.
Vocence implements this as a decentralized subnet where miners deploy voice models (starting with prompt-based text-to-speech) and validators execute a shared evaluation pipeline. The Bittensor network coordinates registration and distributes rewards to both high-performing miners and validators who run honest evaluations. All models, evaluation code, and results remain open and auditable.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
Vocence is a Bittensor subnet for decentralized voice intelligence development, currently focused on Prompt-based Text-to-Speech (PromptTTS). Miners train and deploy voice models that generate speech matching natural-language prompts describing content and voice traits (gender, tone, emotion, pitch, etc.), while validators evaluate model quality across content correctness, audio quality, and prompt adherence using a standardized evaluation pipeline and stake-weighted global consensus scoring.
Vocence operates as a decentralized evaluation network: Miners train PromptTTS models (Q1 focus) and deploy them via the Chutes platform as containerized /speak endpoints, exposing a canonical interface (text + instruction → WAV). Each miner publishes a Hugging Face repository with model artifacts and configuration (miner.py, chute_config.yml, vocence_config.yaml) and commits metadata on the Bittensor chain. Validators run continuously (Docker or CLI), maintaining a local SQLite registry of valid miners (chain-sourced, validated against HF and Chutes), determining the active validator set locally from metagraph + fresh sample buckets, and executing two parallel workflows: (1) Sample Generation—download source audio from local corpus, call each miner's Chutes endpoint with evaluation prompts, run AudioJudge evaluation, upload results to own Hippius bucket; (2) Weight Setting—read evaluation windows from all readable active-validator buckets, aggregate miner scores using fourth-root stake weighting, apply consensus and threshold rules, set weights on-chain via Bittensor.
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 Bittensor chain handles registration, metagraph state, and weight assignments; no single validator's scores determine rewards. All model artifacts and evaluation data remain open; Chutes and Hippius provide model serving and sample storage respectively.
Each validator independently downloads source audio, queries miners via their Chutes /speak API, evaluates results using AudioJudge and the standardized pipeline, and uploads samples to its own Hippius bucket. Weight setting uses global consensus: validators read evaluation windows from all active validators in their VALIDATOR_BUCKETS_JSON, aggregate miner win rates using stake-weighted scoring (weight exponent = 0.25 on stake), require at least 40 evaluations across 3+ active validator buckets for eligibility, enforce a configurable threshold margin (THRESHOLD_MARGIN) for new leaders, and apply winner-take-all distribution with burn (weight 1.0 on UID 0) if consensus rules fail. Active validators are determined locally: peers with fresh evaluations (default 24-hour window) and metagraph stake.
The miner registry is computed locally from chain commitments with HuggingFace/Chutes validation and duplicate detection.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository
Universal motion to meaning
FAQs were auto-generated from the GitHub repository and may not reflect the latest changes.
Holder & total-staked metrics as of 1h ago (hourly snapshot)
Miners deploy models on Chutes platform using canonical Vocence wrapper; specific hardware depends on the PromptTTS model implementation chosen
Runs as containerized service (Docker + Watchtower for auto-updates); local SQLite database for miner registry; corpus downloaded to local storage
Clone the Vocence repository
git clone https://github.com/Vocence-bt/vocence && cd vocence
Install UV package manager and sync dependencies
pip install uv && uv sync
Set up Chutes configuration from template
cd miner_sample && cp chute_template/chute_config.yml.example chute_config.yml
Configure Hugging Face repository with canonical Vocence wrapper (miner.py, chute_config.yml, vocence_config.yaml)
# Render chute_template with: VOCENCE_REPO, VOCENCE_REVISION, VOCENCE_CHUTES_USER, VOCENCE_CHUTE_ID
Build and deploy your model chute (chute name must contain 'vocence')
chutes build && chutes deploy
Push model to Chutes (or use CLI alternative to manual deploy)(optional)
uv run vocence miner push --model-name <name> --model-revision <revision>
Commit model and Chute ID to Bittensor chain (requires Bittensor wallet registration)
uv run vocence miner commit --chute-id <chute-id> --wallet-name <wallet> --hotkey-name <hotkey>
Clone the Vocence repository
git clone https://github.com/Vocence-bt/vocence && cd vocence
Copy environment template
cp env.example .env
Configure environment variables (must contact Vocence team for Chutes permission, API URL, and Hippius bucket keys)
# Edit .env: NETWORK, NETUID (78), WALLET_NAME, HOTKEY_NAME, CHUTES_API_KEY, API_URL, Hippius credentials, VALIDATOR_NAME
Configure validator bucket credentials for consensus scoring
# Edit VALIDATOR_BUCKETS_JSON with readonly access keys for active validator sample buckets
Start validator with Docker Compose (includes Watchtower for auto-updates)
docker-compose up -d
Alternative: run from source without Docker (requires Python 3.12+, FFmpeg, build tools)(optional)
pip install uv && uv sync && uv run vocence serve