Skip to main content

Octavia

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

Octavia — an AI/Agents project on the BNB Smart Chain network, token (symbol: VIA).

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 project that positions itself as an AI assistant/tools for communities (including moderation and analytics).
  • Who it’s for: communities/moderators and users who need an assistant/moderation.
  • Why onchain/token: the VIA token exists on BNB Smart Chain; the Tier‑1 documentation describes staking and the governance utility of the token.
  • What you can actually touch (Tier‑1): public docs + “Create Your AI Agent” (app).

How it works (very briefly)

  1. The community connects the tool: enables moderation/analytics/assistant features (per the project’s claim).
  2. The system analyzes messages/content: performs AI moderation and produces answers/insights (as intent/roadmap).
  3. The user gets: assistant answers, moderation or reports.
  4. Where the blockchain is: the VIA token and its operations — onchain (BNB Smart Chain).
  5. Token role: staking + governance utility (per the Tier‑1 documentation).

Quick links: AI thesis fit

Project passport

Field Value
Project name Octavia
Also known as (aliases) VIA, Octavia AI
Logo (logo) ../assets/454_octavia_logo.svg
Token symbol (ticker) VIA
Category AI/Agents
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0x21ac3bb914f90a2bb1a16088e673a9fdda641434
Token model (token_type) utility (staking + governance)
Max supply 100,000,000 VIA
Issuance —
Tokenomics (tokenomics, brief) Total supply 100M; the Tier‑1 docs describe utilities (staking/governance/premium features/train-to-earn as intent).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI assistant for communities
Use‑case (use_case) moderation + analytics + assistant
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

Octavia positions itself as an AI assistant/set of tools for communities: the Tier‑1 roadmap lists moderation, analytics and assistant features (including “proactive support”, “sentiment analysis”, “AI autoban”, etc.). A Tier‑1 tech description of the AI models/quality metrics is not identified, so the AI reality assessment remains conservative (intent + the existence of an app).

Features/modules

  • AI moderation (intent/roadmap): text/images/audio and scenarios for communities.
  • Assistant (intent/roadmap): answers and contextual help for users.
  • App: creating an AI agent (via the “Create Your AI Agent” link).

Typical scenarios

  • Scenario 1: a community connects moderation → receives automated actions and reports (per the roadmap).
  • Scenario 2: a user creates an AI agent via the app → receives a personal agent/interface.
  • Scenario 3: a user interacts with the VIA token (onchain operations).

Getting started (wallet/network)

  • What you need: access to the app and docs; an EVM wallet for BNB Smart Chain (for onchain operations).
  • Network/chain: BNB Smart Chain.
  • Fees: BNB Smart Chain network fees.

Architecture/tech (non‑AI)

  • Components: offchain app/services + the VIA token (onchain).
  • Participant roles: users/communities; token holders.
  • Where logic runs: moderation/assistant — offchain; the token and transactions — onchain (BNB Smart Chain).
  • Dependencies: BNB Smart Chain RPC infrastructure and the project’s offchain services.

Token/economics (expanded, no forecasts)

  • Token utility: staking rewards; governance; token-gated premium features; train-to-earn (as intent) — per the Tier‑1 docs.
  • Protocol necessity drivers: the token is used as a mechanism of incentives (staking rewards) and of participation in governance (per the Tier‑1 docs).
  • Issuance/burn: issuance/burn parameters are not established per Tier‑1 (within this card).
  • Limitation: a Tier‑1 description of “mandatory payment for the service with the token” as pay‑per‑use is not identified.

Governance

  • Who makes decisions: token holders (governance: propose/discuss/vote — per the Tier‑1 docs).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: GitHub and the official channels (see links_*).
  • Keys/multisig: —.

Security and incidents

  • Audits: — (not established per Tier‑1).
  • Bug bounty: — (not established per Tier‑1).
  • Incidents: — (not established per Tier‑1).
  • Threat model: the risks are typical for offchain services and for a token on an EVM network (contract/admin rights/infrastructure).

Project status and timeline

  • Current status: active.
  • Key releases/milestones: — (not established per Tier‑1).
  • Roadmap: published in the docs (see links_*).

Ecosystem/integrations

  • Integrations: —.
  • Partners: — (not established per Tier‑1).
  • Where it’s actually used: the project’s docs and app (see links_*).

AI component of the project

  • What is real AI here? In Tier‑1 sources, AI is described via a list of moderation/analytics/assistant features (roadmap). Tier‑1 proof of a model/quality metrics is not identified.
  • What is truly onchain? the VIA token on BNB Smart Chain (the contract and max supply are visible in the explorer).
  • Why is a token needed? the Tier‑1 docs describe staking rewards and governance utility (as well as token-gated premium features).
  • Red flags (based on the information found): roadmap promises without artifacts; the absence of a Tier‑1 description of the token utility.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 1
Onchain necessity low 1
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): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 1.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No Tier‑1 description of a specific AI model/mechanics of “what the AI does” (in terms of a model/pipeline) was found — only a list of features.
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/project/roadmap
  • Why sufficient / why not (one line): AI_1 requires specifics about the AI action/pipeline, not just feature names.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The website has a link to an application for creating an AI agent (“Create Your AI Agent”).
  • Evidence: Tier‑1 — https://octavia.one/ ; https://app.renatus.ai
  • Why sufficient / why not (one line): The existence of the app provides a reproducible “surface” of the product (without proving the quality of the models).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/project/roadmap
  • Why sufficient / why not (one line): Quality metrics of the AI models are not identified per Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the AI models/versions (architecture/benchmarks) is not identified per Tier‑1.
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/project/roadmap
  • Why sufficient / why not (one line): Without a specific technical artifact we set 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: VIA token: 0x21ac3bb914f90a2bb1a16088e673a9fdda641434
  • Evidence: Tier‑1 — https://bscscan.com/token/0x21ac3bB914f90A2Bb1a16088E673a9fdDa641434
  • Why sufficient / why not (one line): The onchain artifact (token) and the network are 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 existence of the token).
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/project/roadmap
  • Why sufficient / why not (one line): No Tier‑1 description of useful onchain logic beyond the token is identified.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification was found that without the blockchain the product loses a key property.
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/project/roadmap
  • Why sufficient / why not (one line): OC_3 requires an explicit argument; not identified per Tier‑1.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, VIA (BEP‑20), on BNB Smart Chain.
  • Evidence: Tier‑1 — https://bscscan.com/token/0x21ac3bB914f90A2Bb1a16088E673a9fdDa641434
  • Why sufficient / why not (one line): The explorer records the token, the symbol and the supply.
  • 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 the service with the token” as a mandatory mechanism is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/token
  • Why sufficient / why not (one line): There is no Tier‑1 description of a specific payment model.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The Tier‑1 documentation describes staking of VIA with ecosystem rewards.
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/token
  • Why sufficient / why not (one line): The staking rewards confirm the use of the token as an incentive.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): The Tier‑1 docs describe governance: VIA holders can propose/discuss/vote on changes in the ecosystem.
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/token
  • Why sufficient / why not (one line): Tier‑1 directly describes the governance utility of the token.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token with another mechanism is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.octavia.one/docs/token
  • Why sufficient / why not (one line): TK_4 requires an explicit argument; not found.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://octavia.one/ Positioning and the link to the app (“Create Your AI Agent”).
Tier‑1 https://app.renatus.ai App/demo of creating an AI agent.
Tier‑1 https://docs.octavia.one/docs/project/roadmap Roadmap and the list of AI features (intent).
Tier‑1 https://docs.octavia.one/docs/token Tier‑1 utilities of VIA: staking rewards, governance, premium features (token-gated), train-to-earn (intent).
Tier‑1 https://bscscan.com/token/0x21ac3bB914f90A2Bb1a16088E673a9fdDa641434 Onchain fact: the VIA token (BEP‑20), contract and max supply 100,000,000.

No comments to display

Back to top