Skip to main content

DEVAI

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

DEVAI — an AI/Other project on Ethereum, token (symbol: 0xDEV).

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 Telegram bot and web application for generating and deploying smart contracts (Solidity) based on user parameters, “without writing code” (claimed in the Tier‑1 whitepaper on GitBook and on the website).
  • Who it’s for: users who need a simplified process for deploying contracts (claimed).
  • Why onchain/token: the ERC‑20 token 0xDEV on Ethereum is confirmed onchain; the necessity of the token for the bot/web application features is not established per Tier‑1.
  • What you can actually touch (Tier‑1): web app app.contractdevai.com and Telegram bot ContractDEVAI_bot (see links_*).

How it works (very briefly)

  1. The user does: sets the parameters of the desired smart contract in the bot/web application (claimed).
  2. The system does: generates the contract and helps complete the deployment/verification steps and basic operations (claim).
  3. The user gets: a deployed smart contract (if the user completes the process; the technical implementation is not verified against public code).
  4. Where the blockchain is: onchain — contract deployment by the user + the 0xDEV token on Ethereum.
  5. Token role: not established per Tier‑1 (other than the existence of the token).

Quick links: AI thesis fit

Project passport

Field Value
Project name DEVAI
Also known as (aliases) Contract DEVAI, 0xDEV
Logo (logo) ../assets/779_devai_logo.webp
Token symbol (ticker) 0xDEV
Category AI/Other | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xf7498c98789957f4ee53b3e37ff5b7ef8a6cfc7b
Token model (token_type) —
Max supply 1 000 000 0xDEV
Issuance —
Tokenomics (tokenomics, brief) No Tier‑1 description of the mandatory role of the token in the product was found.
Governance —
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) smart contract template generation
Use‑case (use_case) smart contract deployment via bot/web app
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

DEVAI describes itself as a tool for generating and deploying smart contracts: the user sets parameters, and the bot/web application helps form a contract and complete the deployment steps. Within DecAIHub, this is recorded as an AI‑assisted dev‑workflow (claim). A public code/implementation repository is not listed in links_*, so the level of verifiability is limited to the existence of a Tier‑1 description and a demo surface (bot/web application).

Features/modules

  • Deployer bot (Telegram): generation and deployment steps (claimed).
  • Web app: an interface for the same operations (claimed).

Typical scenarios

  • Scenario 1: a user sets token/contract parameters → receives the result and deployment instructions (claimed).
  • Scenario 2: a user interacts with the 0xDEV token → operations are visible onchain.

Getting started (wallet/network)

  • What you need: Telegram or a web browser for the demo surface; an Ethereum wallet for onchain operations.
  • Network/chain: Ethereum mainnet.
  • Fees: Ethereum network fees for transactions.

Architecture/tech (non‑AI)

  • Components: Telegram bot + web app (offchain), 0xDEV token (onchain).
  • Participant roles: users, service operators, Ethereum infrastructure.
  • Where logic runs: generation/interfaces — offchain; the token and user deployments — onchain.
  • Dependencies: Ethereum infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 (other than the fact of the token’s existence).
  • Supply parameters: max total supply 1 000 000 0xDEV (onchain).
  • Who pays fees: users (gas in ETH) for transactions.
  • Where fees go: to Ethereum network validators/stakers (within the network mechanics).
  • Issuance/burn: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: an audit is claimed (see links_*).
  • Bug bounty: not found per Tier‑1.
  • Incidents: —.
  • Threat model: risks of the token smart contracts and the offchain service; difficult to assess without public code.

Project status and timeline

  • Current status: token on Ethereum mainnet; the demo surface is available (bot/web application).
  • Key releases/milestones: —.
  • Roadmap: present in the whitepaper (see links_*).

Ecosystem/integrations

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

AI component of the project

  • What is real AI here? The Tier‑1 whitepaper claims generation of custom smart contracts tailored to user needs.
  • What is truly onchain? The ERC‑20 token 0xDEV on the Ethereum network; when deploying, the user creates their own contracts onchain.
  • Why is a token needed? No Tier‑1 source unambiguously linking use of the product to the necessity of the token was found.
  • Red flags (based on the information found): absence of a public repository/code in links_*; many claims about “no code”, but the verifiability of the implementation is limited.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity low 1
Token necessity low 0
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 part of the current product, not just a roadmap/intent.
  • Evidence: Tier‑1 — https://devai.gitbook.io/whitepaper
  • Why sufficient / why not (one line): There is a Tier‑1 description of AI features.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Generation of custom smart contracts based on user parameters (claim).
  • Evidence: Tier‑1 — https://devai.gitbook.io/whitepaper ; https://contractdevai.com
  • Why sufficient / why not (one line): Tier‑1 sources describe the purpose of the AI part.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a demo surface: web app and Telegram bot.
  • Evidence: Tier‑1 — https://app.contractdevai.com ; https://t.me/ContractDEVAI_bot
  • Why sufficient / why not (one line): The existence of accessible product surfaces.
  • 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): Quality metrics for the AI part were not found in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The tech description/architecture of the AI component and model versions are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Insufficient details on the AI implementation.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 token contract for 0xDEV: 0xf7498c98789957f4ee53b3e37ff5b7ef8a6cfc7b
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf7498c98789957f4ee53b3e37ff5b7ef8a6cfc7b
  • Why sufficient / why not (one line): The token contract is verifiable via 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 is no Tier‑1 confirmation of onchain logic of the product beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has an ERC‑20 token, 0xDEV, on the Ethereum network.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf7498c98789957f4ee53b3e37ff5b7ef8a6cfc7b
  • Why sufficient / why not (one line): The existence of the token is verifiable onchain.
  • 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): No Tier‑1 statement about the necessity of payment for the service with the token was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The product’s tokenomics are not disclosed in the available sources.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Staking/incentives via the token are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Tier‑1 tokenomics details are needed.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance use of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no description of governance mechanics.
  • 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 information on the necessity of the token.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://devai.gitbook.io/whitepaper Tier‑1 description of the product (bot/web app) and the claimed generation/deployment features.
Tier‑1 https://contractdevai.com Tier‑1 website: links to the web app and Telegram bot (demo surface).
Tier‑1 https://app.contractdevai.com Demo surface: web app.
Tier‑1 https://t.me/ContractDEVAI_bot Demo surface: Telegram bot.
Tier‑1 https://app.solidproof.io/projects/devai-token Public audit page (SolidProof) for the DEVAI token (existence of an audit).
Tier‑1 https://etherscan.io/token/0xf7498c98789957f4ee53b3e37ff5b7ef8a6cfc7b Onchain facts: 0xDEV token, Ethereum network, contract, max supply.
Tier‑2 https://coinmarketcap.com/currencies/devai/ Aggregator profile (for reference).

No comments to display

Back to top