VirtuSwap
VirtuSwap — 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).
VirtuSwap — a DeFi project on the Ethereum network, token (symbol: —).
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 DeFi protocol/application for token swaps and working with liquidity.
- Who it’s for: DeFi users, liquidity providers, integrators.
- Why onchain/token: onchain ensures trade execution/tracking of pool state; the utility of the project token is not established per Tier‑1 sources.
How it works (very briefly)
- The user does: connects a wallet and initiates a token swap or liquidity provision.
- The system does: executes operations through the protocol’s smart contracts.
- The user gets: a swap or a liquidity position (depending on the scenario).
- Where the blockchain is: trade execution/tracking of contract state takes place onchain.
- Token role (if any): the token contract exists; the specific function of the token in the protocol is not established per Tier‑1 sources.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | VirtuSwap |
| Also known as (aliases) | — |
| Logo (logo) | ../assets/791_virtuswap_logo.svg |
| Token symbol (ticker) | VRSW |
| Category | DeFi |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x99a01a4d6a4d621094983050d9a2f10b2912e53d |
| Token model (token_type) | — |
| Max supply | 1 000 000 000 VRSW |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | yes |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | on-chain token swaps + liquidity |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | ai_score 0 / onchain_score 2 / token_score 0 / evidence_score 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://virtuswap.io |
| Docs | https://docs.virtuswap.io/ |
| GitHub | https://github.com/Virtuswap/v1-core |
| Releases / Changelog | https://github.com/Virtuswap/v1-core/commits |
| Whitepaper | https://virtuswap.io/docs/whitepaper.pdf |
| Roadmap | https://virtuswap.io/roadmap.html |
| Security advisories | https://github.com/Virtuswap/v1-core/security |
| Explorer | https://etherscan.io/token/0x99a01a4d6a4d621094983050d9a2f10b2912e53d |
| X | https://twitter.com/VirtuSwap |
| Discord | https://discord.com/invite/virtuswap |
| Telegram | https://t.me/official_virtuswap |
| Medium | https://medium.com/virtuswap |
| Audit report(s) | https://github.com/Virtuswap/v1-core/tree/main/audits |
| Bug bounty | https://hackenproof.com/virtuswap |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/virtuswap/ |
General project overview
VirtuSwap is a DeFi project positioned per Tier‑1 materials as an AMM based on “virtual pools” (see the whitepaper) and an application/protocol for token swaps. Tier‑1 artifacts: official website/documentation, whitepaper, repository and onchain token address. No Tier‑1 confirmation of an AI component was found.
Features/modules
- Protocol smart contracts (v1-core repository).
- Project documentation/materials (Docs/Whitepaper).
- Interface for operations (Website).
Typical scenarios
- Scenario 1: a user swaps tokens → receives the swap result (onchain execution).
- Scenario 2: a user adds/removes liquidity → obtains/closes a liquidity position (if supported by the protocol).
Getting started (wallet/network)
- What you need: an EVM wallet.
- Network/chain: Ethereum.
- Fees: Ethereum network fees (gas) for onchain operations.
Architecture/tech (non‑AI)
- Components: protocol smart contracts, user interface, network access infrastructure (RPC providers).
- Participant roles: users, liquidity providers.
- Where logic runs: onchain execution of operations through smart contracts (Ethereum).
- Dependencies: not established per Tier‑1 sources (for example, the presence of oracles/indexers requires separate verification).
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 sources.
- Protocol necessity drivers: not established per Tier‑1 sources.
- Who pays fees: users pay Ethereum network fees when executing onchain operations.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Keys/multisig: —.
Security and incidents
- Audits: links to audit materials are claimed (see
Audit report(s)). - Bug bounty: a public program (see
Bug bounty). - Incidents: not established per Tier‑1 sources.
Project status and timeline
- Current status: —.
- Key releases/milestones: —.
- Roadmap: published on the official website (see links_*). The roadmap page claims that exchange operations are “winding down”.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? No Tier‑1 confirmation of an AI component (intent or a working feature) was found.
- What is truly onchain? Onchain artifacts are recorded via the explorer; protocol logic is expected to be implemented in smart contracts (see the official repository).
- Why is a token needed? The token contract exists, but a Tier‑1 justification of the token utility in the protocol is not established.
- Red flags (based on the information found): AI label without Tier‑1 artifacts; unestablished token utility; absence of a public roadmap.
DecAI Fit component summary
- DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
| Component | Level | Score |
|---|---|---|
| AI reality | low | 0 |
| Onchain necessity | medium | 2 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 present | 1 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): A Tier‑1 declaration of AI intent is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no confirmed AI intent/roadmap per Tier‑1; the project is described as a DeFi protocol.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): Whether the product contains an AI component and what exactly it does are not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of “what the AI does” was found.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): Demos/examples of the AI component in operation are not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no confirmed AI component, so an AI demo is not applicable.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —.
- Context (version/date/how measured): —.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): AI quality metrics are not applicable: an AI component is not established.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): A tech description of an AI component is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no confirmed AI component.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum.
- Addresses/identifiers: token contract 0x99a01a4d6a4d621094983050d9a2f10b2912e53d.
- Evidence: Tier‑1 — https://etherscan.io/token/0x99a01a4d6a4d621094983050d9a2f10b2912e53d
- Why sufficient / why not (one line): There is an onchain artifact (the token address) in a public explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: protocol operations are implemented by smart contracts (v1-core repository).
- Evidence: Tier‑1 — https://github.com/Virtuswap/v1-core
- Why sufficient / why not (one line): There is a Tier‑1 “core” code artifact for protocol logic, not just a token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 formulation that passes the “replace the blockchain” test.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The token contract exists on the Ethereum network.
- Evidence: Tier‑1 — https://etherscan.io/token/0x99a01a4d6a4d621094983050d9a2f10b2912e53d
- Why sufficient / why not (one line): The existence of the token is confirmed by an onchain address in the explorer.
- 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): It is not established that the token is used as payment for the service.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of the token’s role as payment was found.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): It is not established that the token is used in mechanisms of incentives/collateral/penalties.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of token incentives was found.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): It is not established that the token is used in governance.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of token governance was found.
- 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 per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 justification of the replaceability/irreplaceability of the token.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://virtuswap.io | Official project website (navigation to Tier‑1 materials). |
| Tier‑1 | https://docs.virtuswap.io/ | Project documentation (product description per Tier‑1). |
| Tier‑1 | https://github.com/Virtuswap/v1-core | Tier‑1 development artifact: official “v1-core” repository. |
| Tier‑1 | https://etherscan.io/token/0x99a01a4d6a4d621094983050d9a2f10b2912e53d | Onchain: token contract on the Ethereum network (address confirmed in the explorer). |
| Tier‑1 | https://virtuswap.io/docs/whitepaper.pdf | Whitepaper (Tier‑1): description of the AMM based on “virtual pools” and the protocol’s goals. |
| Tier‑1 | https://virtuswap.io/roadmap.html | Roadmap (Tier‑1): plans/milestones and the note “winding down exchange operations”. |
| Tier‑1 | — | No Tier‑1 source for claim “the project has an AI component” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “the token is needed for specific utility in the protocol” was found. |
No comments to display
No comments to display