Subnet 41: Almanac
Almanac is Bittensor Subnet 41. The Almanac website describes it as a prediction-market terminal that rewards traders for being right early, while the SN41 README source frames the subnet as a sports-prediction competition network connected to trading activity.
What Almanac Provides
The SN41 README describes Sportstensor as a decentralized competition network for sports prediction. It describes Almanac as the front end to Sportstensor: a prediction-market interface that makes submitting predictions through trading more accessible.
At the subnet level, Almanac turns prediction-market activity into a miner-scoring signal. The README describes a scoring mechanism that tracks trading activity over a rolling window, applies eligibility gates, and converts optimized scores into subnet weights for Yuma Consensus.
Miner and Validator Roles
Miners generate information signals by trading through Almanac. The README describes miner scoring as performance-based and model-agnostic, so miners can use manual processes, models, or automated systems as long as their activity can be evaluated by the subnet mechanism.
Validators ingest miner trading history, calculate scores, and set on-chain weights. The repository describes validator work as metadata syncing, data ingestion, scoring, and weight publication.
Market Signal Context
Almanac’s source materials frame miner work as producing information signals through prediction market trading. The website emphasizes early correctness, while the README describes miners as trading through Almanac so that each trade becomes a scored prediction within the incentive mechanism.
That makes the subnet different from a general sports-model leaderboard. A miner can use manual analysis, automated systems, or models, but the subnet evaluates the resulting market activity rather than the model architecture itself. The useful output is a trading signal that can be checked against real-world outcomes.
The README also describes the scoring design as performance-based and model-agnostic. This matters because validator weights are not tied to a required prediction method; they are tied to measured profitability, trading volume, timing, and informational value in the market context.
Scoring Context
The SN41 README describes a two-phase optimization system that rewards historical trading performance among eligible participants. It tracks activity over a rolling window, applies eligibility gates, and converts optimized scores into token weights for Bittensor.
The important distinction is that Almanac rewards signals that remain useful before market outcomes are obvious. The website’s “right early” framing matches the README’s emphasis on trading performance, recent activity, and signal strength rather than late convergence alone.
The README also describes fairness controls such as volume requirements, performance gating, and diversity caps. Those controls make the subnet less like a simple win/loss tally: miner weights reflect a combination of profitability, meaningful participation, and resistance to domination by a single trader or narrow activity pattern.
On-Chain Identity
Live SN41 subnet data is available on TaoStats. The source-backed market-signal and scoring details in this article come from the Almanac website and SN41 README rather than from live identity fields.
Relationship to Yuma Consensus
Subnet 41 uses Yuma Consensus to convert the trading-performance weight vectors that validators submit into the emission shares distributed to miners and validators within the subnet each tempo. The linked documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
In Almanac’s context, validators ingest miner trading history, calculate scores using a two-phase optimization system that tracks rolling-window activity and applies eligibility and diversity gates, and translate those optimized scores into weight vectors for 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 Almanac (SN41), that sequence changes how readers should interpret market prediction signal examples and trading performance scoring outcomes.
In localnet, Almanac-compatible miners and validators can be developed and tested in an isolated environment. Localnet prediction scores and emission outcomes do not represent production subnet performance.
On testnet, Almanac-compatible market signal submissions can be exercised in a shared, non-production network. Testnet evaluations and validator scores are separate from mainnet subnet state.
On mainnet, Almanac (SN41) is the live production subnet where miners submit market intelligence signals and validators score trading performance to determine real Bittensor emissions. The SN41 repository describes the mechanism that applies on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A prediction signal or scoring result from one environment should not be read as representing production subnet performance in another environment.
Reader Boundary
Subnet 41 Almanac should not be read as generic Bittensor subnet documentation, a sports-model leaderboard, or proof that one late consensus call defines rewards. It names one subnet’s prediction-market trading signal competition on netuid 41 (Understanding Subnets, Glossary: Netuid).
Trades Become Scored Predictions
The SN41 README describes miners trading through Almanac so each trade becomes a scored prediction within the incentive mechanism (SN41 repository).
Validator evaluation therefore centers on market activity rather than a required model architecture.
Two-Phase Optimization Applies Eligibility Gates
The README describes a two-phase optimization system with rolling-window activity tracking, eligibility gates, and fairness controls such as volume requirements and diversity caps (SN41 repository).
Those controls are named in the project materials as part of weight conversion.
Validator Weights Still Flow Through Yuma Consensus
Subnet 41 uses Yuma Consensus to convert validator weight submissions into emission shares each tempo (Yuma Consensus, Emission).