Skip to main content

ROVR Network

ROVR Network (ROVR) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

ROVR Network — an AI/Data / DePIN project: it builds a “decentralized, real-time 3D spatial data network” for Spatial AI and intelligent transportation. Participation mechanics: users collect road data via devices (TarantulaX/LightCone) and an app, and rewards are paid in the ROVR token. Onchain SSOT: an SPL token on the Solana network.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a network/platform for collecting and productizing high‑precision 3D/4D road data (HD maps, datasets) with rewards for participants.
  • Who it’s for: drivers/participants who collect data; companies/developers who need spatial datasets/HD maps for autonomous transport, robotics and VR/AR.
  • Why onchain/token: the ROVR token is used to pay rewards for “mapping mileage” and data quality, as well as for the “staking‑to‑device” mechanics (obtaining devices for a stake).
  • What you can actually touch (Tier‑1): the ROVR Open Dataset (GitHub) and the project documentation (GitBook).

How it works (very briefly)

  1. The user does: connects a device (TX/LC) and collects trip data; uploads the data via the ROVR app/service.
  2. The system does: evaluates “mapping mileage” and data quality (tiers/coefficients) and calculates the reward in ROVR.
  3. The user gets: payouts in ROVR (per the tokenomics rules) and access to the “staking‑to‑device” program (optional).
  4. Where the blockchain is: issuance/circulation of the ROVR token — onchain (Solana); payouts/stake — via onchain transactions.
  5. Token role (if any): incentivizes data collection (rewards), ensures long‑term participation via stake‑based acquisition of devices; the tokenomics claim a buyback‑and‑burn from data consumer revenue.

Quick links: AI thesis fit

Project passport

Field Value
Project name ROVR Network
Also known as (aliases) ROVR; $ROVR
Logo (logo) ../assets/233_rovr-network_logo.ico
Token symbol (ticker) ROVR
Category AI/Data | DePIN | Infra
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) 2025-04-26 (TGE)
Project status (status) active
Token (standard) SPL
Token contract FgQ3sxj54SmVzttkxuK4bdiEnUNi6kF9Hyx3ezKW72hn
Token model (token_type) utility (rewards + staking-to-device + burn)
Max supply 10,000,000,000 (fixed supply)
Issuance fixed + buyback-and-burn
Tokenomics (tokenomics, brief) 51% rewards; base rewards “per km” + quality tiers; annual halving base rewards
Governance ROVR Foundation Ltd.
Admins/keys —
Audit —
Bug bounty —
Team (team) ROVR Foundation Ltd. + Rovr Labs, Inc.
Funding (investors/funding) angel funding: Outlier DePIN Accelerator (Borderless/Peaq)
AI component (ai_component) spatial AI (HD maps + 3D/4D datasets)
Use‑case (use_case) autonomous transport + robotics
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 1 / 2
Last verified 2026-02-11

General project overview

ROVR Network builds infrastructure for the mass collection of high‑precision spatial data (3D/4D) — as raw material for autonomous driving systems, robotics and other Spatial AI applications. The documentation names the shortage of quality 3D datasets and HD maps, compared with the availability of text data for LLMs, as the main problem.

The project proposes a “DePIN approach”: participants collect road data using devices (TarantulaX/LightCone) and an app, and then receive rewards in the $ROVR token. The ROVR Open Dataset repository is publicly available as an example dataset for perception tasks (depth estimation / object detection / semantic segmentation).

Features/modules

  • Devices and data collection: TarantulaX (TX) and LightCone (LC) as ways of collecting spatial data.
  • Rewards tokenomics: payouts by mileage and data quality; “revisit decay”.
  • Staking-to-device: obtaining devices for a ROVR stake.
  • Open Dataset: a public dataset and tools on GitHub.

Typical scenarios

  • Scenario 1: a participant collects/uploads data → receives $ROVR per the tokenomics rules.
  • Scenario 2: a participant stakes $ROVR to obtain a device → places an order via the staking-to-device procedure.
  • Scenario 3: a researcher uses the ROVR Open Dataset → trains/tests perception models.

Getting started (wallet/network)

  • What you need: a Solana wallet (for example, Phantom), an account/access to the ROVR App; ROVR tokens are needed for staking-to-device.
  • Network/chain: Solana.
  • Fees: Solana network fees for transfers/staking/interaction with the dApp.

Architecture/tech (non‑AI)

  • Components: data collection devices (TX/LC), an app/service for uploading and evaluating data, offchain processing pipelines, the $ROVR token (Solana).
  • Participant roles: data collectors, data consumers, operators/team, Solana validators.
  • Where logic runs: data collection/processing/evaluation — offchain; token issuance/accounting/staking — onchain.
  • Dependencies: Solana wallets and RPC; an RTK service (GEODNET is mentioned in the docs).

Token/economics (expanded, no forecasts)

  • Token utility: rewards to participants for data collection; staking-to-device (collateral) for obtaining devices.
  • Protocol necessity drivers: the token is the main instrument of incentivization and value distribution in the data network.
  • Who pays fees: users during onchain operations.
  • Where fees go: network fees — to Solana validators; the tokenomics claim the following distribution of data consumer revenue: 60% buyback&burn $ROVR, 20% RTK fees → buyback&burn $GEOD, 20% operating expenses.
  • Issuance/burn: fixed supply 10B; a “permanent burn mechanism” (buyback&burn).
  • Security/incentive mechanisms: quality tiers, revisit decay; staking-to-device with a 1‑year lock and penalties for early exit/inactivity.
  • Distribution and token issuance schedule: 51% rewards; team 9m cliff + 36m vest; investors TGE unlock + vest; ecosystem vest (tokenomics).
  • Treasury: — (the Tier‑1 shown contains no treasury addresses/rules).

Governance

  • Who makes decisions: ROVR Foundation Ltd. (per the docs).
  • How protocol parameters change: the docs mention R2FCs (requests for comments) as a community engagement mechanism.
  • Where decisions are discussed/made: documentation + Discord/X.
  • Keys/multisig: —.

Security and incidents

  • Audits: the CMC card has a link to Certik Skynet (not Tier‑1 for the project’s claims).
  • Bug bounty: not claimed.
  • Incidents: not found in Tier‑1 sources.
  • Threat model: risks of data quality and potential centralization of processing (the docs mention ROVR Inc as the primary data processor).

Project status and timeline

  • Current status: the token is on the Solana network; the TX/LC devices and staking-to-device are described.
  • Key releases/milestones: TGE 2025-04-26; Tokenomics and User Guide in GitBook; the shipping of staking devices is indicated as ~2026-01-15.
  • Roadmap: https://rovr-network.gitbook.io/rovr-docs/journey-into-rovr/journey-into-rovr-unveiling-the-veil

Ecosystem/integrations

  • Integrations: Solana wallets (example: Phantom); the dataset GitHub repository.
  • Partners: GEODNET (RTK) is mentioned in the docs; Outlier DePIN Accelerator / Borderless / Peaq are mentioned as part of angel funding/acceleration.
  • Where it’s actually used: the ROVR Open Dataset for perception research tasks; the claimed HD‑map/3D‑data products are described in the Journey series.

AI component of the project

  • What is real AI here? Tier‑1 sources describe the collection/preparation of 3D/4D data and HD maps as a foundation for Spatial AI; a dataset and a description of perception tasks are published on GitHub.
  • What is truly onchain? the ROVR token (SPL, Solana) and onchain staking mechanics (staking-to-device).
  • Why is a token needed? rewards for data collection and a long‑term participation mechanism (obtaining devices for a stake); the tokenomics claim a buyback‑and‑burn from data consumer revenue.
  • Red flags (based on the information found): AI‑washing — moderate (data infrastructure rather than an “AI product”), onchain‑washing — moderate (the main data processing is offchain), token‑washing — moderate; what to double‑check — the staking dApp contract addresses and the actual implementation of the buyback/burn; key AI‑washing risks — the absence of verifiable model quality metrics.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 3
Onchain necessity medium 2
Token necessity medium 1
Evidence Tier‑1 present 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 3.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the system collects and prepares datasets/HD maps for perception tasks (depth/object detection/segmentation) and Spatial AI training.
  • Evidence: Tier‑1 — https://github.com/rovr-network/ROVR-Open-Dataset ; https://rovr-network.gitbook.io/rovr-docs
  • Why sufficient / why not (one line): there is a description of the data type and the intended tasks for AI.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the ROVR Open Dataset and tools/a usage description for research tasks are published.
  • Evidence: Tier‑1 — https://github.com/rovr-network/ROVR-Open-Dataset
  • Why sufficient / why not (one line): this is a verifiable artifact (dataset) for AI development.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: the Journey page contains comparative figures (for example, “Recall Rate 90%+”, “Accuracy 0.5m/0.2m”), but without a methodology.
  • Context (version/date/how measured): not disclosed to a sufficient extent in Tier‑1.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs/journey-into-rovr/journey-into-rovr-unveiling-the-veil
  • Why sufficient / why not (one line): without a reproducible methodology, the metrics are not counted as verified.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): the docs describe in detail the data collection methodology, the devices (RTK/IMU/LiDAR) and the process of generating HD maps/data.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs
  • Why sufficient / why not (one line): a technical description exists at the level of hardware/processes, albeit without the full pipeline code.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: the ROVR SPL token: FgQ3sxj54SmVzttkxuK4bdiEnUNi6kF9Hyx3ezKW72hn
  • Evidence: Tier‑1 — https://explorer.solana.com/address/FgQ3sxj54SmVzttkxuK4bdiEnUNi6kF9Hyx3ezKW72hn?cluster=mainnet ; https://rovr-network.gitbook.io/rovr-docs/rovr-tokenomics/rovr-tokenomics
  • Why sufficient / why not (one line): the network/contract are confirmed by the explorer and the tokenomics section in the docs.
  • Conflict note (if any): Solscan does not return token details in the text snapshot (page loading limitation).

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: staking-to-device: staking ROVR to “redeem hardware devices” and the lock/unlock rules.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs/user-guide/rovr-staking-to-device-user-guide
  • Why sufficient / why not (one line): this is onchain mechanics beyond “just a token transfer”.
  • Conflict note (if any): the addresses of specific contracts/programs are not provided on the page.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the core functions of data collection/processing and data sales can work offchain; onchain is the economic layer and incentives.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs
  • Why sufficient / why not (one line): the docs describe offchain processing pipelines; onchain is not claimed as the place of inference/processing.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, $ROVR.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs/rovr-tokenomics/rovr-tokenomics
  • Why sufficient / why not (one line): the tokenomics describe supply/allocation/mechanics.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): a direct “payment with the token for access to the service” is not described; the token is used as rewards/stake.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs/rovr-tokenomics/rovr-tokenomics
  • Why sufficient / why not (one line): the tokenomics describe rewards and burn from data consumers, but not a process of users paying with the token.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): rewards per kilometer and for data quality; staking-to-device with unlock/penalty conditions.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs/rovr-tokenomics/rovr-tokenomics ; https://rovr-network.gitbook.io/rovr-docs/user-guide/rovr-staking-to-device-user-guide
  • Why sufficient / why not (one line): the incentive/penalty mechanics are described in the docs.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is not explicitly described in Tier‑1 sources.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs
  • Why sufficient / why not (one line): the docs pay more attention to rewards/devices/data than to governance processes.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the role of the token as rewards/stake can be implemented in different ways; the “irreplaceability” of ROVR specifically is not proven.
  • Evidence: Tier‑1 — https://rovr-network.gitbook.io/rovr-docs/rovr-tokenomics/rovr-tokenomics
  • Why sufficient / why not (one line): the tokenomics contain no argument for “why it cannot be replaced with another asset”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://rovr-network.gitbook.io/rovr-docs description of the goal/approach, the devices and the data collection/productization process
Tier‑1 https://rovr-network.gitbook.io/rovr-docs/rovr-tokenomics/rovr-tokenomics fixed supply 10B, allocation, rewards formulas, buyback-and-burn
Tier‑1 https://rovr-network.gitbook.io/rovr-docs/user-guide/rovr-staking-to-device-user-guide staking-to-device: staking conditions and lock/unlock rules
Tier‑1 https://github.com/rovr-network/ROVR-Open-Dataset public dataset and description of the AI tasks/data type
Tier‑2 https://coinmarketcap.com/currencies/rovr-network/ Aggregator: reference profile and links (not Tier‑1).
Tier‑1 — the Solscan page for the contract does not extract token details in the text snapshot (tool limitation)

No comments to display

Back to top