Subnet 16: BitAds
BitAds is Bittensor Subnet 16 (SN16), operated by FirstTensorLabs. The subnet runs a decentralized proof-of-sale marketing network: campaign owners stake or rent SN16 alpha tokens to secure miner capacity for their campaigns, miners earn emissions by driving verified sales, and validators confirm that real purchases occurred before crediting any miner. Rewards are tied directly to commerce outcomes rather than to impressions, clicks, or other vanity metrics.
How the Mechanism Works
According to the BitAds repository, BitAds verifies commerce through a proof-of-sale model. When a customer completes a purchase through a miner’s campaign link, the transaction is confirmed via a cryptographically-verified webhook from the merchant platform. Only webhook-confirmed sales count toward a miner’s score — promotional activity that generates clicks but no purchases earns nothing.
Validators collect 30-day rolling performance data for each miner and compute scores using a dual-weighted formula: sales volume contributes 15% of the score and total USD revenue contributes 85%. Both metrics are normalized to prevent a small number of high-volume miners from dominating the weight distribution. Refund rates apply a multiplicative penalty — a 10% refund rate reduces a miner’s score by 10% — aligning incentives with genuine customer satisfaction.
The subnet also includes an emission-burn mechanism: if total alpha emissions exceed the dollar value of sales generated, validators burn the excess to maintain a sustainable ratio between emissions and actual commerce value. This prevents the network from over-rewarding miners relative to the value they produce.
Weight vectors from validator scoring feed into Yuma Consensus, distributing emissions via Dynamic TAO.
Participating as a Miner
Miners on BitAds are affiliate marketers. The BitAds repository describes their economic role as driving real purchases for active campaigns by promoting them across any channel — social media, content, email, or paid advertising. Each miner receives a unique trackable link for each campaign they promote; sales through that link are attributed to their hotkey via webhook confirmation.
Miners earn emissions proportional to the verified revenue and order volume they generate. Competitive miners focus on high-commission campaigns that match their audience, maintain low refund rates, and consistently convert traffic into completed purchases. A miner who generates significant revenue without refunds earns top-decile emissions.
Participating as a Validator
Validators on BitAds collect sales data for every active miner over a rolling 30-day window. The BitAds repository describes validators receiving webhook confirmations for completed purchases, tracking refunds, computing per-miner scores, normalizing results to prevent concentration, and submitting weight vectors to Yuma Consensus. Validators also run the emission-burn logic, comparing total alpha emissions against aggregate sales value each epoch.
Merchandisers
Campaign owners — called merchandisers — stake or rent SN16 alpha tokens to reserve miner bandwidth for their campaigns. The BitAds repository describes staking as long-term capacity and renting as flexible short-term access without token lockup. The staking requirement scales with desired campaign reach: larger alpha positions secure more miner attention. Miners choose which campaigns to promote based on commission structures, audience fit, and expected conversion rates.
On-Chain Identity
BitAds is registered at netuid 16 on Bittensor with 256 neurons, verifiable via
taostats.io/subnets/16. The subnet owner coldkey is
5CqRkhQUEgkQ4nBB4SCKnc9AzKPs9VLYv28erjeXPqQYVt9V. The codebase is at
FirstTensorLabs/BitAds and the project site is
bitads.ai.
Relationship to Multiple Mechanisms
BitAds has validators confirm verified sales before crediting miner rewards. The Glossary and Multiple Incentive Mechanisms docs note that validators must evaluate miners separately for each mechanism.
For readers, this article documents one subnet market. If that netuid runs more than one incentive mechanism, validator scores and weights should be read per mechanism rather than as one combined path.
Relationship to Yuma Consensus
Subnet 16 uses Yuma Consensus to convert the 30-day rolling performance 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 BitAds’s context, validators independently collect webhook-confirmed sales data, compute per-miner scores using the dual-weighted revenue and volume formula, apply refund-rate penalties, normalize scores before submitting weights, and also run the emission-burn comparison. Yuma Consensus aggregates those weight submissions across the validator set into a single consensus ranking. 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 BitAds (SN16), that sequence changes how readers should interpret proof-of-sale marketing examples and verified-sale scoring outcomes.
In localnet, BitAds-compatible miners and validators can be developed and tested in an isolated environment. Localnet verified-sale results and emission outcomes do not represent production subnet performance.
On testnet, BitAds-compatible campaign and sale-verification workflows can be exercised in a shared, non-production network. Testnet verification results and validator weights are separate from mainnet subnet state.
On mainnet, BitAds (SN16) is the live production subnet where miners drive verified sales for campaigns and validators confirm purchase outcomes to determine real Bittensor emissions. The BitAds repository is the registered project repository for SN16 on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A verified-sale result or emission outcome from one environment should not be read as representing production subnet performance in another environment.
Miner and Validator Roles
Subnet 16 operates under the standard Bittensor two-role structure. Miners supply the subnet’s capability and validators evaluate those contributions and set weights. Reward distribution follows Yuma Consensus.
Reader Boundary
Subnet 16 BitAds should not be read as generic Bittensor subnet documentation, a pay-per-click ad network, or proof that promotional traffic alone earns emissions. It names one subnet’s proof-of-sale marketing competition on netuid 16 (Understanding Subnets, Glossary: Netuid).
Webhook Confirmation Counts Verified Sales
The BitAds repository credits miners only when merchant webhooks confirm completed purchases rather than clicks or impressions alone (BitAds repository).
Unconverted campaign traffic therefore does not advance a miner’s verified-sales score.
Emission Burn Aligns Rewards With Commerce Value
When alpha emissions exceed the dollar value of verified sales, validators burn the excess to keep rewards proportional to commerce outcomes (BitAds repository).
That mechanism ties subnet emissions to measured sales rather than unconstrained token issuance.
Validator Weights Still Flow Through Yuma Consensus
Subnet 16 uses Yuma Consensus to convert validator weight submissions into emission shares each tempo (Yuma Consensus, Emission).