Back

Blog details

Watch-to-Earn (W2E) on AIOZ Stream: What's Documented

AIOZ Network
7 min readAugust 28, 2026
aioz-streamguide

"Watch-to-Earn" is a real, named feature on AIOZ Stream, confirmed in both the product's own docs and its original launch announcement. What isn't confirmed anywhere is the part most people actually want to know: how much a viewer earns, what triggers a payout, or where the tokens come from. This is what's actually published, what isn't, and what a reasonable person can infer from AIOZ's broader DePIN design in the meantime.

TL;DR:

  • Watch-to-Earn (W2E) is real and confirmed for AIOZ Stream's V1 release, alongside SVOD, TVOD, Tips, and AVOD, described in AIOZ's own launch materials as "optional."
  • No AIOZ source, docs or announcement, publishes a payout formula, a per-minute rate, a funding source, or an eligibility trigger for W2E specifically.
  • The term "on-chain royalties" doesn't appear anywhere in AIOZ Stream's own materials. Treat it as a general industry concept, not an AIOZ-specific mechanism, until AIOZ documents one.
  • Theta Network's TFUEL model, the closest well-documented industry comparison, pays viewers for relaying bandwidth to other viewers, not simply for watch time, which is a useful frame for what W2E might resemble structurally.
  • AIOZ Stream's DePIN nodes already get paid for storage and delivery work under a confirmed incentive model, so a bandwidth-relay-style viewer reward would be structurally consistent with how the rest of the network already pays participants, though this is a reasoned inference, not a documented fact.

What AIOZ actually confirms

Two AIOZ sources mention Watch-to-Earn directly. AIOZ Stream's own concepts documentation lists it as one of five monetization and reward mechanisms, alongside SVOD, TVOD, AVOD, and Tips, describing them collectively as "available without compromising mainstream usability." Separately, AIOZ's original AIOZ Stream launch announcement specifies that monetization, including "AIOZ-denominated AVOD with optional Watch-to-Earn," shipped as part of the V1 release rather than being held back for a future version. Put together, that's a confirmed, real, currently available feature, not a roadmap promise. What both sources have in common is that neither goes further than naming it. There's no accompanying explanation of how a viewer actually accrues tokens.

Person watching a video stream on a laptop, representing a viewer earning rewards

What isn't documented

Four specific things aren't published anywhere in AIOZ's docs, API reference, or public announcements: the payout rate (tokens per minute watched, or any other unit), the funding source (whether rewards come from a fixed pool, from ad revenue, from network inflation, or from the content owner's own budget), the eligibility trigger (does a live stream count differently than VOD, is there a minimum watch duration, does it require a connected wallet), and whether a creator receives any cut of a viewer's W2E reward or whether it's a viewer-only incentive that doesn't touch the creator's side at all. None of AIOZ Stream's payment documentation, which does cover wallet deposits and service billing in real detail, extends to this. That's worth being direct about rather than filling the gap with a plausible-sounding guess: if you're evaluating AIOZ Stream specifically for its W2E mechanic, the honest answer today is that the feature exists and the mechanics aren't public yet.

The practical stakes of each gap are different, and worth separating rather than lumping into one vague "we don't know enough" note. Not knowing the payout rate means a viewer-facing product can't tell a user what to expect before they watch, the same problem an ad network would have with no fill rate. Not knowing the funding source matters more for a platform operator than a viewer: if rewards draw from network inflation, they cost the operator nothing directly; if they draw from the content owner's own budget, W2E becomes a real line item to plan for, not a free feature to flip on. Not knowing the eligibility trigger blocks the most basic integration question, whether a product's own analytics need to report W2E-relevant watch events at all, or whether AIOZ tracks that independently on its own infrastructure without any input from the app built on top of it.

How the industry actually does this

The term "watch-to-earn" covers more than one real mechanism, and the difference matters. Theta Network's TFUEL, the most established comparison in this space, is reported to reward viewers primarily for relaying video to other nearby viewers over a peer-to-peer connection, sharing upload bandwidth rather than simply being rewarded for the act of watching. That's structurally a network-contribution reward wearing a "watch to earn" label, closer to what a DePIN storage or delivery node earns for doing work than to an attention-based ad-revenue share. Other platforms in the same category run closer to a pure engagement model, paying based on watch time or interaction frequency, more like a loyalty-points system denominated in a token instead of cash. Both are legitimately called "watch-to-earn" in marketing copy, and they pay out on completely different logic. A third pattern, reported around Audius's $AUDIO token in the audio-streaming space, is different again: rewards there are described as tied to specific challenges and periodic trending rankings, inviting a friend, hitting a listening streak, landing a track in the week's top five, rather than a continuous per-minute accrual for either listening or relaying. That's closer to a gamified loyalty program than either a bandwidth reward or a pure attention meter. Three real platforms, three different reward logics, all fairly called "earn tokens by consuming media." Without AIOZ publishing which model it follows, or some fourth mechanism entirely, it isn't possible to say which of these W2E on AIOZ Stream actually resembles.

Why the DePIN structure is a reasonable clue

Here's an educated guess, clearly labeled as one rather than presented as fact: AIOZ's own DePIN network already has a confirmed, documented incentive structure where node operators earn AIOZ tokens for contributing storage and delivery capacity, the same mechanism this series has covered in the AIOZ DePIN article. A viewer's device, while watching a P2P-delivered stream, is participating in that same delivery mesh, relaying segments to other nearby viewers exactly the way a dedicated node does, just at a smaller scale and without opting in as an operator. If W2E pays viewers for that relay contribution rather than for the act of watching itself, it would be a natural, minimal extension of an incentive model AIOZ has already built and verified elsewhere in its stack, closer to Theta's model than to a pure attention-reward scheme. That's a coherent guess based on how the rest of AIOZ's architecture is actually documented to work, not a claim about what AIOZ has said. Someone deciding whether to build around this feature should verify it directly rather than take the inference as settled.

The mechanical reason this inference holds together is worth spelling out. In a P2P delivery model, a viewer's player doesn't just pull a stream from a central server, it can also serve already-buffered segments to other nearby viewers requesting the same content, the same peer-assisted delivery mechanic that lets AIOZ's DePIN network offload bandwidth away from centralized origin servers in the first place. A node operator gets paid for exactly that kind of contribution today, measured and settled on-chain per AIOZ's documented payment model. A viewer's browser or app doing the same relay work, even briefly and at a smaller scale, is performing the identical function a paid node performs, just without an operator account attached to it. Extending payment to that already-happening contribution, rather than inventing a reward for the separate, harder-to-verify act of a person's eyes being on a screen, would be the more straightforward engineering path, and it's the one that requires the least new infrastructure on top of what AIOZ has already built and shipped.

What to verify before building on this

If W2E matters to an actual product decision, check three things directly against AIOZ Stream's live dashboard and API rather than any article, this one included: whether a W2E toggle or setting currently exists in the dashboard for a real account, whether the API exposes any reward or earnings endpoint tied to it, and whether AIOZ's support channels or developer community have published anything more specific than the docs since this was written. Documentation gaps close over time, and a feature that's undocumented today may have a published rate by the time anyone reading this actually goes looking.

Frequently Asked Questions

Is Watch-to-Earn (W2E) a real, currently available AIOZ Stream feature?
Yes. It's confirmed in AIOZ Stream's own concepts documentation and in AIOZ's original launch announcement as part of the V1 monetization suite, described as optional.

Does AIOZ publish a W2E payout rate or formula?
No. Neither AIOZ Stream's technical docs nor its payment documentation specifies a rate, funding source, or eligibility trigger for W2E specifically.

Does "on-chain royalties" mean something specific on AIOZ Stream?
Not in AIOZ's own materials, the phrase doesn't appear there. It's a general Web3 creator-economy term, not a documented AIOZ Stream mechanism.

Does a creator get a cut of a viewer's W2E reward?
This isn't specified anywhere in AIOZ's public documentation. Don't assume either answer without verifying directly against a real account.

Is AIOZ Stream's W2E the same mechanism as Theta Network's TFUEL rewards?
Not confirmed either way. Theta's model is reported to reward bandwidth relaying specifically; AIOZ hasn't published which mechanism its own W2E follows, so any resemblance is an informed guess, not a documented fact.

Where should I check for updated details before integrating W2E?
AIOZ Stream's live dashboard and API reference directly, since documentation gaps like this one can close without a corresponding update to third-party articles.

References

We only send updates when meaningful changes ship, and you can unsubscribe anytime

Related Content

blog thumbnail

WebRTC Mesh vs SFU vs MCU: How P2P Video Topologies Actually Differ

Mesh, SFU, and MCU solve the same problem, getting N people in a call to see each other, in three very differently priced ways. The math behind why mesh breaks past 4 people, and why every major platform runs SFU instead of MCU.

aioz-streamguide
7 min readSeptember 20, 2026
blog thumbnail

What Is a CDN Edge Node and How Content Caching Actually Works

A traditional CDN edge is a company-owned data center, one of a few hundred. AIOZ's edge is a community-operated node, one of 328,094. Here's what that structural difference actually means for caching, coverage, and guarantees.

aioz-streamguide
6 min readSeptember 19, 2026
blog thumbnail

Video Container Formats Explained: MP4 vs MOV vs WebM vs MKV

MP4 and WebM aren't independent formats, they're restricted, standardized descendants of MOV and MKV. The real lineage explains the trade-offs better than a feature table, and none of the four is actually what a streaming platform delivers.

aioz-streamguide
7 min readSeptember 18, 2026
blog thumbnail

What Is AV1 and Should You Use It for Video Streaming

AV1 shares VP9's royalty-free pitch, but hardware decode is moving fast and Netflix's own numbers are strong. Here's what actually changed, and whether AIOZ Stream supports it today.

aioz-streamguide
6 min readSeptember 17, 2026
blog thumbnail

Widevine vs FairPlay vs PlayReady: DRM Explained

Most DRM comparisons stop at platform lists. The two things that actually matter: security tiers gate resolution, and a historical encryption mismatch used to break Apple playback silently, until the industry converged on one fix.

aioz-streamguide
6 min readSeptember 16, 2026
blog thumbnail

What Is DRM and Do You Need It for Video Streaming

AIOZ Stream's own docs don't mention DRM anywhere. Here's what DRM actually protects, who really needs it, and what AIOZ Stream offers instead, an access-control model closer to Cloudflare Stream than to Mux's full multi-DRM support.

aioz-streamguide
6 min readSeptember 15, 2026