Subnet 80: DogeLayer
DogeLayer is Bittensor Subnet 80, a subnet for Scrypt proof-of-work mining. It connects Bittensor participation with LTC/DOGE mining by asking miners to contribute Scrypt hashrate and asking validators to measure the value of that contributed work.
The project website is dogelayer.ai. The codebase named by the subnet’s on-chain identity is dogelayer-ai/dogelayer, whose README describes DogeLayer as a Bittensor subnet built around production of Scrypt mining hashrate.
What DogeLayer Provides
DogeLayer turns mining hashrate into the service being evaluated on the subnet. Miners point Scrypt mining hardware or remote hashrate at the DogeLayer pool, and their work is tracked as shares. The subnet then uses Bittensor incentives to reward miners whose hashrate contributes more value to the pool.
This places DogeLayer in the physical-compute side of the subnet ecosystem. Instead of rewarding text answers, model outputs, or data retrieval, it rewards externally measurable proof-of-work mining contribution.
Hashrate Reward Context
The DogeLayer README source describes the subnet as being designed around production of proof-of-work mining hashrate for the Scrypt algorithm used by LTC/DOGE mining. It separates miner rewards into direct mining rewards from actual mining and subnet alpha incentives for Bittensor-registered miners.
The public DogeLayer website uses the same broad framing: it describes a mining pool that enables Scrypt miners to join a Bittensor subnet. Read with the README, that makes Subnet 80 a bridge between an external proof-of-work mining market and Bittensor’s validator-weight system.
This is why DogeLayer is different from a pure compute benchmark. The measured contribution is not whether a miner can run a model; it is whether the miner contributes Scrypt hashrate whose value can be tracked over a period of time. The README says validators rank miners by the share value they produce during each period.
Measurement Context
The README’s architecture section describes a flow from miners submitting work and metrics to validators calculating weights and the Bittensor chain receiving those weights. That flow gives the subnet a concrete measurement boundary: miners contribute mining work, validators evaluate the reported contribution, and the resulting weights determine how Bittensor-side rewards are allocated.
For readers comparing DogeLayer with other subnets, the important distinction is that DogeLayer uses an externally measurable mining substrate. It still depends on validators and Yuma Consensus, but the underlying work is Scrypt hashrate rather than generated text, retrieved data, or model-training improvement.
References: DogeLayer README source, DogeLayer website
Miner and Validator Roles
Miners supply Scrypt hashrate associated with a Bittensor hotkey. The DogeLayer documentation describes miner rewards as coming from two paths: mining rewards handled through the DogeLayer platform and subnet alpha incentives for registered Bittensor participants.
Validators evaluate miner contributions by comparing the share value produced over a period of time. At a high level, miners that provide more valuable shares receive stronger validator weighting, and those weights are processed through Yuma Consensus.
On-Chain Identity
Live SN80 subnet data is available on TaoStats, which identifies the subnet as dogelayer. The live Finney identity for netuid 80 registers the subnet name as dogelayer, with the description “Dogelayer is the world’s first mining pool enabling Scrypt miners to join Bittensor subnet.” The GitHub repository is dogelayer-ai/dogelayer.
Relationship to Yuma Consensus
Subnet 80 uses Yuma Consensus to convert the hashrate-contribution 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 DogeLayer’s context, validators evaluate miner contributions by comparing the share value each miner produces over a measurement period, ranking miners that provide more valuable Scrypt hashrate higher in the weight distribution. Unlike subnets that evaluate model outputs or generated content, DogeLayer’s weight signal comes from externally measurable proof-of-work contribution. 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 Subnet 80, 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, Subnet 80 is registered as the live production subnet at netuid 80. 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.
Reader Boundary
Subnet 80 DogeLayer rewards Scrypt mining hashrate rather than model outputs or retrieved data. The DogeLayer README describes miners earning through separate LTC/DOGE mining rewards and Bittensor alpha-token incentives for participants registered on netuid 80.
Two Reward Paths, One Hashrate Contribution
The same README separates direct cryptocurrency mining earnings, collected and redistributed through the DogeLayer platform, from alpha-token rewards tied to hashpower value for registered subnet miners. Pointing hardware at the pool alone does not describe both paths; registration on subnet 80 is what connects hashrate work to the alpha incentive track.
Validator Weights Follow Measured Share Value
Validators rank miners by the share value produced over each measurement period rather than by self-reported hashrate claims. That keeps subnet weights anchored to tracked mining contribution before Yuma Consensus turns validator agreement into emissions.
Validator weights still flow through Yuma Consensus to determine emissions each tempo (Yuma Consensus, Emission).