← All Subnet News

October 16, 2026 · Published daily

Subnet News — October 16, 2026

Null Consensus opens an optional larger competition format, while SN25 UR announces mainnet and a Network Capacity Reserve. SN95 Actual publishes DGX Station inference measurements, SN4 Targon highlights its revenue dashboard, and SN91 Cascade reports a paper-trading result. Also: SN86 re-registration, SN102 ConnitoAI’s finalized coldkey swap, miner rule changes, unresolved incidents and the latest public Shizzy video.

Coverage window
Oct 15, 2026, 10:31 AM – Oct 16, 2026, 9:00 AM ET
Subnets in coverage roster
128
Subnets with updates
35
01

Biggest stories first

Today's ranked news

★★★★★ marks the day's most consequential news. Scores weigh the size of the announcement, evidence quality, ecosystem reach and relevant market reaction.

#01 · Ecosystemverified
★★★★★

Null Consensus offers larger competitions—with a single weight-setting validator

Openτensor’s October 15 release announcement and primary documentation describe an owner-selected alternative to Yuma. Null permits capacity up to floor(2,500/mechanism count), versus floor(256/mechanism count) under Yuma; switching does not automatically expand a subnet. The highest unrounded-stake registered UID becomes the sole validator permitted to submit weights, and consensus/bond calculations are skipped. That creates room for bigger competitions and precise integer reward ratios, while concentrating weight-setting authority. Yuma remains the default and root cannot select Null. Optional proof-of-work registration is independently available for Null or Yuma: a direct zero-tip submission needs no registration burn, initial collateral purchase or transaction fee, but still requires computational work and obeys admission rules. Const’s October 15 quote welcomes the added scale and freedom; that is commentary, not evidence every subnet has switched. Direct finalized storage at block 9,296,035 confirms SN120 Affine already using Null with capacity 1,000 and PoW enabled; SN25 UR and SN128 byteleap.ai remain Yuma with capacity 256. The release index separately labels a 16,000-capacity Null version upcoming, conflicting with the guide/post’s 2,500 description. We do not assume that larger version is active; exact per-subnet configuration takes precedence.

Why 5 stars: A primary protocol release materially changes competition capacity, admission options and trust assumptions across Bittensor.

#02 · SN4 · Targondeveloping
★★★★★

SN4 Targon highlights revenue visibility and enterprise booking

Openτensor’s October 16 Novelty Search announcement describes SN4 Targon’s new GPU capacity being booked within a day, often on year-long enterprise contracts, and points to its public revenue dashboard. The dashboard labels its measure combined platform revenue over the last 30 days. This makes customer activity more visible, but the numeric chart did not render in our public page extraction, so the roughly $583,000 circulated by commentators is not presented as an independently verified current total. Bookings and revenue are attributed claims, not net profit or a completed token buyback. The discussion also separates available cloud products from roadmap services.

Why 4 stars: A public commercial reporting surface and concrete enterprise-demand claims matter, with chart and financial verification limits explicit.

#03 · SN25 · URverified
★★★★★

SN25 UR announces mainnet and a Network Capacity Reserve

SN25 UR’s October 16 announcement says its validator is active, setting weights and verifying traffic, with permissionless participation. Its existing 100,000-plus network providers are being transitioned—not 100,000 registered miners independently counted today. The October 15 reserve document explains that excess miner emissions become working capital to commission useful connectivity ahead of operator demand, rather than all being distributed immediately. The reserve is described as a separate multisig, with payments conditional on verified commitments and disclosed transfers. This connects a privacy-network service to Bittensor incentives. The document distinguishes current routing verification from stronger geographic/traffic verification that proposed programs would require; future reserve payouts and customer growth are not already proven. At the same finalized head, SN25 UR has 256 registered UIDs under Yuma; this is a direct check against interpreting the provider-transition headline as 100,000 on-chain UIDs.

Why 4 stars: An official mainnet announcement plus primary operating design advances a real network beyond a scheduled launch, while rollout counts remain bounded.

#04 · SN95 · Actualverified
★★★★★

SN95 Actual publishes DGX Station inference measurements

SN95 Actual’s October 15 case study introduces its e engine on NVIDIA DGX Station with Nemotron 3.5 Super VL. It reports preliminary decode measurements of 455 tokens/second for one stream and over 8,000 across 128 streams, with 0.58-second first-token latency for a fresh 8K-token prompt. The stated setup uses FP8 weights and MTP. This is a concrete effort to serve department-scale agent workloads on owned hardware. These are team measurements, not an independently reproduced comparison; a hosted model and a local open model are not interchangeable quality/cost benchmarks. The confidential relay claim concerns the described relay architecture, not proof of privacy on every endpoint.

Why 4 stars: A primary product case study supplies a named engine, hardware/model setup and measurable serving results.

#05 · Ecosystemdeveloping
★★★★★

eTAO emission-weight code is published; finalized runtime remains 479

The primary repository contains spec-480 eTAO per-subnet emission-weight work. Our finalized archive-node check at block 9,296,035 still reports runtime 479. Published implementation and active-chain deployment are separate facts: this report does not call spec 480 live or assume its new controls are already available. The current immunity and registration-cost decay parameters match yesterday’s checked values. This matters because subnet teams should follow actual activation gates, not treat every merged or branch commit as a mainnet upgrade.

Why 3 stars: Substantial protocol implementation is relevant, with the observed activation boundary retained.

#06 · SN3 · Teutonicverified
★★★★★

SN3 Teutonic tightens specialist improvement requirements

Primary SN3 Teutonic code now requires specialist own-source improvement to meet the domain threshold, with greater metric-display precision. This changes the qualification signal, rather than treating aggregate performance as sufficient. Community benchmark/threshold chatter was also collected, but its numerical improvements and hardware guidance are not promoted to an official independently verified result.

Why 3 stars: An explicit qualification rule changes what models must demonstrate.

#07 · SN9 · iotadeveloping
★★★★★

SN9 IOTA highlights upload constraints amid P2P issues

The October 16 digest attributes a warning that sub-30 Mbit/s upload is not viable to SN9 IOTA’s owner after a miner reported missed weight-upload windows. Primary v4.13.7 release code is available, but a release alone does not establish resolution of every peer-reachability failure. This makes network throughput an operating constraint, not only a GPU specification.

Why 3 stars: A specific attributed network requirement and active availability problem are useful to miners.

#08 · SN10 · Paretondeveloping
★★★★★

SN10 Pareton adjusts Kimi evaluation while a pause is reported

SN10 Pareton’s primary changes run Kimi K3 at concurrency 32 with eight prompts per tier and allow campaign-specific baseline drift ceilings. The October 16 digest reports a temporary evaluation pause tied to costly and unreliable 8×B300 instances, with a later round expected. This is a changed evaluation setup and attributed availability issue, not a verified restart time. A possible future burn reduction is not treated as already executed.

Why 3 stars: Concrete evaluation changes and a reported pause affect miner participation.

#09 · SN14 · Cacheondeveloping
★★★★★

SN14 Cacheon reports a faster baseline and updates speculative auditing

The October 16 digest attributes a Qwen3.8-27B baseline upgrade using native speculative decoding and FP8 KV caching to SN14 Cacheon, reporting 57 output tokens/second and a 72% improvement. Those measurements remain attributed. Primary changes audit recurrent MTP state and hybrid prefix keys and allow sealed decode budgets for speculative arenas. Baseline shifts affect the bar miners must beat; this is not an independently reproduced general-speed gain or proof that every validator adopted the update.

Why 3 stars: A changed reference baseline and primary evaluator work materially affect competition conditions.

#10 · SN19 · blockmachinedeveloping
★★★★★

SN19 Blockmachine reports its sixth buyback

The October 16 digest attributes a $7,475.77 sixth buyback/burn to SN19 Blockmachine, described as 89% above September. Its ambition to offset all miner emissions remains a goal, not an already achieved full offset. The transaction and accounting period were not independently decoded, so this remains an attributed commercial update rather than an audited burn total.

Why 3 stars: A specific reported buyback milestone is relevant while execution and full-offset claims remain bounded.

#11 · SN28 · SayGMverified
★★★★★

SN28 SayGM adds an SN53 Engy video route in miner code

SN28 SayGM’s merged gm-miner change adds an SN53 Engy MiniMax H3 video route. A separate documentation change describes DeepInfra GLM-5.3 and Flash sourcing. This advances yesterday’s video feature with an additional provider path and makes routing more explicit. Code availability is verified; successful paid production requests and provider-wide rollout were not exercised, and route documentation is not a universal confidential-compute guarantee.

Why 3 stars: A concrete counterpart-subnet routing implementation expands the previously announced feature.

#12 · SN37 · Aureliusdeveloping
★★★★★

SN37 Aurelius adds runtime-479 miner compatibility

SN37 Aurelius’ primary miner change explicitly supports the reviewed mainnet runtime 479. The October 16 digest reports mining live and a separate WT balance-transfer delay under investigation. Runtime compatibility is verified code; fleet activation, individual balances and complete recovery were not independently tested.

Why 3 stars: A concrete compatibility change and attributed activation/incident update affect participation.

#13 · SN41 · Almanacverified
★★★★★

SN41 Almanac adds recovery for transient forecasting failures

SN41 Almanac’s merged PR 58 adds retries, logging, timeouts and stale-weight fallback, with weights version 4. The primary change describes fallback for up to six hours when scoring data cannot be gathered. A digest attributes two zero-weight forecasting epochs to transient API failures. The patch is a concrete resilience change; the reported 6–8% incentive impact and fleet-wide adoption were not independently reconstructed. Validators need the updated deployment rather than assuming a merge repairs an already running instance.

Why 3 stars: A primary fix directly targets an availability failure affecting forecasting weights.

#14 · SN53 · engydeveloping
★★★★★

SN53 Engy reports a 50-billion-token day

SN53 Engy’s October 15 post says it processed more than 50 billion tokens the preceding day and links its statistics. This is a dated service-usage claim, not 50 billion paid customer tokens independently verified or equivalent revenue. The October 16 digest separately attributes a persistent post-disruption worker-degradation fix and recovered workers to the team. Together they describe demand and an operating repair; neither establishes audited profit or that every affected user has recovered.

Why 3 stars: A quantified usage milestone and specific reported repair warrant coverage with measurement limits.

#15 · SN54 · Yanezdeveloping
★★★★★

SN54 Yanez reports rewards delayed toward October 19

The October 16 SN54 Yanez digest attributes delayed Phase 4 Cycle 5 UAV rewards to scoring roughly two million submissions, including manual screen-replay reviews. Phase 5 execution is now expected by October 19, without an additional delay bonus. This revises timing rather than proving rewards have been finalized or paid. Original private messages and the payout vector were not independently read.

Why 3 stars: An attributed payment/phase delay materially affects miners and needs follow-up.

#16 · SN62 · Ridgesverified
★★★★★

SN62 Ridges explains dynamic upload prices

SN62 Ridges’ October 15 post and upload-pricing guide specify default submission pricing with a $5 floor, approximately 15% increase per purchased upload, and a 30-minute half-life between purchases. Unused alpha can carry forward, with a top-up flow when the price changes during submission. This changes the cost and timing of joining coding competitions; it is not a fixed $5 fee or a guarantee that an upload will earn rewards.

Why 3 stars: Concrete published admission economics affect participants directly.

#17 · SN64 · Chutesdeveloping
★★★★★

SN64 Chutes details its Parallax training-cost example

SN64 Chutes’ October 15 post describes an 8B pretraining run across rented RTX 5090s over the internet:574 billion tokens in 52 hours, around $6,500 and $11.27 per billion tokens. Four CPU VMs are described as syncers. This is a concrete team-reported training example; retail-price comparisons with a differently sized/reference run are estimates rather than like-for-like independent benchmarking. A new post about a run is not automatically the run’s completion date.

Why 3 stars: A named workload and disclosed setup add useful evidence, with cost/comparison limits retained.

#18 · SN66 · conjecturesdeveloping
★★★★★

SN66 Conjectures reports verified DEFLATE parsers

The dated digest reports three DEFLATE submissions released as a verified Rust crate, with Lean proofs of parser correctness and claimed speed/compression gains over named comparators. This is attributed release evidence, not a benchmark we reran or proof every compression operation is universally superior. A separate public report describes requiring AI chat logs for new proof bounties; its detailed bonus amounts were not verified against original rules and are not presented as confirmed payouts.

Why 3 stars: A reported usable verified-parser artifact is distinct from casual benchmark chatter.

#19 · SN78 · Umideveloping
★★★★★

SN78 UMI previews its product path; paid weights are not payouts

SN78 UMI’s October 16 trailer and caption describe pre-orders as opening soon. Inspected frames show SignRush, miner/model competition and a reward-curve discussion; the full audio was not transcribed, so further media-only specifications are not inferred. Separately, the dated digest reports certified C5 paid-service allocation weights, while explicitly keeping on-chain reward activation pending. A published allocation table is not an executed alpha payment, and a product trailer is not completed preorder availability.

Why 3 stars: New product context and a scoring milestone matter while the payment gate remains unresolved.

#20 · SN81 · Reliquaryverified
★★★★★

SN81 Reliquary adds 1,893 supervised-training problems

SN81 Reliquary’s primary environment release appends 1,893 competitive-code problems for supervised fine-tuning. Its release notes keep previous training indices and evaluation/qualification sets unchanged and describe decontamination against those held-out sources. This expands training material without claiming a new benchmark score; data-policy implementation is not an independent contamination audit.

Why 3 stars: A specific training-data release is substantive and its evaluation boundary is documented.

#21 · SN86 · OnSaleverified
★★★★★

SN86 was removed and re-registered; sale terms are unverified

Late-found direct chain evidence places NetworkRemoved at block 9,289,316 on October 15 at 14:26:48 UTC, in extrinsic 18, alongside a new registration queue entry. NetworkAdded follows at block 9,289,319 at 14:27:24 UTC; the registration-height storage and new owner key match. The queued lock is 493.992245801 TAO, a protocol registration lock—not a negotiated purchase price. The screener now labels the slot OnSale, but that label does not identify a buyer or prove a sale. These events precede yesterday’s stated cutoff by minutes but occurred after its recorded node head, so they are explicitly backfilled today. The identity of any new operating team remains unconfirmed.

Why 3 stars: Decoded events and before/after storage establish a real slot replacement rather than inferring a sale from price or a name.

#22 · SN90 · KubeTEEverified
★★★★★

SN90 KubeTEE publishes a new hardware acceptance policy

SN90 KubeTEE’s October 16 documentation change says new GPU nodes must use Blackwell or Vera Rubin and new CPU nodes sixth-generation Xeon or EPYC with the specified confidential-compute support. Existing Hopper capacity is deprecated, with removal targeted as new capacity comes online around November. This is published operator policy, not evidence every older node was removed today or that every advertised hardware configuration has been independently validated.

Why 3 stars: A published acceptance/deprecation rule materially changes node planning.

#23 · SN91 · cascadedeveloping
★★★★★

SN91 Cascade reports first place in a paper-trading competition

SN91 Cascade’s October 15 post says its Gnomon time-series harness with GLM 5.2 finished first of 26 entries across five weeks: +14.8% on a $10,000 paper account over 23 trades. It contrasts GLM 5.2 alone at tenth and −7.7%. The relevant development is a dated application result for its forecasting tooling. This is a team-reported simulated competition, not live investment performance, a causal controlled experiment or a promise of future returns. Connecting the harness to time-series inference is described as the next step.

Why 3 stars: A specific dated applied result merits coverage while paper-account and independent-reproduction limits prevent overstatement.

#24 · SN92 · REAXdeveloping
★★★★★

SN92 REAX revises scoring while competition awards remain gated

SN92 REAX’s October 16 digest reports active inference mining and a capacity-scoring revision following a delegation fix. Primary release notes for 1.2.0rc5 retain owner-signed approval before competition awards and hold the engine track in code. This prevents the scheduled October 16 competition time being mistaken for independently verified reward execution. Current identity is REAX; commits in the legacy MicroTensor repository are not automatically attributed to today’s slot. The 12:49 UTC alpha/TAO snapshot is −16.04% over 24 hours and +2,485.58% over seven days, which shows volatility rather than proving one catalyst.

Why 3 stars: Substantial scoring/award-gate changes deserve coverage without turning a scheduled competition into confirmed payouts.

#25 · SN97 · Albedodeveloping
★★★★★

SN97 Albedo reportedly halted evaluation

The October 16 digest attributes confirmation of a halt at 16:00 UTC on October 15 to SN97 Albedo. Further changes were teased, with no verified specification or restart time. This is an availability update and open follow-up, not a completed relaunch or evidence the slot has been deregistered.

Why 3 stars: Reported evaluation availability directly affects participants.

#26 · SN102 · ConnitoAIverified
★★★★★

SN102 ConnitoAI’s owner coldkey swap is finalized

At block 9,294,106 on October 16, our node decodes ColdkeySwapped in extrinsic 14 and swap_coldkey_announced execution; SN102 ConnitoAI’s owner storage changes from the prior key to the named successor. This verifies execution, not merely a scheduled announcement. A coldkey rotation alone does not establish an off-chain sale, buyer identity or payment. Separately, the dated channel digest reports v0.7.0’s residual-expert task switch and temporary RPC-related fallback weights; that fleet/recovery description remains attributed rather than an independently reconstructed reward history.

Why 3 stars: A decoded executed key change resolves ownership-state monitoring without inventing transaction economics.

#27 · SN105 · Beamdeveloping
★★★★★

SN105 Beam publishes audit visibility; the global fix remains open

SN105 Beam’s October 16 UTC post advertises endpoints for transfers, assignments, scores and reward calculations. This adds a path for participants to inspect recorded outcomes. It does not resolve the underlying room/S3 assignment allegations: the dated digest attributes continued investigation and says the global fix is not yet deployed. The endpoint demo was not fully reviewed or reconciled against historical transfers, so neither universal audit completeness nor recovery of disputed rewards is asserted. A secondary Box-integration lead lacked a verified counterpart announcement and is not promoted as a new confirmed partnership.

Why 3 stars: A transparency feature and a material unresolved incident belong together, avoiding an unsupported all-clear.

#28 · SN108 · ChipForgedeveloping
★★★★★

SN108 ChipForge closes Quest1 and previews a larger NPU task

The October 16 digest reports Quest 1’s October 15 21:00 UTC deadline, with timely submissions evaluated and a further 24-hour reward period for the winner. Quest 2 is described as a larger edge-AI NPU with a custom compiler; full specification and timing remain upcoming. The 12:49 UTC alpha/TAO snapshot is −21.19% daily, which is a research trigger and not evidence the scheduled transition caused the move.

Why 3 stars: A specific competition transition affects participation; the next task is accurately labelled planned.

#29 · SN118 · Dittodeveloping
★★★★★

SN118 Ditto describes a new development-funding allocation

The October 16 digest attributes a plan to direct 75% of miner emissions to product development to SN118 Ditto, alongside stuck-agent work and a future source reveal. This is different from yesterday’s reported 70% burn/gamma settings: the two descriptions are not silently equated or added together. Finalized weights and funding transfers were not decoded, so exact implementation and reconciliation remain open. The team’s separate roughly-$1 pull-request-review example is a workload claim, not a universal cost guarantee.

Why 3 stars: A reported major funding policy warrants notice while conflicting mechanisms require verification.

#30 · SN120 · Affinedeveloping
★★★★★

SN120 Affine weight complaints remain unresolved

Yesterday’s primary recovery work does not establish a fleet-wide all-clear. The October 16 SN120 Affine digest continues to report unchanged weights and active miners missing rewards, with a team account asking for action. Its exact duration and individual losses were not independently reconstructed. A separate public proof-of-work registration report is relevant to access, but does not settle the weight-update incident.

Why 3 stars: A continuing reported reward failure remains material despite published fixes.

#31 · SN121 · sundae_bardeveloping
★★★★★

SN121 Sundae Bar’s bundle challenge has a reported scoring issue

The October 16 digest says SBC30 opens with folder-based submissions and reports an over-strict cross-file repetition check, with a fix scheduled for SBC31. It also reports removal of exposed construction_notes from the challenge API. These are attributed operational findings, not independently replayed exploit or grading results. Yesterday’s bundle support does not imply the new format is free of scoring faults.

Why 3 stars: A new challenge and specific reported scoring limitation affect submissions.

#32 · SN122 · CookingTAOdeveloping
★★★★★

SN122 CookingTAO separates total revenue from monthly revenue

The October 16 UTC post from SN122 CookingTAO reports $1,064.84 in total beta-v2 revenue, including $505.44 this month, and a $17.69 alpha buyback test. This clarifies yesterday’s approaching-$1,000 language: the new figure is cumulative, not verified monthly recurring revenue. Automated real buybacks are still planned after beta. Its mining-management product provides the business context; revenue and the test transaction were not independently audited.

Why 3 stars: A new concrete commercial milestone also corrects an easy-to-confuse revenue period.

#33 · Ecosystemverified
★★★★★

New public Shizzy episode added to the video library

The October 15 public upload “TAO RISES FROM HELL! 🔥 Bittensor Is Making HUGE Moves!” is now the default video, with 18:44 duration confirmed by player metadata. Both Videos and Live tabs were checked. SN48 Quantum Compute remains a completed replay, the October13 members video stays correctly restricted, and no new upcoming stream was verified. Removed or postponed episodes remain disabled.

Why 2 stars: Verified channel metadata keeps the public player and library current.

#34 · SN21 · AdTAOverified
★★★★★

SN21 ADTAO adjusts scoring when efficiency cannot be measured

Primary SN21 ADTAO code scores entries without measurable efficiency on cost and conversions. This makes the fallback evaluation basis explicit rather than treating missing efficiency as a valid measured value. It is an implemented scoring change, not independently verified advertiser ROI or validator-wide adoption.

Why 2 stars: A specific primary fallback rule improves interpretation of miner scores.

#35 · SN44 · Scoredeveloping
★★★★★

SN44 Score reports restored run data; another detector is planned

The October 16 digest attributes a fixed read error and restored run JSON to SN44 Score. Fallen-person detection is described as expected next, not already verified live. Yesterday’s scoring/enforcement complaints are not automatically resolved, and the new box-overlay social clip was not fully reviewed as a release demonstration.

Why 2 stars: A bounded data-access repair is kept separate from future detection support and unresolved scoring.

#36 · SN49 · Nepher Roboticsdeveloping
★★★★★

SN49 Nepher Robotics plans an NVIDIA GTC Berlin appearance

SN49 Nepher Robotics’ October 15 post says it will join the robotics community at NVIDIA GTC Berlin on October20–22 and describes its simulation-to-hardware policy workflow. This is a planned appearance, not a new NVIDIA customer contract or independently validated days-versus-months performance result.

Why 2 stars: A dated official upcoming appearance is useful without inflating it into a commercial partnership.

#37 · SN65 · True Performance Networkdeveloping
★★★★★

SN65 TPN teases November; TPN-006 remains the current competition

SN65 TPN’s October 16 teaser artwork says “xx Nov 2026”; its caption promises something next month without naming a release day or specification. That is an upcoming reveal. The dated digest separately reports TPN-006 activation with its 8 GiB Ministral-3-8B target and 25% competition weight, advancing yesterday’s opening announcement. Neither establishes a successful optimized model already meeting the target.

Why 2 stars: The teaser was inspected and kept distinct from a reported operational competition.

#38 · SN117 · everyframe.studioverified
★★★★★

SN117 Everyframe prepares v0.5.7 with clearer provider failures

SN117 Everyframe’s primary miner change preserves provider failure categories and prepares v0.5.7. Distinguishing a provider fault from a generic worker error helps operators diagnose failed service. This follows yesterday’s balance/recovery release; merged preparation is not proof that all workers upgraded or that all external provider errors have disappeared.

Why 2 stars: A bounded operational repair improves diagnosis without overstating rollout.

04

Audit trail

Coverage notes

Searched

  • 128 current subnet profiles; dated channel digests, official accounts, aliases and primary repository changes.
  • Signed-in @ShizzyUnchained: Grok discovery, corrected top-five attention query, omission review and direct Const Posts/Replies.
  • AlphaGap public pages, SubnetRadar/Moments, TAO Daily and partner/product sources; preceding seven editions.
  • Direct finalized archive-node owner/registration/network comparisons and decoded targeted events, with bounded historical range attempt.
  • YouTube Videos and Live tabs; player title, duration, access and completed-stream metadata.

Public-data gaps

  • Public X samples and Grok do not provide exhaustive coverage or reliable mention counts; inaccessible accounts and media outcomes are retained in the source audit.
  • Full-window historical storage querying returned RPC4003. Targeted decoded events verify the reported changes, but other temporary intermediate events cannot be excluded. Off-chain buyer identities and sale prices are not inferred.
  • Private Discord originals were not read. Digest-only claims remain attributed and developing; community posts are not automatically team statements.
  • Some candidate videos were only partially inspected or remain inaccessible; no additional feature claims are inferred from unreviewed media. AlphaGap paid/live intelligence was not inspected.
  • Revenue, usage and benchmark figures are attributed to their publishers, not independently audited. No paid request, wallet transaction or benchmark rerun was performed.