hackquest logo

Bittensor Subnet Hackathon — Round 2 (Testnet)

Welcome to Round 2 of the Bittensor Subnet Ideathon—the Testnet Hackathon!

Register Countdown

Schedule Detail
Bittensor Subnet Hackathon — Round 2 (Testnet)
Registration
19 days left

Host by

Bittensor

Hackathon Mode

ONLINE

Ecosystem

All

Tech Stack

All

Participants

JBH
22+

Community

≈ 23,000 USD

Available in Prizes

Hackathon Winner10,000 USD
Hackathon Runner-UP3,000 USD
Subnet Ideathon Award * 51,000 USD
Discretionary Investment≈ 260,000 USD
Basilica Compute Credit Award≈ 5,000 USD

Description

Watch the introductory video by Jacob Robert Steeves, co-founder of Bittensor, to quickly learn more about Bittensor.

Watch the following video to learn what makes a great subnet.

Round II — Subnet Hackathon(Testnet) (Mar 9,2026 - Mar 30,2026

In Round 1, we saw incredible potential in your subnet designs. Now, it's time to turn those exceptional mechanism designs and incentive logic into reality. The core objective of Round 2 is to validate that your subnet ideas can be successfully deployed and operate meaningfully on the Bittensor testnet.


Who is Eligible?

  • Round 1 Advanced Teams: Only the 7 teams selected from Round 1 are eligible to compete for the Grand Prize ($10,000 Hackathon Winner).

  • Open Participants (Permissionless): All other rewards (Runner-UP, Discretionary Investment, and Compute Credits) are open to everyone. Even if you didn't participate in Round 1, as long as you deploy a functional Subnet or Miner on the Bittensor Testnet, you are welcome to submit and compete!


Execution & Submission Requirements

For Round II, participants are required to submit the following materials:

1. Updated Proposal

Submit an updated proposal reflecting your latest implementation and mechanism design.

2. Demo Video

Submit a demo video showing your subnet or miner running on the Bittensor testnet.

3. Code

Provide a GitHub repository link. The repository must include:

  • Subnet code

  • Miner code

  • Validator code

  • Setup instructions

  • Run instructions

4. Node Setup

Your testnet setup must include:

  • 10 miner hotkeys

  • 3 validator hotkeys

5. Running Evidence

Provide evidence that your system is running properly, including:

  • Miner running logs

  • Validator running logs

  • Query / response logs

  • Weight update evidence, including set_weights or ranking outputs

💡 Tip: Extreme polish is not necessary at this stage, but functional correctness and conceptual integrity are strictly required.


Community Support & Events

To ensure you have the resources and guidance needed during the testnet phase, we have prepared the following support:

  • Weekly Workshops: Throughout Round 2, we will be hosting weekly online workshops. These sessions are designed to provide ongoing technical guidance, answer your questions, and help you navigate the testnet deployment process smoothly. (Specific schedules and meeting links will be shared in our community channels.)


Judging Criteria

In Round 2, judges will evaluate your subnet's testnet performance and mechanism design across the following key dimensions:

  • Functional Implementation: We look for an end-to-end operational subnet on the testnet. This includes successful deployment, functional miner and validator logic, complete flow integrity (from task assignment to reward), and overall network stability.

  • Incentive Mechanism Integrity: The reward logic must behave exactly as designed. High-quality miners should earn more, adversarial or low-quality "spam" behavior must be penalized, and validators must be incentivized for honest evaluation.

  • Proof of Intelligence / Proof of Effort: Your subnet must produce meaningful, non-trivial work. Judges will look for objective evaluation metrics, reproducibility of scoring, and clear signals that the output reflects measurable competence.

  • Validator & Scoring Robustness: A strong evaluation mechanism is crucial. We expect transparent scoring logic, strong resistance to manipulation or collusion, and effective mitigation of systematic bias.

  • Conceptual Integrity & Architecture: Your testnet implementation should align strongly with your approved Round I proposal, featuring a clean structure and a logical, understandable architectural flow.

  • Market & Ecosystem Potential: Beyond the code, your subnet should solve a meaningful real-world problem and clearly add long-term value to the broader Bittensor network.


Timeline

  • Round 2 Hackathon Starts: March9, 2026

  • Submission Ends: March 30, 2026

  • Demo Day (Tentative): March 31, 2026

  • Winner Announcement: April 7, 2026

Good luck building on the testnet! We look forward to seeing you turn your "Proof of Intelligence" into actual, running code.

FAQs

Can teams continue working on their subnet after the ideathon?
Is the ideathon held online or in person?
Can’t find what you’re looking for? Reach out to us!