Skip to main content

Velvet Capital

Velvet Capital — 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).

Velvet Capital — an AI/Agents | DeFi project: a DeFi platform for onchain portfolios/“vaults” and trading from the wallet, with the Velvet Unicorn AI assistant (multi‑agent AI for research/trades/auto‑portfolios). Token: VELVET (BEP‑20 on BNB Smart Chain).

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 app and a set of smart contracts for creating tokenized portfolios (vaults) and executing trades/DeFi actions from the wallet.
  • Who it’s for: users (trading/DeFi), portfolio managers (public vault strategies), integrators (contract API).
  • Why onchain/token: onchain is needed for issuing portfolio shares (index tokens) and executing deposits/withdrawals/trades; the VELVET token is used for staking/governance and discounts/referral incentives (while the “AI gas token” in the ecosystem is described separately as VU).
  • What you can actually touch (Tier‑1): https://dapp.velvet.capital and the “How to Use Velvet Unicorn” guide https://docs.velvet.capital/product/ai-framework.

How it works (very briefly)

  1. The user does: connects a wallet and either trades (swap/DeFi pools) or creates/enters a portfolio (vault).
  2. The system does: (per Tier‑1) when a portfolio is created, deploys/configures a vault and issues portfolio shares (index tokens); for deposits/withdrawals it uses the multi‑token deposit/withdraw functions.
  3. The user gets: an onchain share of the portfolio and the ability to manage assets/positions; in the trading terminal — execution of trades directly from the wallet.
  4. Where the blockchain is: the logic of deposits/withdrawals/issuance of portfolio shares and the accounting of positions are implemented via smart contracts; the VELVET token and transactions are confirmed by the BNB Smart Chain explorer.
  5. Token role: VELVET takes part in veVELVET staking (governance/discounts/referral rewards and revenue distribution); AI calls in the ecosystem are claimed to be paid for with the VU token (but this is not the same token as VELVET).

Quick links: AI thesis fit

Project passport

Field Value
Project name Velvet Capital
Also known as (aliases) Velvet; VELVET
Logo (logo) ../assets/79_velvet_logo.svg
Token symbol (ticker) VELVET
Category AI/Agents | DeFi
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) 2025-07-09
Project status (status) active
Token (standard) BEP-20
Token contract 0x8b194370825E37b33373e74A41009161808C1488
Token model (token_type) utility (staking + governance)
Max supply 1 000 000 000 (cap)
Issuance capped; mintable by owner (until cap)
Tokenomics (tokenomics, brief) veVELVET lock 1–200 weeks; revenue split 50% to veVELVET stakers / 50% treasury
Governance DAO
Admins/keys —
Audit yes
Bug bounty yes
Team (team) Velvet Capital
Funding (investors/funding) investors are mentioned in the tokenomics (including Binance Labs and others)
AI component (ai_component) multi-agent DeFi copilot (Velvet Unicorn)
Use‑case (use_case) AI-assisted trading + tokenized DeFi portfolios (vaults)
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 3 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

Velvet describes itself as a “DeFi operating system” for non‑custodial trading and portfolio management. The product consists of:

  • Trading Terminal: a trading terminal that allows trading tokens and entering DeFi pools directly from the wallet (without depositing to the platform).
  • Portfolio Management: a builder of public/private portfolios (vaults), where portfolio shares (index tokens) are created and trading/management of positions inside the vault is available.
  • AI Framework (Velvet Unicorn): a chat assistant that is claimed to be a multi‑agent system (LLM agents + small task‑specific models) for market research, intent execution and (prospectively) autonomous portfolio management.

Features/modules

  • Trading terminal: trends/new pairs/gainers/volumes + quick trades (“Quick Buy”) and working with DeFi pools.
  • Vaults/portfolios: public and private portfolios, issuance of shares (index tokens), deposits/withdrawals and management of assets/positions.
  • Contract API: methods for obtaining the portfolio composition, multi‑token deposit/withdraw, emergency withdrawal, etc.
  • Velvet Unicorn AI: natural language questions → structured insights → intent execution of trades/actions.

Typical scenarios

  • Scenario 1 (user): opens the Trading Terminal → finds a trending token → performs a swap from the wallet or enters a DeFi pool.
  • Scenario 2 (portfolio manager): creates a public vault → sets the parameters (fees/whitelist/assets) → deploys and runs the strategy; users can enter/exit.
  • Scenario 3 (AI assistant): opens Velvet Unicorn → asks a question/intent (“Trade 1 ETH into $VU”) → receives insights and can initiate actions.

Getting started (wallet/network)

  • What you need: an EVM wallet (for BNB Smart Chain and other supported networks).
  • Network/chain: the app supports several networks (including BNB Chain, Ethereum, Base, etc.); the VELVET token is confirmed on BNB Smart Chain.
  • Fees: network fees of the selected network + a platform execution fee (the docs specify a 0.5% execution fee).

Architecture/tech (non‑AI)

  • Components: web app (dapp), vault smart contracts (portfolio tokens), execution engine (collection of the execution fee), and the contract API (deposit/withdraw/emergency withdrawal).
  • Participant roles: traders/users (make trades), portfolio managers (create/manage vaults), token holders (stake veVELVET), developer‑integrators (call the contract methods).
  • Where logic runs: onchain — issuance of portfolio shares and accounting of deposits/withdrawals/transactions; offchain — UI/routing/analytics and some of the data sources.
  • Dependencies: RPC/infrastructure of the supported networks; DeFi protocol integrations (yield), as well as monitoring tools (Forta/Defender/Tenderly — claimed in the security section).

Token/economics (expanded, no forecasts)

  • veVELVET (Tier‑1): staking VELVET → veVELVET with a lock of 1–200 weeks and linear decay; veVELVET gives voting rights and affects discounts/referral rewards.
  • Fee sharing / real yield (Tier‑1): protocol revenue is split 50% → swapped into VELVET and paid out to veVELVET stakers, 50% → DAO treasury.
  • Platform fees (Tier‑1): the execution engine takes a 0.5% transaction fee; the docs say the fee can be reduced by staking VELVET.
  • Separate token for AI (Tier‑1): the tokenomics describes the “Velvet Unicorn token (VU)” as the payment token for AI inference (⅓ burn / ⅓ treasury / ⅓ via VELVET rewards to veVELVET stakers).

Governance

  • Who makes decisions: Velvet DAO (the tokenomics specifies voting rights for veVELVET).
  • How protocol parameters change: via DAO decisions (integrations/fee distribution, future emission allocation).
  • Where: — (a specific forum/snapshot is not recorded per Tier‑1).
  • Keys/multisig: —.

Security and incidents

  • Audits: 7 audits are claimed (Peckshield, Softstack, Resonance Security, Shellboxes, etc.) + an open competition (Hats Finance); the final reports are published in the audits GitHub repository.
  • Bug bounty: an active program on Immunefi + Hats Finance (in the docs).
  • Incidents: no public postmortems/confirmed incidents were found per Tier‑1 → —.
  • Threat model: risks of the vault smart contracts and the execution engine (including integrations with DEXes/DeFi), risks of permissions/upgrades (if any), risks of the offchain part (data sources/routing), and risks of the AI layer (quality of insights/errors in intent execution).

Project status and timeline

  • Current status: the product is available; the VELVET token is deployed on BNB Smart Chain; part of the AI roadmap is described in phases (research → intent execution → autonomous portfolio management).
  • Key milestones: deployment of the VELVET contract (2025‑07‑09); launch of Velvet Unicorn Phase 1 (per the AI Framework — “completed”).
  • Roadmap: published in the docs (links_*).

Ecosystem/integrations

  • Integrations: DeFi pool/yield integrations (the docs claim “30+ yield integrations”); security tools Forta + OpenZeppelin Defender + Tenderly (in the docs).
  • Partners: — (no separate verification of partners was performed).
  • Where it’s actually used: the dapp (trading/vaults) + the Velvet Unicorn AI button (per the guide).

AI component of the project

  • What is real AI here? Velvet Unicorn is described as a multi‑agent AI OS for DeFi: natural language chat, routing to sub‑agents, insights (including a prediction model) and intent execution of trades/actions.
  • What is truly onchain? Vaults/portfolio tokens (index tokens) and deposit/withdraw/trade operations are executed as transactions from the wallet; the VELVET token is confirmed on BNB Smart Chain.
  • Why is a token needed? VELVET is used for veVELVET (governance + discounts/referral rewards + fee sharing); AI calls are described as paid for with a separate token, VU.
  • Red flags (based on the information found): claims about a “self‑improving multi‑agent OS” without public quality metrics; intent execution requires caution (model errors → wrong trades).

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity high 3
Token necessity low 1
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 layer (Velvet Unicorn) is described as an already working product component, not only an intent.
  • Evidence: Tier‑1 — https://docs.velvet.capital/product/ai-framework
  • Why sufficient / why not (one line): the docs have a “How to Use” in the dapp and a description of the functions.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Velvet Unicorn is a multi‑agent AI: it answers questions, provides structured insights and can perform intent actions (trades/portfolio actions).
  • Evidence: Tier‑1 — https://docs.velvet.capital/product/ai-framework
  • Why sufficient / why not (one line): the page describes the agent roles, routing and the range of actions (research → execution).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a reproducible path to open Velvet Unicorn AI in the dapp and use the chat interface; the docs have a step‑by‑step guide.
  • Evidence: Tier‑1 — https://dapp.velvet.capital ; https://docs.velvet.capital/product/ai-framework
  • Why sufficient / why not (one line): the docs specify the steps (connect wallet → “Velvet Unicorn AI” button).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — — (no published quality/accuracy metrics/benchmarks were found per Tier‑1)
  • Why sufficient / why not (one line): without numbers and a methodology, the component is not counted.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): the multi‑agent architecture (agent roles, routing, LLM + task‑specific models, reward/feedback loop) and the development phases are described.
  • Evidence: Tier‑1 — https://docs.velvet.capital/product/ai-framework
  • Why sufficient / why not (one line): the page contains an architectural description and “Roadmap phases”.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain (VELVET token); the product supports several networks (per the docs).
  • Addresses/identifiers: VELVET token 0x8b194370825E37b33373e74A41009161808C1488 (BSC).
  • Evidence: Tier‑1 — https://bscscan.com/address/0x8b194370825E37b33373e74A41009161808C1488 ; https://docs.velvet.capital/product/trading-terminal
  • Why sufficient / why not (one line): the token address is confirmed by the explorer; the docs record the terminal’s multi‑network support.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: vault contracts with multi‑token deposit/withdraw methods and issuance of portfolio shares (index tokens); portfolio fees are accrued in the form of vault tokens.
  • Evidence: Tier‑1 — https://docs.velvet.capital/for-developers ; https://docs.velvet.capital/product/portfolio-management ; https://docs.velvet.capital/product/fees
  • Why sufficient / why not (one line): Tier‑1 describes the contract functions and the onchain model of fees/index tokens.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain execution, the verifiability of portfolio shares (index tokens), non‑custodiality and the transparency of deposits/withdrawals/fees are lost.
  • Evidence: Tier‑1 — https://docs.velvet.capital/product/portfolio-management ; https://docs.velvet.capital/for-developers
  • Why sufficient / why not (one line): the product is built around onchain vaults and operations from the wallet.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, VELVET (BEP‑20), on BNB Smart Chain.
  • Evidence: Tier‑1 — https://bscscan.com/address/0x8b194370825E37b33373e74A41009161808C1488
  • Why sufficient / why not (one line): the explorer confirms the token 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): users pay for the service specifically with the VELVET token.
  • Evidence: Tier‑1 — https://docs.velvet.capital/governance/tokenomics
  • Why sufficient / why not (one line): in the tokenomics, payments for AI inference are described with a separate token, VU; VELVET is described as a stake/governance/fee-sharing token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): staking VELVET → veVELVET gives rewards (including fee sharing) and takes part in incentive programs (Gems/emissions).
  • Evidence: Tier‑1 — https://docs.velvet.capital/governance/tokenomics
  • Why sufficient / why not (one line): the tokenomics describes veVELVET rewards, the revenue split and emissions.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): veVELVET gives voting rights on key Velvet DAO decisions (integrations, fee distribution, etc.).
  • Evidence: Tier‑1 — https://docs.velvet.capital/governance/tokenomics
  • Why sufficient / why not (one line): the tokenomics lists “Voting rights on major Velvet DAO decisions”.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): the core functions (trading/creating vaults) are not shown to be impossible without VELVET; the token is mainly about incentives/discounts/governance.
  • Evidence: Tier‑1 — https://docs.velvet.capital/product/trading-terminal ; https://docs.velvet.capital/governance/tokenomics
  • Why sufficient / why not (one line): the trading terminal is described as working “from the wallet”; the tokenomics links VELVET to staking/governance/fee sharing, not to mandatory payment.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.velvet.capital/product/ai-framework What Velvet Unicorn is (multi‑agent AI), what actions it performs (insights + intent execution) and how to open the AI assistant in the dapp.
Tier‑1 https://dapp.velvet.capital An accessible web app (demo) for the trading terminal/portfolios and entry into the AI assistant.
Tier‑1 https://docs.velvet.capital/product/portfolio-management How to create a public portfolio (vault), the deploy steps and strategy management via onchain actions.
Tier‑1 https://docs.velvet.capital/for-developers The existence of a vault contract API: getTokens, multiTokenDeposit/Withdrawal, emergency withdrawal, etc.
Tier‑1 https://docs.velvet.capital/product/fees Platform and vault fees (0.5% execution fee; fees are accrued in vault tokens).
Tier‑1 https://docs.velvet.capital/governance/tokenomics Token stack: VELVET → veVELVET (lock/decay), revenue split, voting rights; VU as the payment token for AI inference.
Tier‑1 https://bscscan.com/address/0x8b194370825E37b33373e74A41009161808C1488 Onchain confirmation of the VELVET contract (BEP‑20, BNB Smart Chain).
Tier‑1 https://bscscan.com/tx/0x86a519ffca3dd89a10ceb8d075595053708b42c882b6a7a1509dba3728bfe543 Creation date of the VELVET token contract (2025‑07‑09).
Tier‑1 https://docs.velvet.capital/security-and-audits The existence of audits/security monitoring and links to the audits repo + bug bounty (Immunefi/Hats).
Tier‑1 https://github.com/Velvet-Capital/audits Public audit report(s) referenced by the official documentation.
Tier‑1 https://immunefi.com/bug-bounty/velvetcapital/ Public bug bounty program (scope/rules/rewards).

No comments to display

Back to top