Loading
Loading
Neuron registration trends
Live speech interpretation requires speed, naturalness, and understanding—not word-for-word accuracy. Traditional machine translation pipelines optimize for literal correctness and often feel too slow or wooden for real-time use. Human interpreters anticipate what is being said, compress rambling phrasing, remove accidental repetition, and deliver meaning in natural spoken language. Conventional benchmarks that measure word-level latency miss what actually matters in live settings.
A decentralized incentive network can reward miners for solving the interpretation problem as humans do: accept source audio, decide when enough meaning is available to respond, generate target-language speech with minimal delay, and preserve intent while sounding natural. Rather than a single best model, the network benefits from diverse architectural experiments—speech-token models, hybrid STT-translate-TTS pipelines, recurrent architectures for causal inference, speculative decoding, and language-model fine-tuning for interpretation-quality output.
Babelbit (Subnet 59) implements this as a two-phase competition. Qualifying miners receive proportional rewards (20% of emissions) based on challenge performance, creating a stable baseline for contributors. Top qualifiers compete in The Arena for the remaining 80%. Validators score miner audio by transcribing it with their own STT model, comparing semantic meaning against reference text using embeddings (not exact matching), checking that speaking rate is plausible, and measuring latency—allowing a small delay based on source utterance length (30% of duration, minimum 2 seconds, maximum 10 seconds). Audio that preserves meaning and speaks naturally is scored on latency alone; audio that fails meaning or rate checks scores zero.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
Babelbit is a Bittensor subnet (SN59) focused on low-latency speech-to-speech translation and interpretation. Rather than optimizing for word-for-word accuracy, it rewards miners for producing natural, spoken-quality target language output with minimal latency, mimicking human interpreter behavior. The subnet runs a two-phase competition: a qualifying round with proportional rewards (20% of emissions), and an arena phase for top performers (80% of emissions).
Validators score miner audio submissions based on semantic meaning preservation, speaking rate plausibility, and latency relative to source utterance duration.
Validator components: (1) Subtensor Gateway – local Bittensor chain query service; (2) Signer – signs requests with validator hotkey; (3) Runner – discovers qualifying miners, generates challenge batches, submits requests, collects responses, orchestrates scoring; (4) Validator – receives runner outputs, calculates weight assignments, submits weights to chain; (5) Scoring Engine – transcribes miner audio (faster-whisper), embeds text for semantic comparison (sentence-transformers), validates speaking rate, computes latency scores. Miners register on netuid 59, publish axon metadata, and accept signed Bittensor requests at a prediction endpoint compatible with current miner contract. Qualifying discovery via axon metadata; managed submission flows (arena) also require Docker image and Hugging Face repository handle.
Challenge status and score artifacts stored in shared local filesystem (BB_CHALLENGE_STATUS_DIR, BB_OUTPUT_SCORES_DIR). Optional Postgres for auxiliary integrations but not core scoring persistence.
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.
Miners submit audio responses to translation challenges. Validator transcribes miner audio with faster-whisper STT, compares transcript meaning to reference via sentence embeddings (all-MiniLM-L6-v2), verifies speaking rate (0.3x–1.3x reference speed), and scores latency. Utterances failing meaning (accuracy <0.65) or rate gates score 0.
Passing utterances score based on latency: full score if finished at/before source end, or within allowed delay window (min 2s, max 10s, default 30% of source duration). Latency score decays smoothly from 1.0 toward 0.0 within window, then 0.0 beyond. Challenge scores average all utterance scores.
Qualifying phase rewards all participants proportionally; arena phase selects best qualifying performers for 80% of remaining emissions.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes.
FAQs were auto-generated from the GitHub repository and may not reflect the latest changes.
Miner hardware requirements not specified in validator documentation. Refer to separate miner repository for miner-specific hardware guidance.
CPU-only validator floor based on benchmarks with faster-whisper-small STT model. 4vCPU/8GB RAM (DigitalOcean Regular Intel) measured too slow for production; 8vCPU/16GB RAM AMD completed 250-miner/60-second workload in ~24 minutes. Storage accounts for OS, Python venv, Docker layers, Hugging Face model cache, logs, and score artifacts. Benchmarked on DigitalOcean Premium AMD (EPYC/Zen 2) vs Regular Intel (Broadwell Xeon). STT transcription is the primary CPU bottleneck.
Miner setup is not documented in this validator repository. Use the dedicated miner repository for miner-specific installation and configuration instructions.
Refer to separate miner repository
Install Bittensor CLI, UV package manager, create and activate virtual environment, and sync project dependencies
pip install bittensor-cli && curl -LsSf https://astral.sh/uv/install.sh | sh && uv venv && source .venv/bin/activate && uv sync
Copy example environment file and configure required variables: BITTENSOR_WALLET_PATH, BITTENSOR_WALLET_COLD, BITTENSOR_WALLET_HOT, BABELBIT_NETUID=59, BITTENSOR_SUBTENSOR_ENDPOINT, SIGNER_URL, SUBTENSOR_GATEWAY_URL, BB_* paths and API endpoints
cp env.example .env && edit .env with your wallet and endpoint settings
Deploy validator stack using Docker Compose (recommended approach). Starts subtensor-gateway, signer, runner, validator, and model-cache services with shared volumes.
docker compose down && docker compose pull && docker compose up --build -d
Monitor validator logs to verify all services are healthy and operational
docker compose logs -f --tail 100
Alternative to Docker: run validator components locally. Start signer, subtensor-gateway, runner, and validate commands in separate terminal sessions for local development/testing.(optional)
bb -vv signer && bb -vv subtensor-gateway && bb -vv runner && bb -vv validate (in separate terminals)