Skip to main content

VEROX

VEROX (VRX) — 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).

VEROX — a project that describes AI/ML tools and the VeroxAI App application for crypto market analytics in the Tier‑1 documentation (GitBook). The VRX token is an ERC‑20 on Ethereum.

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: an application/set of tools for crypto market analytics (claimed in the Tier‑1 GitBook).
  • Who it’s for: users who need “analysis/a scanner/alerts” (claimed).
  • Why onchain/token: the VRX token contract (ERC‑20) on Ethereum is confirmed; the necessity of the token in the protocol (payment/incentives/governance) is not established per Tier‑1.
  • What you can actually touch (Tier‑1): The VeroxAI App and its description in the GitBook (see links_*).

How it works (very briefly)

  1. The user does: uses the VeroxAI App (claimed).
  2. The system does: provides analysis/scanning/signals/alerts (claimed in the docs).
  3. The user gets: analysis results and the application interface (claimed).
  4. Where the blockchain is: the VRX token on Ethereum is confirmed; the rest of the application logic is offchain (details not established).
  5. Token role (if any): the token exists; a specific necessity of the token (payment/access) is not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name VEROX
Also known as (aliases) VeroxAI; VRX
Logo (logo) ../assets/547_verox_logo.png
Token symbol (ticker) VRX
Category AI/Other
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x87DE305311D5788e8da38D19bb427645b09CB4e5
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI/ML crypto market analytics (app)
Use‑case (use_case) crypto analytics
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 0 / 3
Last verified 2026-02-11

General project overview

In the Tier‑1 documentation, VEROX describes an ecosystem around the VeroxAI App and the VRX token.
Confirmed: Tier‑1 docs (GitBook), the existence of the application (app/demo), and the VRX token contract on Ethereum.

Features/modules

  • VeroxAI App (Tier‑1).
  • Coin analysis/scanner and alerts (claimed).

Typical scenarios

  • Scenario 1: a user analyzes tokens → receives a report/score/alert (claimed).
  • Scenario 2: a user tracks the market → receives signals/notifications (claimed).

Getting started (wallet/network)

  • What you need: open the VeroxAI App / website and follow the documentation.
  • Network/chain: Ethereum (the VRX token — ERC‑20).
  • Fees: Ethereum fees for onchain operations; the subscription/payments/access model is not established per Tier‑1.

Architecture/tech (non‑AI)

  • Components: an offchain application + the VRX token contract (Ethereum).
  • Participant roles: users of the application; token holders (if applicable).
  • Where logic runs: analytics/ML — offchain; onchain is confirmed at the token level.
  • Dependencies: — (not established per Tier‑1).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 (other than the fact of the token’s existence and the presence of docs).
  • Protocol necessity drivers: not established.
  • Who pays fees: Ethereum users for onchain operations (gas).
  • Where fees go: to the Ethereum validators (gas); the project’s protocol fees — not established.
  • Issuance/burn: — (not established).
  • Security/incentive mechanisms: — (not established).
  • Distribution and token issuance schedule: — (not established).
  • Treasury: — (not established).

Governance

  • Who makes decisions: — (not established).
  • How protocol parameters change: — (not established).
  • Where decisions are discussed/made: — (not established).
  • Keys/multisig: — (not established).

Security and incidents

  • Audits: there is a link to an audit in links_*.
  • Bug bounty: —.
  • Incidents: — (not found per Tier‑1).
  • Threat model: the token utility is not confirmed; the risks of the application/models require a separate assessment.

Project status and timeline

  • Current status: active (based on the presence of up‑to‑date documentation/website).
  • Key releases/milestones: — (not established).
  • Roadmap: the link is given in links_*.

Ecosystem/integrations

  • Integrations: — (not established per Tier‑1).
  • Partners: — (not established per Tier‑1).
  • Where it’s actually used: — (not established per Tier‑1).

AI component of the project

  • What is real AI here? The Tier‑1 docs describe AI/ML analysis and the application’s features (AI reality at the level of the product description).
  • What is truly onchain? The VRX token contract (ERC‑20) on Ethereum is confirmed.
  • Why is a token needed? The existence of the token is confirmed; the necessity of the token as a mandatory mechanism of access/payment/incentives is not established per Tier‑1.
  • Red flags (based on the information found): risk of token‑washing (utility not confirmed); the claimed “signals/profit” are not proof — the access model and data sources require re‑checking.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 2
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 partial 3
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 = 2.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI/ML is used for coin/market analysis within the VeroxAI App (per the description).
  • Evidence: Tier‑1 — https://vrx.gitbook.io/vrx/veroxai-app/what-is-the-verox-app
  • Why sufficient / why not (one line): there is a Tier‑1 description of the features of the application’s AI part.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is the VeroxAI App (web/app) and a description stating that it can be used.
  • Evidence: Tier‑1 — https://veroxai.com/, https://vrx.gitbook.io/vrx/veroxai-app/what-is-the-verox-app
  • Why sufficient / why not (one line): this is sufficient Tier‑1 “what you can touch” for AI_2.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1.
  • Context (version/date/how measured): not found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): metrics/context not found → 0.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a tech description/architecture of the models and versions are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): insufficient data for 1 → 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: VRX token (ERC‑20): 0x87DE305311D5788e8da38D19bb427645b09CB4e5
  • Evidence: Tier‑1 — https://etherscan.io/token/0x87DE305311D5788e8da38D19bb427645b09CB4e5
  • Why sufficient / why not (one line): the existence of the onchain artifact is confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established (only the token is confirmed).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no grounds for 1 were found → 0.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established (strictly).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): insufficient justification → 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, VRX (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x87DE305311D5788e8da38D19bb427645b09CB4e5
  • Why sufficient / why not (one line): the existence of the token is confirmed by the contract.
  • 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): Tier‑1 confirmation of payment/access via the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without confirmation of utility → 0.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): incentives/collateral/penalties via the token are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no grounds for 1 were found → 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no grounds for 1 were found → 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): insufficient data → 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://vrx.gitbook.io/vrx Tier‑1: project description, AI/ML positioning
Tier‑1 https://vrx.gitbook.io/vrx/veroxai-app/what-is-the-verox-app Tier‑1: “what you can touch” — the VeroxAI App (description of features)
Tier‑1 https://veroxai.com/ Tier‑1: entry point of the application/website
Tier‑1 https://etherscan.io/token/0x87DE305311D5788e8da38D19bb427645b09CB4e5 onchain: the VRX token contract (ERC‑20, Ethereum)
Tier‑2 https://solidity.finance/audits/Verox/ audit (third‑party report; not Tier‑1)
Tier‑2 https://coinmarketcap.com/currencies/verox/ reference token profile (not proof of utility)
Tier‑3 — —

No comments to display

Back to top