Skip to main content

Victoria VR

Victoria VR (VR) — 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).

Victoria VR — a VR metaverse/gaming ecosystem that claims a “VR AI Builder” and AI Agents for creating and bringing virtual worlds to life, as well as an economy based on the VR token (ERC‑20 on the Ethereum network). In the Tier‑1 sources the VR token is described as “multi‑utility” (payments within the ecosystem, access to tools, staking and a future DAO).

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 VR metaverse/gaming platform with an internal economy based on the VR token.
  • Who it’s for: players and creators of content/experiences, communities, staking participants.
  • Why onchain/token: the VR token is a means of settlement/access and the basis for staking; the existence of the token’s ERC‑20 contract is provable onchain.
  • What you can actually touch (Tier‑1): the public VR AI Builder page with examples/demo materials and the GitBook section on VR AI Builder (including a demonstration video).

How it works (very briefly)

  1. The user does: buys/uses VR, participates in the ecosystem (games/assets/tools), can stake VR.
  2. The system does: accounts for token operations onchain (ERC‑20), while product functions (VR experience, “AI builder/agents”) are implemented at the application/platform level.
  3. The user gets: access to the ecosystem/content and (when staking) periodic rewards/privileges.
  4. Where the blockchain is: Tier‑1 confirms the onchain VR token on Ethereum; regarding the “Victoria VR Blockchain” there are roadmap statements without specific public addresses/specifications.
  5. Token role: VR is used as the ecosystem’s “multi‑utility” token (payments/access/staking/future DAO).

Quick links: AI thesis fit

Project passport

Field Value
Project name Victoria VR
Also known as (aliases) VR | Victoria VR Metaverse
Logo (logo) ../assets/40_victoria-vr_logo.svg
Token symbol (ticker) VR
Category AI/Agents | Gaming | Metaverse
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2021
Project status (status) active
Token (standard) ERC-20
Token contract 0x7d5121505149065b562c789a0145ed750e6e8cdd
Token model (token_type) utility (payments + staking)
Max supply 16,800,000,000 VR (max total supply)
Issuance fixed cap
Tokenomics (tokenomics, brief) distribution: Golden Ticket (4.266B), Rewards Pool (8.4B), Development (4.134B); staking (10–3650 days) and P2E rewards
Governance DAO planned (currently centralized)
Admins/keys owner rights on the token contract (pause/unpause, snapshot)
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) VR AI Builder + AI agents
Use‑case (use_case) VR metaverse games + creation tools
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 2 / 2 / 3
Last verified 2026-02-11

General project overview

According to the Tier‑1 GitBook, Victoria VR describes itself as a VR metaverse where the economy is built around the VR token and a set of utilities: in‑game transactions, access to creation tools, staking and (in the future) governance via a DAO. In parallel, the same source claims AI functions: “VR AI Builder” (no‑code creation of VR experiences) and “AI Agents” (intelligent NPCs/assistants for games/business/education).

It is important to separate the verifiable onchain part (the ERC‑20 token) from the product claims: the AI descriptions in the GitBook are high‑level and contain no technical details of models/versions/metrics.

Features/modules

  • VR metaverse / games (claimed).
  • VR AI Builder: a no‑code tool for creating VR scenes/worlds (claimed).
  • AI Agents: agents/“smart” NPCs for interactivity (claimed).
  • VR token (ERC‑20): payments/access/staking/future DAO (claimed; the existence of the contract is verifiable onchain).
  • Staking program: locking VR for periods of 10–3650 days, monthly accruals/privileges (described).

Typical scenarios

  • Scenario 1 (user/player): uses the VR token for transactions in the ecosystem → gains access to content/assets.
  • Scenario 2 (content creator): uses the “VR AI Builder” to create a VR experience → monetizes it through the platform’s economy (claimed).
  • Scenario 3 (token holder): stakes VR for a period → receives monthly rewards/perks (described).
  • Scenario 4 (demo/examples): a creator goes through the public examples/videos on the VR AI Builder and reproduces the basic no‑code flow of creating a scene/experience (within the available “builder zone”).

Getting started (wallet/network)

  • What you need: an EVM wallet (Ethereum), the VR token (ERC‑20).
  • Network/chain: Ethereum.
  • Fees: Ethereum gas for any onchain operations with VR; additional fees depend on the ecosystem applications used.

Architecture/tech (non‑AI)

  • Components: the VR ERC‑20 token contract; metaverse applications/services (the Tier‑1 technical architecture of the applications is not disclosed).
  • Participant roles: users/players; content creators; stakers.
  • Where logic runs: token accounting onchain on Ethereum; gaming/VR/AI functionality — at the application/platform level.
  • Dependencies: Ethereum as the token’s base network; the metaverse client applications.

Token/economics (expanded, no forecasts)

  • Token utility: in‑game transactions; “access to tools such as the VR AI Builder”; creation of AI agents; staking; future governance via a DAO (as claimed in the GitBook).
  • Protocol necessity drivers: the token is described as the “foundation for economy” and “multi‑utility” (Tier‑1); however, the verifiability of specific payment flows in the application is limited.
  • Who pays fees: participants performing onchain operations (Ethereum gas); ecosystem users when using the token.
  • Where fees go: — (not established per Tier‑1 within this card).
  • Issuance/burn: Etherscan lists a max total supply of 16.8B VR; burn mechanics are not identified as mandatory in the Tier‑1 GitBook text.
  • Security/incentive mechanisms: a staking program with lock‑up and rewards/perks; for the token — the presence of owner functions pause/unpause/snapshot.
  • Distribution and token issuance schedule: the official tokenomics article (2021‑11‑18) describes 3 distribution categories: Golden Ticket 4.266B (25.39%), Rewards Pool 8.4B (gradual unlock tied to activity/staking), Development 4.134B (including team tokens released 1 year after the TGE, monthly over 3 years) + a strategic reserve (1.68B is mentioned).
  • Treasury: —.

Governance

  • Who makes decisions: a DAO is declared as a future stage; until its launch governance is described as centralized.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: owner rights on the token contract (pause/unpause/snapshot).

Security and incidents

  • Audits: per the token page on Etherscan, a smart contract audit report has been published (Hacken, 2021).
  • Bug bounty: — (no Tier‑1 confirmation found).
  • Incidents: — (not established).
  • Threat model: centralization of the token’s admin rights (pause/unpause/snapshot); correspondence of the claimed in‑app utilities to the actual implementation; risks of centralized metaverse components.

Project status and timeline

  • Current status: the VR token exists on Ethereum; product milestones are published in the GitBook roadmap.
  • Key releases/milestones: the 2025 roadmap highlights include the VR AI Builder, AI Agents, DAO launch and the “Victoria VR Blockchain” as declared directions.
  • Roadmap: see the GitBook roadmap.

Ecosystem/integrations

  • Integrations: Ethereum (ERC‑20); community (Discord/Telegram); staking infrastructure (the GitBook mentions third‑party statistics pages).
  • Partners: — (not established per Tier‑1 within this card).
  • Where it’s actually used: Tier‑1 claims gaming and creator scenarios and staking (implementation details depend on the ecosystem applications).

AI component of the project

  • What is real AI here? Tier‑1 describes the “VR AI Builder” and “AI Agents” as metaverse features (creating experiences without code, adaptive NPCs/assistants), but without disclosing specific models/metrics.
  • What is truly onchain? Verifiable: the VR ERC‑20 token on Ethereum; Tier‑1 also claims that VR Lands are registered on the blockchain as NFTs. A separate “Victoria VR Blockchain” is not confirmed by Tier‑1 artifacts (there is only a roadmap mention).
  • Why is a token needed? Declared as the foundation of the economy: payments/access/staking/future DAO.
  • Red flags (based on the information found): AI‑washing (descriptions without technical details and metrics), onchain‑washing (mention of the “Victoria VR Blockchain” without public specifications/addresses), token‑washing (some utilities may be offchain and replaceable; the actual payment flows need to be verified).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): the AI functions are described as product elements (AI builder/agents), so this is not just “intent”.
  • Evidence: Tier‑1 — https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/artificial-intelligence
  • Why sufficient / why not (one line): AI is claimed as functionality, but without verification of “what exactly is under the hood”.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI Agents (adaptive NPCs/assistants) and the VR AI Builder as a tool for creating VR experiences “without code” are described.
  • Evidence: Tier‑1 — https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/artificial-intelligence/vr-ai-builder, https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/artificial-intelligence/vr-ai-agents
  • Why sufficient / why not (one line): there is a description of behavior/roles, but no model/versions/inference parameters.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the official website and the docs provide video examples of projects created/shown via the VR AI Builder (showroom/gallery).
  • Evidence: Tier‑1 — https://victoriavr.com/builder, https://victoriavr.gitbook.io/victoria-vr-the-ai-powered-platform/vr-ai-builder
  • Why sufficient / why not (one line): Tier‑1 contains specific demonstration materials/links to videos.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — — | No Tier‑1 source on AI metrics was found.
  • Why sufficient / why not (one line): no numbers/context.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the technical architecture of the AI component (models/versions/inference) is not disclosed in the card’s Tier‑1 sources.
  • Evidence: Tier‑1 — — | No Tier‑1 source on a technical description of the AI component was found.
  • Why sufficient / why not (one line): there is a marketing description, but no engineering details.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0x7d5121505149065b562c789a0145ed750e6e8cdd
  • Evidence: Tier‑1 — https://etherscan.io/token/0x7d5121505149065b562c789a0145ed750e6e8cdd
  • Why sufficient / why not (one line): the token contract and supply are verifiable.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: VR Lands are claimed as NFTs that are bought/minted onchain (sale/mint/trade) — this is an onchain component of the ecosystem beyond the ERC‑20 token.
  • Evidence: Tier‑1 — https://victoria-vr.gitbook.io/home/getting-started/what-is-a-vr-land
  • Why sufficient / why not (one line): Tier‑1 explicitly states the registration of VR Lands “on the blockchain as NFTs”; at the same time, specific NFT contract addresses are not listed in the extracted Tier‑1.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not proven by Tier‑1 that the product cannot operate without a blockchain (other than the existence of the token).
  • Evidence: Tier‑1 — https://victoriavr.gitbook.io/victoria-vr-token-utility/roadmap
  • Why sufficient / why not (one line): there are roadmap mentions of a blockchain/DAO, but without criteria for “breaks down without onchain”.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, VR (ERC‑20).
  • Evidence: Tier‑1 — https://victoriavr.gitbook.io/victoria-vr-token-utility/introduction/what-are-usdvr-tokens
  • Why sufficient / why not (one line): the contract and the role of the token are described.
  • Conflict note (if any): —

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): VR is described as a token for in‑app transactions and access to tools (including the VR AI Builder).
  • Evidence: Tier‑1 — https://victoriavr.gitbook.io/victoria-vr-token-utility/introduction/what-are-usdvr-tokens
  • Why sufficient / why not (one line): “multi‑utility” and usage examples are listed.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): a VR staking program with lock‑up and rewards/perks is described.
  • Evidence: Tier‑1 — https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/additional-usdvr-utilities/virtual-revolution-staking
  • Why sufficient / why not (one line): the staking terms and benefits are described explicitly.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): a DAO is declared as a future feature; onchain governance mechanics/contracts are not confirmed by the card’s Tier‑1 sources.
  • Evidence: Tier‑1 — https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/additional-usdvr-utilities/dao
  • Why sufficient / why not (one line): the existence of “governance now” is not proven; we count 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): in Tier‑1 the token is positioned as central to the economy and staking; replacement is not confirmed.
  • Evidence: Tier‑1 — https://victoriavr.gitbook.io/victoria-vr-token-utility/introduction/what-are-usdvr-tokens, https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/additional-usdvr-utilities/virtual-revolution-staking
  • Why sufficient / why not (one line): the token is tied to the staking program and to the claimed access/economy.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://victoriavr.gitbook.io/victoria-vr-token-utility/introduction/what-is-victoria-vr product positioning (VR metaverse + AI + blockchain)
Tier‑1 https://victoriavr.gitbook.io/victoria-vr-token-utility/introduction/what-are-usdvr-tokens ticker, token address, “multi‑utility” and areas of use (including AI builder/agents, staking, governance)
Tier‑1 https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/artificial-intelligence/vr-ai-builder description of the VR AI Builder and its role/promises
Tier‑1 https://victoriavr.gitbook.io/victoria-vr-the-ai-powered-platform/vr-ai-builder demonstration video of the VR AI Builder (Early Access / Builder Zone)
Tier‑1 https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/artificial-intelligence/vr-ai-agents description of the AI Agents and scenarios
Tier‑1 https://victoriavr.gitbook.io/victoria-vr-token-utility/usdvr-token-ecosystem/additional-usdvr-utilities/virtual-revolution-staking staking terms and the claimed rewards/perks
Tier‑1 https://victoriavr.gitbook.io/victoria-vr-token-utility/roadmap 2025 roadmap: VR AI Builder, AI Agents, DAO launch, “Victoria VR Blockchain” (as directions)
Tier‑1 https://victoriavr.com/builder VR AI Builder showcase + examples/videos of “past projects” (showroom/gallery)
Tier‑1 https://etherscan.io/token/0x7d5121505149065b562c789a0145ed750e6e8cdd onchain fact of the VR token (max supply 16.8B; verified contract; owner/pause/unpause/snapshot; link to the audit)
Tier‑1 https://victoria-vr.gitbook.io/home/getting-started/what-is-a-vr-land Tier‑1: VR Lands are registered “on the blockchain as NFTs” (mint/sale/trade).
Tier‑1 https://www.victoriavr.com/whitepaper/ existence of the whitepaper page and the declared sections (tokenomics/roadmap)

No comments to display

Back to top