How redteamsubnet/redteam works
RedTeam is a Bittensor cybersecurity-challenge subnet: miners submit Docker-based solutions, and validators run challenge-specific evaluation, check originality, maintain scores, and persist validator and submission state. The graph captures the documented submission-to-evaluation-to-incentive workflow and sampled Docker, scoring, and storage responsibilities. Validator lifecycle wiring and some README-described scoring details are not present in the sampled excerpts, so uncertain calls between those components are omitted.
Main entry points: controller.py Challenge controller · miner_manager.py Miner scoring · main.py Runtime configuration · protocol.py Commit protocol
Components 14
Miner Submission
- Commit protocol
src/redteam_core/protocol.py
Challenge Evaluation
- Active challenge config
src/redteam_core/challenge_pool/active_challenges_manager.py - Challenge state
src/redteam_core/validator/challenge_manager.py - Challenge controller
src/redteam_core/challenge_pool/controller.py - Docker runtime
src/redteam_core/challenge_pool/docker_utils.py
Validator Scoring
- Miner scoring
src/redteam_core/validator/miner_manager.py - State and commit storage
src/redteam_core/validator/storage_manager.py - Runtime configuration
src/redteam_core/config/main.py - Remote log forwarding
src/redteam_core/validator/log_handler.py
External Services
- Docker engine
- Internal scoring services
- Storage API
- Bittensor network
Other components
- Miner
Connections 13
- Miner → Commit protocol: submits commits
- Commit protocol → Bittensor network: exchanges synapses
- Active challenge config → Challenge state: resolves manager class
- Challenge controller → Docker runtime: runs containers
- Docker runtime → Docker engine: controls runtime
- Challenge controller → Internal scoring services: checks similarity
- Challenge controller → Internal scoring services: requests scoring
- Miner scoring → Challenge state: aggregates challenge scores
- Miner scoring → Bittensor network: reads metagraph
- State and commit storage → Storage API: fetches and uploads state
- Remote log forwarding → Storage API: uploads logs
- Runtime configuration → State and commit storage: provides API settings
- Runtime configuration → Challenge controller: provides service settings