Registration Guide

Registration & Issue Submission

Link your GitHub account to your Bittensor hotkey and learn how to submit valid issues to earn rewards.

Prerequisites

Before you begin, make sure you have:

Bittensor Wallet

A Bittensor wallet with a miner hotkey registered on Subnet 100. You'll need the secret key (64-character hex or mnemonic phrase).

GitHub Account

An active GitHub account that will be linked to your hotkey for issue submissions and reward tracking.

Installation

Clone the repository and build the CLI tools:

1234

git clone https://github.com/PlatformNetwork/bounty-challenge.git
cd bounty-challenge
cargo build --release
export PATH="$PWD/target/release:$PATH"

Registration Process

Use the interactive wizard to register your GitHub account:

bounty wizard

The wizard will guide you through the following steps:

Enter Secret Key

Provide your hotkey's secret key (64-character hex string or 12/24 word mnemonic phrase).

Derive Hotkey

The CLI derives your hotkey address in SS58 format from the secret key for verification.

GitHub Username

Enter your GitHub username (case-insensitive, will be lowercased for signing).

Sign Registration

The CLI signs a registration message with sr25519 using your hotkey.

Submit to Platform

The signed registration is submitted to the Platform Network for verification and storage.

Message Format

The registration message follows this exact format:

register_github:{github_username_lowercase}:{unix_timestamp}

Example

For username alice at timestamp 1704067200:

register_github:alice:1704067200

Creating Valid Issues

For an issue to be considered valid and earn rewards, it must meet these requirements:

Repository: Must be in PlatformNetwork/bounty-challenge

Title Format: Must include version: [TYPE] [vX.X.X] Description

Valid Types: BUG, FEATURE, PERF, DOCS

Closure: Issue must be closed by a maintainer with the valid label

Title Examples

Valid[BUG] [v0.2.1] CLI crashes when hotkey file is missing

Valid[FEATURE] [v0.3.0] Add support for ed25519 signatures

Valid[PERF] [v0.2.0] Registration takes 10+ seconds on slow networks

Valid[DOCS] [v0.2.1] Missing installation instructions for Windows

InvalidBug report: something is broken

Invalid[BUG] Missing version number in title

Issue Template

Use this template to structure your issue reports:

12345678910111213141516

## Description
[Clear description of the bug/feature]

## Steps to Reproduce
1. Step one
2. Step two

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Environment
- OS: [e.g., Ubuntu 22.04]
- Version: [e.g., 0.1.0]

Clear, well-structured issues are more likely to be validated. Include all relevant information to help maintainers understand and verify your report.