Skip to main content

Raven Protocol

Raven Protocol (RAVEN) — 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).

Raven Protocol — a project about distributed computing/model training (decentralized deep learning) with open repositories and documentation (Tier‑1: GitHub org + docs). The RAVEN token/asset is visible in the block explorer.

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 network/framework for distributed training/computing (deep learning), built around a set of libraries/repositories (Tier‑1).
  • Who it’s for: developers and teams that need distributed training/compute (claimed).
  • Why onchain/token: the RAVEN asset is confirmed in the block explorer; the necessity of the token in the protocol is not established per Tier‑1.

How it works (very briefly)

  1. The user does: runs training/a task via the library/infrastructure (claimed in the docs/repos).
  2. The system does: distributes computing/training across participants/nodes (claimed).
  3. The user gets: the result of the computation/training (claimed).
  4. Where the blockchain is: only the onchain artifact of the token/asset is confirmed; the onchain logic of the protocol is not established per Tier‑1.
  5. Token role (if any): the token/asset exists; the token utility (payment/incentives/governance) is not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name Raven Protocol
Also known as (aliases) RAVEN
Logo (logo) ../assets/546_raven-protocol_logo.png
Token symbol (ticker) RAVEN
Category AI/Compute | Infra
Primary chain (chain) —
Type non-EVM
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) —
Token (standard) —
Token contract RAVEN-F66 (asset id)
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) distributed deep learning / compute
Use‑case (use_case) distributed training
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 0 / 1
Last verified 2026-02-11

General project overview

Raven Protocol describes itself as a decentralized network/infrastructure for distributed training and computing (deep learning), which is confirmed by the existence of repositories and documentation on GitHub (Tier‑1).
Per Tier‑1, no specific onchain mechanics are established other than the existence of the token/asset.

Features/modules

  • Repositories/libraries for distributed training and compute (Tier‑1: GitHub).
  • Project documentation (Tier‑1: GitHub docs).

Typical scenarios

  • Scenario 1: a developer runs distributed training → receives a trained model/result (claimed).
  • Scenario 2: a participant provides compute → receives participation in the network (the reward mechanics are not established per Tier‑1).

Getting started (wallet/network)

  • What you need: follow the documentation/repositories (see links_*).
  • Network/chain: the network/chain parameters are not recorded per Tier‑1; the token/asset is visible in the public explorer.
  • Fees: not established per Tier‑1.

Architecture/tech (non‑AI)

  • Components: offchain compute/nodes + client libraries/repositories (Tier‑1: GitHub).
  • Participant roles: requesters (task requesters), compute providers (executors) — claimed.
  • Where logic runs: computing/training — offchain; the onchain part (other than the token) is not established.
  • Dependencies: — (not found per Tier‑1).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1.
  • Protocol necessity drivers: not established.
  • Who pays fees: not established.
  • Where fees go: not established.
  • Issuance/burn: — (not established).
  • Security/incentive mechanisms: — (not established).
  • Distribution and token issuance schedule: — (not established).
  • Treasury: — (not established).

Governance

  • Who makes decisions: — (not established).
  • How protocol parameters change: — (not established).
  • Where decisions are discussed/made: GitHub/social media (see links_*).
  • Keys/multisig: — (not established).

Security and incidents

  • Audits: — (not found per Tier‑1).
  • Bug bounty: —.
  • Incidents: — (not found per Tier‑1).
  • Threat model: the token utility is not confirmed; there is also a risk of a lack of onchain evidence on the economics/incentives.

Project status and timeline

  • Current status: mainnet (based on the presence of a public asset explorer).
  • Key releases/milestones: see GitHub Releases (links_*).
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: — (not found per Tier‑1).
  • Partners: — (not found per Tier‑1).
  • Where it’s actually used: — (not found per Tier‑1).

AI component of the project

  • What is real AI here? In the Tier‑1 repositories and documentation, the project describes distributed deep learning/compute (AI reality at the level of intent/docs).
  • What is truly onchain? The RAVEN asset is confirmed in the block explorer; the onchain logic of the protocol (other than the token) is not established per Tier‑1.
  • Why is a token needed? The existence of the token is confirmed; Tier‑1 evidence of the necessity of the token (payment/incentives/governance) is not established.
  • Red flags (based on the information found): risk of token‑washing (utility not confirmed); the economic model of the network and the addresses/contracts (if any) require re‑checking.

DecAI Fit component summary

  • DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
Component Level Score
AI reality high 2
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 partial 1
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 = 2.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the project describes distributed training/computing for neural networks (deep learning) as its main function.
  • Evidence: Tier‑1 — https://github.com/ravenprotocol/ravdl/blob/main/README.md
  • Why sufficient / why not (one line): there is a specific description of the purpose of the libraries/network.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a public “touch it” demo (app/demo) is not recorded per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no explicit Tier‑1 demo → 0.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1.
  • Context (version/date/how measured): not found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without metrics/context we set 0.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): there is technical documentation/repositories on the libraries/components (architectural context).
  • Evidence: Tier‑1 — https://github.com/ravenprotocol/docs, https://github.com/ravenprotocol
  • Why sufficient / why not (one line): the existence of Tier‑1 tech docs is sufficient for 1 at the level of “a description exists”.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Chain (asset explorer)
  • Addresses/identifiers: RAVEN asset: RAVEN-F66
  • Evidence: Tier‑1 — https://explorer.bnbchain.org/asset/RAVEN-F66
  • Why sufficient / why not (one line): the existence of the onchain artifact is confirmed in the block 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/asset).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no grounds for 1 were found → 0.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established (strictly).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): insufficient justification → 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token/asset, RAVEN.
  • Evidence: Tier‑1 — https://explorer.bnbchain.org/asset/RAVEN-F66
  • Why sufficient / why not (one line): the existence is confirmed by 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): Tier‑1 confirmation of payment for compute/the service with the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without confirmation → 0.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): economic incentives/collateral via the token are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): insufficient data → 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no grounds for 1 were found → 0.
  • 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.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): insufficient data → 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://github.com/ravenprotocol/docs Tier‑1: project documentation (AI/compute context)
Tier‑1 https://github.com/ravenprotocol/ravdl/blob/main/README.md Tier‑1: purpose/description of the library for distributed deep learning
Tier‑1 https://explorer.bnbchain.org/asset/RAVEN-F66 onchain: the existence of the RAVEN asset
Tier‑1 — No Tier‑1 source on the token utility (payment/incentives/governance) was found.
Tier‑2 https://coinmarketcap.com/currencies/raven-protocol/ reference token profile (not proof of utility)
Tier‑3 — —

No comments to display

Back to top