Veritas Protocol
Veritas Protocol — 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).
Veritas Protocol — an AI/Other project on the Base network, token (symbol: VPT).
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 AI‑powered platform/protocol for smart contract security: automated audits, scam detection, forensics and related tools (see Tier‑1).
- Who it’s for: users and investors who check tokens/contracts; projects/teams that need auditing/monitoring/insurance.
- Why onchain/token: the $VPT token is claimed to provide token‑gated access to products + voting on platform decisions and a deposit mechanism for the insurance pool (see Tier‑1).
- What you can actually touch (Tier‑1): Veritas Explorer (B2C) and Veritas Audit (B2B) (public entry points).
How it works (very briefly)
- The user does: submits a token/contract address for checking or launches an audit.
- The system does: performs automated checks/auditing, generates a report and risk signals.
- The user gets: a report/assessment, identified red flags and recommendations for fixes (including via AI Debugger, claimed).
- Where the blockchain is: the analyzed contracts and onchain metrics are checked across networks; the $VPT token exists on the Base network (onchain fact).
- Token role (if any): access to products (token‑gated), governance and participation in the insurance pool (per Tier‑1).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Veritas Protocol |
| Also known as (aliases) | — |
| Logo (logo) | ../assets/888_veritas-protocol_logo.svg |
| Token symbol (ticker) | VPT |
| Category | AI/Other |
| Primary chain (chain) | Base |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Base; Ethereum L2) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x00096697dc24bd10423690126d91546a20ccb3f0 |
| Token model (token_type) | utility (access + governance + insurance) |
| Max supply | 1 000 000 000 |
| Issuance | — |
| Tokenomics (tokenomics, brief) | token‑gated access; $VPT deposits into the insurance pool; revenue share claimed (see Tier‑1). |
| Governance | token governance (vote on risk/claims/updates) |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI audit + smart contract scam detection |
| Use‑case (use_case) | token/contract checks/audits |
| DecAI Fit — AI thesis fit | 5/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 3 / 1 / 3 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://veritasprotocol.com/ |
| Docs | https://docs.veritasprotocol.com/ |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://docs.veritasprotocol.com/veritas-protocol/white-paper |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://basescan.org/token/0x00096697dc24bd10423690126d91546a20ccb3f0 |
| App / Demo | https://explorer.veritasprotocol.com/ |
| X | https://twitter.com/veritas_web3 |
| Discord | — |
| Telegram | https://t.me/veritasprotocolverify |
| Medium | — |
| Audit report(s) | https://docs.veritasprotocol.com/ecosystem/asset-audit |
| Bug bounty | — |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/veritas-protocol/ |
General project overview
Per Tier‑1 sources, Veritas describes an AI‑powered platform for Web3 security, including automated audits, scam detection, forensics and related tools. The documentation also describes an “asset audit” flow for users/investors and the basic theses of the White Paper. The $VPT token is claimed to be a utility token providing access to products, governance and participation in the insurance pool.
Features/modules
- Automated audits: automation of smart contract auditing/checks.
- Scam detection / forensics: tools for detecting scam patterns and conducting investigations.
- Asset audit: a user flow for analyzing token contracts and red flags.
- AI Debugger: claimed to be autonomous AI agents for analysis and proposing/deploying fixes.
Typical scenarios
- Scenario 1: a user checks a token/contract → receives a report/red flags.
- Scenario 2: a project launches automated auditing/monitoring for its contracts.
Getting started (wallet/network)
- What you need: an EVM wallet that supports Base.
- Network/chain: Base.
- Fees: Base network fees for transfers/operations.
Architecture/tech (non‑AI)
- Components: the token contract on the Base network.
- Participant roles: token holders and participants of the Base network.
- Where logic runs: accounting/transfers of the token — onchain on Base.
- Dependencies: Base RPC/wallets/infrastructure.
Token/economics (expanded, no forecasts)
- Token utility: token‑gated access to products; governance; deposits into the insurance pool; revenue share claimed.
- Protocol necessity drivers: utility is described in Tier‑1 tokenomics; protocol-level onchain necessity other than the token is not established.
- Who pays fees: users of the Base network.
- Where fees go: to the sequencer/validators/L1 participants per Base/Ethereum rules (depends on the fee component).
- Issuance/burn: —.
- Security/incentive mechanisms: —.
- Distribution and token issuance schedule: —.
- Treasury: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Keys/multisig: —.
Security and incidents
- Audits: there is an asset audit page (see
links_*). - Bug bounty: —.
- Incidents: —.
- Threat model: risks are typical for tokens and wallet/RPC infrastructure; without a Tier‑1 description of the product, the threat model is not established.
Project status and timeline
- Current status: mainnet (based on the fact of the token’s existence on the network).
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? Tier‑1 describes AI‑driven security: automated audits + a multi‑agent framework (agentic pipeline) for analysis and (claimed) proposing/deploying fixes.
- What is truly onchain? the token contract on the Base network (contract and transactions — onchain).
- Why is a token needed? Tier‑1 describes the utility of $VPT: access to products, governance, an insurance pool and claimed revenue share.
- Red flags (based on the information found): a lack of Tier‑1 metrics for detector quality/accuracy (AI_3=0); the risk of “badge‑washing” if reports are not transparent about the methodology.
DecAI Fit component summary
- DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 3 |
| Onchain necessity | low (token only) | 1 |
| Token necessity | high | 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 working functionality (AI‑powered audits/scam detection), not only as “intent/roadmap”.
- Evidence: Tier‑1 — https://docs.veritasprotocol.com/ ; https://docs.veritasprotocol.com/veritas-protocol/white-paper
- Why sufficient / why not (one line): when a Tier‑1 description of working AI features is present, AI_0 adds no signal.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Tier‑1 describes AI‑driven automated audits, scam detection and forensics of smart contracts.
- Evidence: Tier‑1 — https://docs.veritasprotocol.com/ ; https://docs.veritasprotocol.com/veritas-protocol/white-paper
- Why sufficient / why not (one line): there is a Tier‑1 description of the tasks the AI system solves.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): Tier‑1 includes the “asset audit” user flow (checking tokens/contracts) and the public entry point Veritas Explorer.
- Evidence: Tier‑1 — https://docs.veritasprotocol.com/ecosystem/asset-audit ; https://explorer.veritasprotocol.com/
- Why sufficient / why not (one line): the presence of a described user flow and an available entry point is sufficient as a demo surface.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not found.
- Context (version/date/how measured): not found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no Tier‑1 metrics/context → 0.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): Tier‑1 describes an agentic framework (a multi-agent pipeline) for analysis/auditing and verification.
- Evidence: Tier‑1 — https://docs.veritasprotocol.com/veritas-protocol/white-paper
- Why sufficient / why not (one line): the White Paper contains an architectural description of the agentic pipeline and the analysis/inference stages.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Base
- Addresses/identifiers: 0x00096697dc24bd10423690126d91546a20ccb3f0
- Evidence: Tier‑1 — https://basescan.org/token/0x00096697dc24bd10423690126d91546a20ccb3f0
- Why sufficient / why not (one line): the onchain fact of the token contract 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 per Tier‑1 (other than the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there are no Tier‑1 addresses/description of onchain logic other than the token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established (no Tier‑1 description of the product).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a Tier‑1 justification of criticality, we set 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the token exists (ERC‑20 on Base).
- Evidence: Tier‑1 — https://basescan.org/token/0x00096697dc24bd10423690126d91546a20ccb3f0
- Why sufficient / why not (one line): the token is identified by the contract address.
- 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): Tier‑1 describes that holders get access to products (token‑gated membership).
- Evidence: Tier‑1 — https://docs.veritasprotocol.com/veritas-protocol/tokenomics
- Why sufficient / why not (one line): token‑gated access is “access” utility that requires the token.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): Tier‑1 describes $VPT deposits into the insurance pool to obtain insurance coverage and rewards.
- Evidence: Tier‑1 — https://docs.veritasprotocol.com/veritas-protocol/tokenomics
- Why sufficient / why not (one line): an insurance pool with deposits/rewards is an incentive/collateral mechanism.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): Tier‑1 describes that holders vote on platform decisions (risk/claims/updates).
- Evidence: Tier‑1 — https://docs.veritasprotocol.com/veritas-protocol/tokenomics
- Why sufficient / why not (one line): a direct Tier‑1 description of the governance feature is sufficient for TK_3=1.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): not established (no Tier‑1 allowing replaceability to be assessed).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): with insufficient data, we set 0 (conservatively).
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://basescan.org/token/0x00096697dc24bd10423690126d91546a20ccb3f0 | Address of the ERC‑20 token contract on the Base network (onchain fact). |
| Tier‑1 | https://docs.veritasprotocol.com/ecosystem/asset-audit | The presence of an asset audit/asset checking page in the official documentation. |
| Tier‑1 | https://docs.veritasprotocol.com/ | Tier‑1 description of the product as an AI‑powered platform for audits/scam detection/forensics. |
| Tier‑1 | https://docs.veritasprotocol.com/veritas-protocol/white-paper | White Paper: description of automated audits/AI Debugger and the agentic framework. |
| Tier‑1 | https://docs.veritasprotocol.com/veritas-protocol/tokenomics | Utility of the $VPT token: access (token‑gated), governance, insurance pool, revenue share (claimed). |
| Tier‑2 | https://coinmarketcap.com/currencies/veritas-protocol/ | Reference token profile (metadata, links). |
No comments to display
No comments to display