Subnet 125: 8 Ball
8 Ball is Bittensor Subnet 125. Public project materials describe 8BALL as prediction markets on Bittensor, with a website at 8ball125.com and a miner-support repository at Barbariandev/8Ball_miner.
What 8 Ball Provides
The 8BALL website describes a prediction-market system built around outcome markets, an orderbook, conditional tokens, and a reward engine called Valley. In this model, users trade outcome positions, while market makers post bid and ask liquidity on orderbooks for YES and NO sides of each market.
The public miner repository focuses on how off-chain liquidity-provider wallets are associated with Bittensor identities. It describes Ethereum wallets as the accounts that place orders on the 8BALL orderbook, while the Bittensor hotkey is the identity that receives subnet emissions. That bridge is important because market activity happens through Ethereum wallets, but subnet rewards are assigned to Bittensor participants.
Miner and Validator Roles
Miners participate by providing orderbook liquidity and linking the Ethereum wallet that provides that liquidity to their Bittensor hotkey. The repository describes this as a cryptographic binding: an Ethereum wallet signs a message naming the hotkey, the signed bundle is published at a stable URL, and that URL is committed on chain for validators to read.
Validators score market-maker activity. The repository describes reward scoring over recent orderbook liquidity, with qualifying resting orders evaluated by spread tightness, notional size, and duration. It also states that validators map an Ethereum address back to a Bittensor hotkey through the registered binding before assigning emissions. Those validator scores become the subnet’s input to Yuma Consensus, which converts subnet weights into the incentive split across miners and validators.
The website describes Valley as the longer-term reward engine. Valley frames maker rewards as a convex optimization problem that allocates liquidity across bid and ask price levels subject to budget and spread constraints, then distributes maker rewards according to the useful flow those resting orders support.
Wallet Binding Context
The 8Ball miner README describes the subnet’s identity bridge between Ethereum liquidity wallets and Bittensor hotkeys. The Ethereum wallet is the account that creates limit orders on the prediction-market orderbook, while the Bittensor hotkey is the identity that receives subnet emissions after validator scoring.
The binding process matters because validators need to know which hotkey should receive credit for a wallet’s market-making activity. The README describes an EIP-191 signature bundle: the Ethereum wallet signs a message naming the hotkey, the bundle is published at a stable public URL, and that URL is committed on chain for validators to read. That makes the off-chain market wallet and the Bittensor miner identity auditable without sending Ethereum private keys to validators.
For readers, this explains why 8 Ball is not a normal miner-server task. The miner contribution is resting orderbook liquidity from linked Ethereum wallets, and the subnet-specific validator job is to map that liquidity back to Bittensor identities before weights are assigned.
Reference: 8Ball miner README source
Liquidity Scoring Context
The 8BALL website describes the market system around an orderbook, conditional tokens, and a reward engine. The miner README describes the current liquidity-mining program as scoring recent resting orders by spread tightness, notional size, and duration. Orders nearer to the market midpoint, larger orders, and orders that remain resting longer receive more credit.
That scoring model makes liquidity quality different from simple trading volume. Filled orders stop accumulating duration, and orders outside the qualifying spread range do not receive the same reward treatment. The README also states that all active markets and directions are weighted equally for the launch program, so market makers are rewarded for useful quoted liquidity across YES bids, YES asks, NO bids, and NO asks.
The article’s reward discussion should therefore be read as a market-making incentive loop: Ethereum wallets place and maintain useful orderbook liquidity, validators score that activity over recent windows, and the wallet-to-hotkey binding tells the subnet which Bittensor identity should receive credit.
References: 8BALL website, 8Ball miner README source
On-Chain Identity
Live SN125 data is available on TaoStats. The source-backed prediction-market and liquidity-mining details in this article come from the public 8BALL website and miner repository rather than from live identity fields.
Relationship to Yuma Consensus
Subnet 125 uses Yuma Consensus to convert the liquidity-scoring weight vectors that validators submit into the emission shares distributed to miners and validators within the subnet each tempo. The Yuma Consensus documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
In 8 Ball’s context, validators score recent resting orderbook liquidity, map each linked Ethereum wallet back to a Bittensor hotkey, and submit the resulting weight vectors to the subnet. The Emission documentation describes how those consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For 8 Ball (SN125), that sequence applies to the standard Bittensor lifecycle: localnet for isolated development, testnet for shared non-production testing, and mainnet for live operation with real emissions.
On mainnet, 8 Ball (SN125) is registered as the live production subnet at netuid 125. The Bittensor Networks reference separates mainnet, testnet, and localnet. Participation examples or emission outcomes from one environment should not be read as representing production subnet performance in another environment.
Netuid 125 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 125 is the subnet registered at netuid 125 (Glossary: Netuid). The Understanding Subnets reference explains that each subnet runs its own incentive mechanism while sharing the same underlying Subtensor chain, so the netuid is the stable handle that distinguishes 8 Ball from every other subnet.
For a reader, this means “Subnet 125” and “netuid 125” refer to the same on-chain slot. A claim about 8 Ball should be tied to that netuid rather than to the registered name alone, because the name field can be changed on-chain while the netuid stays fixed.
Reader Boundary
Subnet 125 8 Ball should not be read as generic Bittensor subnet documentation, financial, trading, or investment advice, or a substitute for the subnet’s own primary sources. It names the on-chain subnet registered at netuid 125 under the identity “8 Ball” (Understanding Subnets, Glossary: Netuid).