Loading
Loading
"The RedTeam subnet by Innerworks is a decentralized platform designed to drive innovation in cybersecurity through competitive programming challenges. The subnet incentivizes miners to develop and submit code solutions to various technical challenges, with a focus on enhancing security. These solutions can be integrated into real-world products to improve their security features."
Neuron registration trends
Security teams struggle to stay ahead of evolving automation frameworks, anti-detect browsers, and bot traffic. Traditional centralized approaches create bottlenecks where solutions are developed in isolation and lag behind new evasion techniques. A decentralized network of independent security researchers can rapidly develop and test novel detection methods, sharing insights through competitive benchmarking.
RedTeam Subnet addresses this through a performance-based incentive model where miners submit detection and classification solutions to real-world security challenges. Each submission is validated for code quality, compared against prior work to enforce originality, and scored based on accuracy. Validators evaluate solutions in isolated environments, ensuring reproducibility and preventing unfair advantages. Yuma Consensus aggregates validator assessments to allocate TAO emissions proportional to solution quality, creating a self-reinforcing cycle where better security innovations receive proportional rewards.
The subnet currently hosts six active challenge categories: AB Sniffer (automation framework detection), ADA Detection (anti-detect browser identification), Humanize Behaviour (human-mimicking bot scripts), FlowRadar (VPN traffic detection), Bot Virus (bot completion under detection constraints), and Device Fingerprinter (device identification across browsers). Miners package solutions as Docker images, submit through a 24-hour commit cooldown to prevent gaming, and earn rewards based on validator consensus until submission decay.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
RedTeam Subnet is a decentralized cybersecurity platform on Bittensor that incentivizes miners to develop and submit code solutions to security challenges. Miners earn TAO rewards based on solution quality and originality, with submissions evaluated through validation, plagiarism detection via similarity checking, and performance scoring. The subnet emphasizes continuous improvement through decay mechanisms and fairness through strict anti-plagiarism policies.
RedTeam Subnet operates on Bittensor with a validator-miner architecture. Miners develop solutions to challenges (AB Sniffer, ADA Detection, Humanize Behaviour, FlowRadar, Bot Virus, Device Fingerprinter), package them as Docker images, and submit via the miner node (which handles commit cooldown ~24 hours, encryption, and timing). Submissions flow through validators which run the code in isolated containers, evaluate quality, and assign scores/weights.
A centralized evaluation system performs validation (code quality checks), comparison (similarity detection via code analysis), and scoring (challenge-specific metrics). Yuma Consensus aggregates validator weights to determine final TAO emission distribution. The dashboard provides real-time monitoring of submission status (Received → Validated → Accepted/Rejected/Invalid → Decaying → Decayed) and detailed payload inspection (validation output, comparison logs, scoring results).
Private Docker Hub repositories and Personal Access Tokens (PATs) secure solution confidentiality during transmission and evaluation.
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 solutions to challenges and receive scores based on quality and originality. Each submission undergoes validation (code quality/structure checks), comparison (plagiarism detection via similarity scoring against accepted submissions and same-day submissions), and scoring (challenge-specific evaluation). Accepted submissions earn rewards for ~10-15 days before score decay reduces earnings.
The system uses similarity thresholds: same-miner submissions must differ substantially (reject if ≥0.9 similarity), different-miner submissions must be sufficiently unique (reject if ≥0.7 similarity). Validators assign weights based on submission quality, and Yuma Consensus determines final emission allocation. New submissions immediately override previous ones, stopping prior earnings.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository
"The RedTeam subnet by Innerworks is a decentralized platform designed to drive innovation in cybersecurity through competitive programming challenges. The subnet incentivizes miners to develop and submit code solutions to various technical challenges, with a focus on enhancing security. These solutions can be integrated into real-world products to improve their security features."
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)
System requirements are for running miner node. Actual development requirements depend on challenge type (JavaScript/Python/Python ML).
Bare metal server recommended for production. Must stake sufficient TOA tokens on the subnet.
Set up development environment and tools
Install prerequisites: git, Python (>= v3.10), pip (>= 23), Miniconda (recommended), Docker, and docker compose
Create, fund, and register wallet on RedTeam Subnet 61
Setup Bittensor wallet following https://docs.theredteam.io/manuals/bittensor/wallet/
Create dedicated workspace for RedTeam projects
mkdir -pv ~/workspaces/projects/redteam61 && cd ~/workspaces/projects/redteam61
Clone miner node repository
git clone https://github.com/RedTeamSubnet/miner.git && cd miner
Configure environment variables (wallet directory, wallet name, hotkey name)
cp -v ./.env.example ./.env && nano ./.env
Configure Docker Hub Personal Access Token (PAT) for private image authentication
cp -v ./templates/configs/personal_access_token.txt ./volumes/configs/agent-miner/personal_access_token.txt && nano ./volumes/configs/agent-miner/personal_access_token.txt
Configure active_commit.yaml with Docker image SHA256 digests in format: <CHALLENGE_NAME>---<USERNAME>/<REPO_NAME>@sha256:<DIGEST>
cp -v ./templates/configs/active_commit.yaml ./volumes/configs/agent-miner/active_commit.yaml && nano ./volumes/configs/agent-miner/active_commit.yaml
Validate docker compose configuration
./compose.sh validate
Start miner node (keep running continuously to submit solutions and earn rewards)
./compose.sh start -l
Set up development environment and tools
Install prerequisites: git, Python (>= v3.10), pip (>= 23), Miniconda (recommended), Docker, and docker compose
Create, fund, register wallet, and stake sufficient TOA tokens for validator node
Setup Bittensor wallet following https://docs.theredteam.io/manuals/bittensor/wallet/ and register on RedTeam Subnet 61
Create dedicated workspace for RedTeam projects
mkdir -pv ~/workspaces/projects/redteam61 && cd ~/workspaces/projects/redteam61
Clone official validator repository (mandatory as of Jan 25, 2026)
git clone https://github.com/RedTeamSubnet/validator.git && cd validator
Configure environment variables (wallet directory, wallet name, hotkey name)
cp -v ./.env.example ./.env && nano ./.env
Validate docker compose configuration
./compose.sh validate
Start validator node using Docker Compose (recommended for production)
./compose.sh start -l
Monitor validator logs and performance(optional)
./compose.sh logs agent-validator