Bitcast (SN93)

Bitcast SN93 Turns Creator Attention Into a Bittensor Scoring Market

Bitcast is a Bittensor subnet that evaluates creator content against brand briefs, estimates its value through platform data, and uses validator-set weights to direct emissions. Its design connects YouTube and X activity to an on-chain incentive system, but the model depends heavily on third-party APIs, validator judgments, and the project’s own reporting.

What Bitcast is designed to do

Bitcast describes itself as a decentralized content-marketing protocol on Bittensor. Its stated objective is to reward creators for content that generates measurable brand attention, rather than paying solely for posting or raw audience size. The project currently identifies YouTube and X as its supported platforms, with creators supplying content and validators assessing whether that content satisfies active campaign requirements.

The practical use case is a marketplace for campaign discovery and measurement. Brands or campaign operators provide briefs; creators publish or submit relevant content; and the subnet attempts to convert resulting attention into a dollar-denominated score. This is a project description, not independent proof that the system has achieved commercial scale or that reported campaign values correspond to audited revenue.

How the YouTube mechanism works

The public Bitcast repository describes a miner-validator workflow centered on YouTube. Miners provide OAuth access for channels they operate. Validators retrieve active briefs, query channel and video information through the YouTube Analytics API, assess brief matching with language-model assistance, calculate rewards, and convert those scores into on-chain weights. The repository separates these functions into miner, validator, reward, YouTube, and language-model components.

This architecture makes Bitcast less like a standalone video-hosting network and more like an evaluation layer over existing platforms. Its output depends on access to YouTube data, the quality of campaign briefs, the scoring formulas, and the consistency of validator implementations. The code also indicates that validator scores pass through an exponential moving average and weight-processing steps before submission, so short-term performance does not necessarily translate directly into emissions.

The X mechanism and multi-platform expansion

Bitcast also maintains a separate public repository for an X-based subnet mechanism. The deployment repository describes YouTube and X validators as two Bitcast mechanisms operating under netuid 93, with separate services and configuration. This suggests that SN93 is being used as a broader creator-attention framework rather than only a YouTube scoring system.

The multi-platform design may broaden the addressable creator base, but it adds measurement problems. YouTube and X expose different analytics, audience behaviors, content formats, and rules for identifying engagement. A score that is comparable across platforms requires normalization choices that can materially affect miner rankings and emissions. The public repositories document the operating components, but they do not by themselves establish that cross-platform scores are economically equivalent.

What SN93’s token does

SN93 is a Bittensor subnet rather than a conventional application token issued independently from the network. Bittensor documentation describes subnet alpha assets as part of the network’s emission and staking structure. In Bitcast’s implementation, validators submit weights for miners, and unallocated emission is directed to a burn UID. The token’s direct protocol role is therefore tied to subnet participation, emissions, liquidity, and staking mechanics rather than serving as a payment token inside a conventional centralized advertising platform.

Bitcast’s dashboard presents revenue and buyback figures and describes a portion of revenue as being recycled into SN93. Those figures should be treated as first-party project reporting. The dashboard does not, in the inspected material, provide a complete independently audited accounting trail linking customer payments, operating costs, buybacks, wallet transactions, and token supply changes.

Operators, control, and dependencies

Running Bitcast requires more than holding the subnet asset. The deployment instructions require Bittensor wallet credentials, validator hotkeys, API keys, server resources, and separate services for the YouTube and X mechanisms. The code repository also lists external dependencies including YouTube access, language-model providers, and observability tooling. These requirements create operational barriers for miners and validators and give outside services a meaningful role in the system’s continuity.

The public code is licensed under MIT and includes tests, but the inspected repositories do not constitute a security audit. They also do not fully explain how disputed campaign results are appealed, how malicious engagement is detected across every supported platform, or how protocol changes are approved. At the Bittensor layer, subnet registration, emissions, and validator behavior are governed by network rules and configuration controls; Bitcast’s own repositories remain important practical sources for understanding implementation changes.

What to verify before relying on the system

Bitcast’s model is easy to describe but difficult to validate economically. A high reported audience count does not prove genuine attention, a campaign score does not prove advertiser willingness to pay, and a buyback percentage does not prove that token demand will persist. Users should distinguish dashboard totals from independently verifiable blockchain transactions and confirm the relevant subnet, wallets, APIs, and software versions before operating a node or interpreting reported performance.

Key takeaways

• Bitcast SN93 is a Bittensor subnet for scoring creator content and directing emissions through validator-set weights.
• The YouTube mechanism uses OAuth access, campaign briefs, platform analytics, language-model-assisted matching, reward calculations, and on-chain weight submission.
• An X mechanism is maintained separately, creating a multi-platform design but also introducing comparability and measurement challenges.
• SN93’s token role is tied primarily to Bittensor subnet emissions, staking, liquidity, and network participation.
• Revenue and buyback figures shown by the project are first-party claims and should not be treated as independently audited financial data.
• Operating the system depends on Bittensor infrastructure, platform APIs, external model providers, validator software, and server configuration.

Risks and open questions

• The project’s scoring process depends on third-party platform APIs and data access that may change, be restricted, or provide incomplete signals.
• Validator judgments, language-model outputs, reward formulas, and moving-average processing can affect miner rankings and emissions.
• The inspected sources do not provide a complete independent audit of reported revenue, buybacks, audience figures, or campaign economics.
• Cross-platform comparison between YouTube and X engagement may be difficult because the platforms expose different data and incentives.
• The public repositories do not fully document dispute resolution, malicious-engagement handling, or the process for approving all future protocol changes.
• Token liquidity, emissions, validator concentration, and subnet-level control remain material risks separate from the usefulness of the creator-marketing product.