Skip to main content

Verida

Verida — 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).

Verida — an AI/Data | Infra project: a network for identity/SSO, messaging and private storage of personal data; token (symbol: VDA) and a set of SDKs for integration.

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 protocol/network that adds “missing” services to the Web3 stack: identity/SSO, private data storage, messaging, notifications.
  • Who it’s for: dApp developers who need private user data and convenient onboarding; users of the “data wallet”.
  • Why onchain/token: the VDA token is described as the network’s utility token; the onchain layer is used for interaction with dApps and for verification/accounting of some processes (including “trust” via smart contracts).

How it works (very briefly)

  1. The user does: creates an identity and uses Verida Wallet (data wallet).
  2. The application does: requests access to the user’s private data/messages via the SDK.
  3. The network does: provides services (storage/messaging/SSO) via nodes/providers.
  4. Where the blockchain is: onchain is used for dApp transactions and some verification/accounting (including smart‑contract libraries for verifying offchain data).
  5. Token role: VDA is described as a utility token for the network economy (incentives/growth/distribution).

Quick links: AI thesis fit

Project passport

Field Value
Project name Verida
Also known as (aliases) VDA
Logo (logo) ../assets/506_verida_logo.svg
Token symbol (ticker) VDA
Category AI/Data | Infra
Primary chain (chain) Polygon
Type EVM
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x683565196C3EAb450003C964D4bad1fd3068D4cC
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000 VDA
Issuance fixed
Tokenomics (tokenomics, brief) The whitepaper records the supply and distribution (incentives/network growth/investors/team).
Governance —
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) personal data for AI applications
Use‑case (use_case) self-sovereign data wallet + SSO + messaging
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 2 / token_score 1 / evidence_score 2
Last verified 2026-02-11

General project overview

Verida is positioned as infrastructure that gives dApp developers a set of “Web2‑like” services: private storage of personal data, identity/SSO, messaging and notifications. There is a reference wallet (Verida Wallet), which combines a data wallet and a crypto wallet, and SDKs for integration into web/Node/React Native.

Features/modules

  • Identity + SSO SDK: QR‑based authentication via Verida Wallet.
  • Private storage + messaging: encrypted data and inbox/messages.
  • SDKs + nodes: open‑source SDKs and server nodes that can be run to participate in the network.
  • Trust SDK (mention): smart‑contract libraries for verifying offchain data.

Typical scenarios

  • Scenario 1: the user stores data in Verida Wallet → a dApp requests access → the user agrees/declines.
  • Scenario 2: a developer integrates the SDK → gets identity/SSO and access to data in the application.

Getting started (wallet/network)

  • What you need: Verida Wallet (as the reference app) and/or access to the SDK (see links_* Developer Docs).
  • Network/chain: a multi‑chain approach is described in the whitepaper; the VDA token is present on EVM networks (in this card we record the contract on Polygon).
  • Fees: EVM fees for onchain transactions; the offchain cost of storage depends on the provider.

Architecture/tech (non‑AI)

  • Components: client SDK, SSO SDK, server nodes, wallet app, smart‑contract libraries (per the whitepaper).
  • Participant roles: users, developers, providers/node operators.
  • Where logic runs: private data and services — offchain; onchain — dApp transactions and verification/incentives (per the description of the Trust SDK and token economics).
  • Dependencies: EVM networks for onchain integrations + the offchain infrastructure of providers.

Token/economics (expanded, no forecasts)

  • Token utility: VDA is described as the native utility token of Verida Network.
  • Supply: the whitepaper specifies a supply of 1,000,000,000 and a fixed model.
  • Distribution: the whitepaper lists pools (community incentives, network growth rewards, investors, team, etc.).

Governance

  • Who makes decisions: not established per Tier‑1.

Security and incidents

  • Audits: there is an audit of the Verida protocol (Hashlock) at the link from links_*.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: privacy/key/node risks and risks of access to personal data; the whitepaper emphasizes privacy and consented access.

Project status and timeline

  • Current status: the whitepaper mentions the testnet status of the wallet; the overall network status “mainnet/testnet” is not fixed in 1 line (in the passport we record mainnet for the token).
  • Roadmap: published on the website (see links_* Roadmap).

Ecosystem/integrations

  • Integrations: multi‑chain integrations are claimed in the whitepaper (support for several blockchains).
  • Partners: —.

AI component of the project

  • What is real AI here? the positioning mentions “Private AI” (Verida AI) and hyper‑personalization scenarios; no Tier‑1 technical details of the AI module (architecture/versions/metrics) were found.
  • What is truly onchain? the VDA token on EVM and smart‑contract libraries for verifying offchain data (described in the whitepaper).
  • Why is a token needed? VDA is described as a utility token for the network economy and incentives.
  • Red flags (based on the information found): AI‑washing risk (AI is mentioned as a product/marketing, but the technical details of the AI component are not fixed); the core of the project is data/identity infrastructure, not a proven AI protocol.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): The Tier‑1 source mentions Verida AI / “Talk with your Private AI”.
  • Evidence: Tier‑1 — https://www.verida.network/whitepaper
  • Why sufficient / why not (one line): This is intent/applicability, but without Tier‑1 proof of a specific AI component of the protocol.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): It is not established that the project has a specifically described AI feature/model at the protocol level.
  • Evidence: Tier‑1 — https://www.verida.network/whitepaper
  • Why sufficient / why not (one line): The whitepaper focuses on data/identity services; the AI details are insufficient for 1.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo/app for the AI part was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without an explicit demo link we do not raise the flag.
  • 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): Metrics of the AI component were not found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The architecture of the AI models/versions is not described at the Tier‑1 level.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The whitepaper contains a tech description of the protocol, but not of the AI module.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Polygon
  • Addresses/identifiers: VDA token contract: 0x683565196C3EAb450003C964D4bad1fd3068D4cC
  • Evidence: Tier‑1 — https://polygonscan.com/token/0x683565196C3EAb450003C964D4bad1fd3068D4cC
  • Why sufficient / why not (one line): The explorer confirms the onchain artifact (the token contract).
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: smart‑contract libraries for verifying offchain data (Trust SDK) + interaction of dApps with supported blockchains.
  • Evidence: Tier‑1 — https://www.verida.network/whitepaper
  • Why sufficient / why not (one line): The whitepaper describes onchain interoperability and a trust layer beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that the product breaks down without the blockchain (most services are offchain).
  • Evidence: Tier‑1 — https://www.verida.network/whitepaper
  • Why sufficient / why not (one line): OC_3=1 requires an explicit argument of irreplaceability; not found per Tier‑1.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): VDA is described as the native utility token of Verida Network.
  • Evidence: Tier‑1 — https://www.verida.network/whitepaper
  • Why sufficient / why not (one line): The whitepaper contains a “Verida Token Economics” section.
  • 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): Payment for services with the token as a mandatory protocol mechanism is not established per Tier‑1.
  • Evidence: Tier‑1 — https://www.verida.network/whitepaper
  • Why sufficient / why not (one line): The whitepaper describes the economy and incentives, but an explicit “pay‑per‑service” with the token is not fixed in a single fact.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The token economics describe incentives/rewards for network growth and participants.
  • Evidence: Tier‑1 — https://www.verida.network/whitepaper
  • Why sufficient / why not (one line): The token economics section directly describes the distribution of tokens for incentives/network growth.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): An explicit governance mechanism via the token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): TK_3=1 requires an explicit section on the governance use of the token; not found per Tier‑1.
  • 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.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no explicit comparison “can be replaced with USDC/a subscription”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.verida.network/whitepaper Description of the protocol (identity/SSO/messaging/private storage) and token economics (VDA supply/distribution).
Tier‑1 https://polygonscan.com/token/0x683565196C3EAb450003C964D4bad1fd3068D4cC VDA token contract on Polygon.
Tier‑1 https://hashlock.com/audits/verida-protocol-audit Protocol audit (external report).
Tier‑1 — No Tier‑1 source for the claim about a working AI component (metrics/architecture/versions) was found.
Tier‑2 https://www.coingecko.com/en/coins/verida Token profile/metadata (for reference).
Tier‑2 https://coinmarketcap.com/currencies/verida/ Token profile/metadata (for reference).

No comments to display

Back to top