Skip to main content

Atlas Navi

Atlas Navi (NAVI) — 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).

Atlas Navi — an AI/ComputerVision / Consumer app / NFT project: a “drive‑to‑earn” mobile navigation app that uses computer vision (smartphone camera/dashcam) to detect road events and improve routing; the NAVI token (ERC‑20) is used in the app economy and NFT mechanics.

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: “drive‑to‑earn” mobile navigation with 3D vehicle NFT and a system of rewards for mileage/data.
  • Who it’s for: drivers (app users), owners/buyers of vehicle NFT, partners (fleets/brands/cities — per the docs).
  • Why onchain/token: the NAVI token is needed to buy/upgrade NFTs and to pay for some of the paid features; the blockchain records the token/part of the economic rules.
  • What you can actually touch (Tier‑1): https://www.atlasnavi.com/

How it works (very briefly)

  1. The user does: launches navigation and (optionally) enables camera‑based road analysis.
  2. The system does: CV/ML models detect road events (police/accidents/potholes/roadworks/traffic, etc.) and use this for routing and for sharing the information with other drivers.
  3. The user gets: more “informed” navigation + game/economic mechanics: rewards (internal points, described as $MILE) for mileage/data contribution.
  4. Where the blockchain is: the NAVI token is an ERC‑20 on Ethereum; the docs describe NFT purchases/upgrades and payments in NAVI.
  5. Token role: NAVI is used for premium features, buying/upgrading vehicle NFTs, participation in game mechanics and voting (per the docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name Atlas Navi
Also known as (aliases) AtlasNavi; Drive‑to‑Earn navigation; NAVI; MILE (in‑app rewards points)
Logo (logo) ../assets/212_atlas-navi_logo.png
Token symbol (ticker) NAVI
Category AI/ComputerVision | NFT | Consumer app
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) unknown (the app is available in the App Store/Google Play; the docs describe a public beta)
Project status (status) active (app + token on mainnet; some mechanics are described as beta/plans)
Token (standard) ERC-20
Token contract 0xFc1C93a2507975E98b9d0E9260Ded61A00152BF1
Token model (token_type) utility (governance)
Max supply 300,000,000 NAVI (cap per Etherscan and the docs)
Issuance capped supply + minting via the owner (initMint/mint with a 48h delay) + burn (per the code on Etherscan)
Tokenomics (tokenomics, brief) vesting/distribution and utility are described in the docs; premium payments in fiat imply a NAVI buyback (per the docs); the docs mention a possible burn of part of the buyback
Governance DAO/voting rights are claimed (per the docs)
Admins/keys owner‑controlled (Ownable contract; ownership not renounced per the code/contract page)
Audit unknown: the docs mention a future “audit from Certik”, but the report is not attached; no audit is listed on Etherscan
Bug bounty —
Team (team) experienced team (claimed in the docs without the roster)
Funding (investors/funding) an EU innovation grant is claimed + quarterly audits during development (per the docs and the website)
AI component (ai_component) CV/ML road event detection from video
Use‑case (use_case) navigation + drive-to-earn + vehicle NFTs
DecAI Fit — AI thesis fit 6/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 3 / 3
Last verified 2026-02-11

General project overview

Atlas Navi is a mobile navigation app that claims to use computer vision and machine learning to continuously analyze the road via the smartphone/dashcam camera and automatically detect events (police, accidents, lane‑level traffic, roadworks, potholes, parking, etc.). The detections are used for more efficient routing and for sharing “signals” with other drivers in the app’s network.

On top of the utilitarian navigation, a “drive‑to‑earn” economy is described: for mileage/data contribution the user receives in‑app rewards (referred to as $MILE points), which can be exchanged for NAVI and spent in the ecosystem on vehicle NFTs, upgrades/repairs/“refuel”, premium features, game modes and participation in voting (per the docs).

Features/modules

  • AI navigation / CV detections: real‑time detection of road objects and events from video.
  • Drive‑to‑Earn: rewards for mileage/data via in‑app points ($MILE) with exchange into NAVI (per the docs).
  • Premium app features: PRO features (cloud storage, group trips, live streaming, multi‑stop routing, fleet accounts, etc.), paid in fiat or NAVI (per the docs).
  • Vehicle NFTs and garage economy: purchase, upgrades/repairs/maintenance, marketplace; 3D models and licensing (per the website and the docs).
  • Social and “fleet” scenarios: group trips, live stream, dispatching/tracking (per the website and the docs).

Typical scenarios

  • Scenario 1: a driver enables navigation and AI detection → receives event‑aware routing and accumulates $MILE points.
  • Scenario 2: a driver buys a vehicle NFT for NAVI → gets the ability to convert $MILE into NAVI and spend NAVI on upgrades/repairs/games (per the docs).
  • Scenario 3: a corporate client (fleet) connects a paid fleet account → receives dispatching/tracking/statistics and pays in NAVI (per the docs).

Getting started (wallet/network)

  • What you need: install the app (App Store / Google Play), register an account; in the beta, access is via an invite/referral code (per the docs).
  • Network/chain: for the token — Ethereum (ERC‑20 NAVI); the app’s internal logic and AI run offchain.
  • Fees: Ethereum onchain fees for transfers/operations with NAVI and, probably, NFTs (if they are onchain; NFT contract addresses were not extracted from Tier‑1).

Architecture/tech (non‑AI)

  • Components: iOS/Android mobile app; back‑end/network layer for signal exchange and accounts; onchain NAVI token (ERC‑20); NFT subsystem (described in the docs/website).
  • Participant roles: drivers/users; vehicle NFT owners; third parties (fleets/cities/brands — as potential data buyers/advertising accounts per the docs); owner/admin of the token contract (Ownable).
  • Where logic runs: AI detection and routing — offchain (on the smartphone and in services); onchain — the NAVI token and transactions on Ethereum.
  • Dependencies: mapping provider (per the docs), mobile cameras/dashcams, Ethereum RPC/wallets for operations with NAVI; video storage — device/cloud (a premium feature per the docs).

Token/economics (expanded, no forecasts)

  • Token utility: per the docs, NAVI is used for premium features (Atlas Navi PRO), buying/maintaining/upgrading vehicle NFTs, participation in games/competitions, payment for data access and in governance voting.
  • Protocol necessity drivers: some payments allow fiat (with a subsequent NAVI buyback per the docs), but for a number of mechanics “inside the ecosystem” NAVI is claimed as the primary payment token (NFTs, upgrades, data/ads accounts, etc.).
  • Who pays fees: Ethereum onchain fees for operations with NAVI are paid by users/counterparties; offchain payments (subscriptions) depend on the chosen payment method.
  • Where fees go: the docs describe a buyback mechanic for fiat payments; the distribution of revenue between participants/the treasury is not verified by addresses/contracts.
  • Issuance/burn: NAVI is capped at 300,000,000; the contract allows the owner to initiate a mint with a 48h delay, and there is a burn function (per Etherscan). The docs mention: “if the economy allows — burn 25% of the NAVI buyback” (conditional).
  • Security/incentive mechanisms: incentives — drive‑to‑earn rewards in $MILE points with conversion into NAVI; “value sinks” via repairs/refuel/maintenance of vehicle NFTs (per the docs).
  • Distribution and token issuance schedule: the docs contain vesting schemes and the distribution (TEAM/DEVELOPMENT/MARKETING/REWARDS/LIQUIDITY/ADVISORS, etc.); the details depend on the specific pool and the TGE date (not tied to an onchain event in the extracted Tier‑1 sources).
  • Treasury: owner control and the distribution of treasury funds/wallets are not explicitly disclosed in Tier‑1.

Governance

  • Who makes decisions: the docs claim “DAO / Voting rights” for NAVI holders (e.g., which cars/features to release).
  • How protocol parameters change: the governance mechanism is described at the level of product/promises; smart‑contract voting procedures were not extracted from Tier‑1.
  • Where decisions are discussed/made: official channels (X/Discord/Telegram) and the docs.
  • Keys/multisig: the token contract is Ownable (the owner address is specified in the source code on Etherscan); multisig/timelock are not confirmed by Tier‑1.

Security and incidents

  • Audits: the docs mention an intention to conduct an audit “from Certik”, but the report is not attached; Etherscan shows “No Contract Security Audit Submitted”.
  • Bug bounty: —.
  • Incidents: public post‑mortems not found/not extracted.
  • Threat model: the key risk is the centralized administration of the token contract (minting by the owner), the security of the mobile app/backend and the quality/authenticity of camera data; Ethereum onchain risks (MEV/fees/phishing).

Project status and timeline

  • Current status: the product — public beta (per the docs), the NAVI token — on Ethereum mainnet.
  • Key releases/milestones: the app is available in the App Store/Google Play; the docs claim that the product is “already launched … as public beta”.
  • Roadmap: a roadmap page is published in the docs (graphics; detailed items are not listed as text on the page).

Ecosystem/integrations

  • Integrations: App Store / Google Play; the Ethereum NAVI token; wallet connection (a “wallet connect feature” is mentioned in the docs).
  • Partners: the docs mention Machinations.io (audit/check of the economy’s sustainability) and the EU grant; the website has “Trusted by” logos, but without formalized terms.
  • Where it’s actually used: the main use is mobile navigation and the app’s internal economy; onchain use — the NAVI token.

AI component of the project

  • What is real AI here? Tier‑1 docs describe ML/CV neural networks that analyze the camera video stream in real time and detect road objects/events; training on 100 TB of images/video is claimed.
  • What is truly onchain? the ERC‑20 NAVI token on Ethereum; the NFTs/economy are claimed to be “on blockchain”, but NFT contract addresses are not specified in the extracted Tier‑1 pages.
  • Why is a token needed? NAVI is needed for premium features, buying/upgrading/maintaining NFT cars, and is also claimed for DAO/voting and B2B purchases of data/ad placements.
  • Red flags (based on the information found): AI‑washing — medium (there is a technical description, but no metrics/benchmarks or public model code); onchain‑washing — medium (the AI/routing core is offchain, onchain = token/economy); token‑washing — medium (some features are available for fiat, NAVI is partially replaceable).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as current product functionality, not as an “intent in the roadmap”.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/product-details/technical ; https://docs.atlasnavi.com/
  • Why sufficient / why not (one line): the materials describe AI detection as a component that is already being implemented, not as a plan.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): CV/ML neural networks detect road objects/events from video (police/accidents/pedestrians/potholes/roadworks/traffic, etc.) and help improve routing.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/product-details/technical ; https://www.atlasnavi.com/
  • Why sufficient / why not (one line): there is an explicit Tier‑1 description of the AI detection functions and examples on the website.
  • Conflict note (if any): some of the claims are marketing and not backed by metrics.

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): product videos are published and live demos/comparisons with other navigators are described (a claim in the docs).
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/product-details/technical ; https://www.atlasnavi.com/
  • Why sufficient / why not (one line): there are public video materials and a Tier‑1 claim about demos/tests.
  • Conflict note (if any): video is not a strict scientific benchmark.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: “processes 100 times more data” and “analytics 25 times/sec” are claimed, but without measurable quality metrics (accuracy/precision/latency) in the extracted Tier‑1 sources.
  • Context (version/date/how measured): — (not specified in the extracted sources)
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/product-details/technical ; https://www.atlasnavi.com/
  • Why sufficient / why not (one line): verifiable quality metrics/benchmarks of the models are absent.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): CV/ML neural networks, training on 100 TB of data and integration into the mobile app are described; the types of detections are listed.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/product-details/technical
  • Why sufficient / why not (one line): there is a technical description at the level of “what was done and on what”, but without model code/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: NAVI (ERC‑20): 0xFc1C93a2507975E98b9d0E9260Ded61A00152BF1
  • Evidence: Tier‑1 — https://etherscan.io/token/0xFc1C93a2507975E98b9d0E9260Ded61A00152BF1 ; https://docs.atlasnavi.com/
  • Why sufficient / why not (one line): the token is verifiable via the explorer; the docs confirm the existence of NAVI as a utility/governance token.
  • Conflict note (if any): NFT contract addresses are not specified in the extracted Tier‑1 materials.

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the onchain component is described via the NAVI token and the NFT economy (purchase/upgrades/marketplace) — but the extracted Tier‑1 contains no contract scheme/addresses for the NFT part.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/fundamentals/token-functions ; https://docs.atlasnavi.com/tokenomics/token-utility
  • Why sufficient / why not (one line): the tokenomics/NFT mechanics are described, but the onchain implementation of the NFT logic is not verified by addresses/contracts.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: without the blockchain there would be no token/NFT mechanics, but the core AI navigation can work as a Web2 app.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/product-details/technical ; https://docs.atlasnavi.com/tokenomics/token-utility
  • Why sufficient / why not (one line): the AI functionality is described as offchain‑mobile; onchain is needed mainly for the economy/incentives.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the NAVI token exists and is claimed as utility/governance.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/ ; https://etherscan.io/token/0xFc1C93a2507975E98b9d0E9260Ded61A00152BF1
  • Why sufficient / why not (one line): the existence of the token is confirmed by the docs and the explorer.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): premium features and subscriptions, as well as a number of B2B functions, can be paid for in NAVI (per the docs).
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/fundamentals/token-functions ; https://docs.atlasnavi.com/tokenomics/token-utility
  • Why sufficient / why not (one line): the docs list specific paid features and NAVI payment scenarios.
  • Conflict note (if any): some scenarios allow fiat payment (the token is partially replaceable).

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

  • TK_2 (decision): 1
  • Claim (one line): incentives are tied to drive‑to‑earn: rewards are counted in $MILE points and can be exchanged for NAVI; “value sinks” — repairs/refuel/maintenance/NFT upgrades.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/fundamentals/token-functions ; https://docs.atlasnavi.com/tokenomics/token-utility
  • Why sufficient / why not (one line): specific mechanics of rewards/spending the token are described.
  • Conflict note (if any): penalties/slashing as an onchain mechanism are not described.

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): token holders can vote (vehicles/features; DAO/voting rights) — claimed in the docs.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/tokenomics/token-utility ; https://docs.atlasnavi.com/fundamentals/token-functions
  • Why sufficient / why not (one line): there is a direct description of the governance utility, but the onchain implementation of voting is not verified by contracts.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): some features allow fiat payment and conversion into NAVI via buyback, so the token is partially replaceable.
  • Evidence: Tier‑1 — https://docs.atlasnavi.com/tokenomics/token-utility ; https://docs.atlasnavi.com/fundamentals/token-functions
  • Why sufficient / why not (one line): the availability of a fiat payment alternative reduces the “hard” necessity of the token in the product.
  • Conflict note (if any): the token remains central to the NFT/game economy by the design of the docs.

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.atlasnavi.com/product-details/technical Tier‑1 description of the AI/CV: types of detections, training on 100 TB of data, embedding into the mobile app.
Tier‑1 https://docs.atlasnavi.com/ General description of the product, public beta note, definition of the NAVI and $MILE tokens.
Tier‑1 https://docs.atlasnavi.com/fundamentals/token-functions Specific token functions: PRO subscriptions, NFT purchases, rewards/exchange $MILE→NAVI, possible buyback/burn, voting, etc.
Tier‑1 https://docs.atlasnavi.com/tokenomics/token-utility NAVI utility in the product (premium/NFT/DAO/B2B data/ads/fleet), details of the economic scenarios.
Tier‑1 https://docs.atlasnavi.com/tokenomics/token-supply Supply/vesting and distribution (cap 300M).
Tier‑1 https://etherscan.io/token/0xFc1C93a2507975E98b9d0E9260Ded61A00152BF1 Onchain confirmation of the ERC‑20 NAVI: contract, cap 300M, code (mint/burn/owner).
Tier‑1 https://www.atlasnavi.com/ Product pages and videos; claims about AI detection and drive‑to‑earn, links to the App Store/Google Play.
Tier‑2 https://www.coingecko.com/en/coins/atlas-navi Reference profile (market/links), does not confirm technical claims.
Tier‑3 https://coinmarketcap.com/currencies/atlas-navi/ Reference aggregator, not a Tier‑1 source on AI/architecture.

No comments to display

Back to top