Skip to content
Javokhir Javokhir
January 19, 2026 ยท 4 min read

Repository split and migration deadline

Announcement Banner

We are separating the monolithic RedTeam repository into four focused projects so updates can ship faster and operators can manage only what they run. The split will be merged on Jan 25, 2026. After the merge, any validator still using the old repository will stop working.

Actions That need to be done

Action Required

For Miners:

  • Read the Miner documentation carefully.
  • Clone the miner repository and follow the installation steps provided in its README.
  • Follow all provided instructions to set up your miner node.
  • Update your environment variables and service definitions to point at the new miner codebase.
  • Restart your miner and confirm it's running properly by monitoring the logs.

For Validators:

  • Read all Validator documentation thoroughly.
  • Stop your existing validator that was built from the monolithic repository.
  • Clone the dedicated validator repository and follow the installation steps provided in its README.
  • Update your environment variables and service definitions to point at the new validator codebase.
  • The new repository includes important stability fixes and improvements.
  • Restart the validator and confirm it by monitoring the logs.

Shared Components

Shared core contains shared services and protocol types. Find the source in the streamlined RedTeam repository, which we're transitioning to redteam_core.

Timeline

  • Now: The migration window is open, and we encourage you to switch immediately.
  • Jan 25, 2026: The new repos become authoritative. Validators still on the old repository will stop and lose rewards until migrated.

Why the change

  • This split enables faster, isolated releases for miners, validators, and the scoring server.
  • It provides tighter blast-radius control and clearer ownership for each role.
  • We keep redteam_core lighter by including only shared components.
  • The result is a simpler security posture where public APIs stay public while validator runtimes and shared core remain compartmentalized.
  • It makes onboarding easier since miners and validators only pull what they need, reducing update friction and dependency drift.

If you hit issues while migrating, open a GitHub issue in the relevant repository or reach out in our public Discord channel on the Bittensor server.