Skip to main content

DeepFakeAI

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

DeepFakeAI — an AI/Other project on the Ethereum network, token (symbol: FAKEAI).

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 web service for generating deepfake clips (creating videos with “face/voice swapping”) in the cloud.
  • Who it’s for: regular users and teams/developers who need fast clip production via web, Telegram bots or API.
  • Why onchain/token: the token is used as an access/bonus mechanism (access to features per the project’s rules); onchain records the issuance/circulation of the token.
  • What you can actually touch (Tier‑1): the Web App (/app) and the Quickstart Guide on creating the first clip.

How it works (very briefly)

  1. The user does: chooses a character/settings and uploads source materials (per the service interface).
  2. The system does: generates the clip on the cloud infrastructure side and prepares the result.
  3. The user gets: a finished deepfake clip and (optionally) access to additional features (characters/settings/bots/API).
  4. Where the blockchain is: onchain — the issuance and circulation of the ERC‑20 token on Ethereum (the token contract).
  5. Token role (if any): the token is used as part of the access model (holding the token grants free clips per the service rules).

Quick links: AI thesis fit

Project passport

Field Value
Project name DeepFakeAI
Also known as (aliases) FakeAI, FAKEAI
Logo (logo) ../assets/511_deepfakeai_logo.png
Token symbol (ticker) FAKEAI
Category AI/Other | Consumer
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 0x5aef5bba19e6a1644805bd4f5c93c8557b87c62c
Token model (token_type) utility (access)
Max supply 1,000,000,000 FAKEAI
Issuance —
Tokenomics (tokenomics, brief) Holding the token grants free clips per day (per the service rules); minutes are paid for with cryptocurrency (per the service rules).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) deepfake clip generation (cloud)
Use‑case (use_case) deepfake clip creation (web/Telegram/API)
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

DeepFakeAI describes itself as a cloud solution for creating deepfake clips (generative videos) with access via a web application, Telegram bots and a web API. Per the official documentation, the user can quickly start creating clips following the quickstart guide, and also use advanced features (for example, creating a bot for a Telegram group or embedding the service into a website).

Features/modules

  • Web App: the interface for creating clips.
  • Telegram Bots: creation/launch scenarios via bots.
  • Web API: embedding the clip generation function into other products.
  • Custom characters: a library of characters and custom characters (per the documentation).

Typical scenarios

  • Scenario 1: the user opens the web application → creates a clip following the quickstart → receives the generated video.
  • Scenario 2: the user uses the Telegram bot → generates a clip → receives the result in a familiar channel.
  • Scenario 3: a developer connects the Web API → embeds clip generation into their website/product.

Getting started (wallet/network)

  • What you need: an account in the service (registration on the website), as well as access to the web application or Telegram.
  • Network/chain: Ethereum is used only for the token; the main product is a web service.
  • Fees: onchain fees apply to operations with the token; the purchase of “minutes” and the use of the service are described in the project’s pricing section.

Architecture/tech (non‑AI)

  • Components: the web application, Telegram bots, the web API; a separate onchain part — the ERC‑20 token contract.
  • Participant roles: service users, developers/integrators.
  • Where logic runs: clip generation — offchain (in the cloud infrastructure); the token — onchain (Ethereum).
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: holding the token grants the right to free clip creation per day and access to the service features (per the project’s rules).
  • Protocol necessity drivers: the token is used as an access/bonus mechanism, but the product itself (clip generation) remains an offchain service.
  • Issuance/burn: max total supply 1,000,000,000 FAKEAI (per the token contract data in the explorer).
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.

Governance

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

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks of quality/ethics/rights to content and risks of service availability; for the onchain part — standard risks of the ERC‑20 contract and infrastructure.

Project status and timeline

  • Current status: the web service is available; the token is deployed on Ethereum mainnet.
  • Key releases/milestones: —.
  • Roadmap: published in the official documentation (see links_*).

Ecosystem/integrations

  • Integrations: Telegram, web API integrations.
  • Partners: —.
  • Where it’s actually used: the service is oriented toward generating clips via the web application/bots; the evidence — official docs/quickstart (see Evidence).

AI component of the project

  • What is real AI here? deepfake clip generation (a generative AI service) is described in the official documentation, with a quickstart guide.
  • What is truly onchain? onchain — the ERC‑20 token on the Ethereum network (the token contract and its parameters in the explorer).
  • Why is a token needed? per the documentation, holding the token grants the right to free clips per day and access to the service features.
  • Red flags (based on the information found): if the token is positioned as a “protocol necessity” while the onchain logic is limited to ERC‑20 and the product works as an offchain web service; it is also important to separate “access to the service” from evidence of quality/model metrics.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 3
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): AI is described as a working part of the service (clip generation), not only as an intent/roadmap item.
  • Evidence: Tier‑1 — https://deepfakeai.gitbook.io/deepfakeai
  • Why sufficient / why not (one line): When Tier‑1 already describes a working AI service, a separate “intent” flag adds no signal.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The service generates deepfake clips (deepfake clip creation) via the web application and Telegram bots.
  • Evidence: Tier‑1 — https://deepfakeai.gitbook.io/deepfakeai
  • Why sufficient / why not (one line): The Tier‑1 documentation directly describes the product as a cloud‑based deepfake clip creation solution.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a Web App and a quickstart guide describing the creation of the first clip.
  • Evidence: Tier‑1 — https://fakeai.io/app ; https://deepfakeai.gitbook.io/deepfakeai/features/quickstart-guide
  • Why sufficient / why not (one line): The presence of an app surface and a quickstart instruction is sufficient for “what you can touch”.
  • 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): No Tier‑1 benchmark/quality metrics of the model or the results were found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The whitepaper describes the generative process (character selection → clip generation → HD lip-sync) and the access methods (web app / web API / Telegram bot).
  • Evidence: Tier‑1 — https://fakeai.io/whitepaper_2.pdf
  • Why sufficient / why not (one line): The whitepaper provides technical context on the clip generation process and the service components (without public code and quality benchmarks).
  • 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 0x5aef5bba19e6a1644805bd4f5c93c8557b87c62c
  • Evidence: Tier‑1 — https://etherscan.io/token/0x5aef5bba19e6a1644805bd4f5c93c8557b87c62c
  • Why sufficient / why not (one line): The presence of a deployed token contract in the explorer confirms the onchain component.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established (other than the token).
  • Evidence: Tier‑1 — https://deepfakeai.gitbook.io/deepfakeai
  • Why sufficient / why not (one line): Per Tier‑1, the product is described as a web service; onchain logic other than the ERC‑20 token is not confirmed.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established (there is no Tier‑1 justification of onchain criticality for the operation of the service).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 argument “without the blockchain the rationale/security of the product breaks down” we set 0.
  • 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, FAKEAI.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x5aef5bba19e6a1644805bd4f5c93c8557b87c62c
  • Why sufficient / why not (one line): The Tier‑1 explorer confirms the existence of the token.
  • 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 confirmation was found that specifically the FAKEAI token is the mandatory means of payment for minutes/the service.
  • Evidence: Tier‑1 — https://deepfakeai.gitbook.io/deepfakeai/about-deepfakeai/pricing
  • Why sufficient / why not (one line): Tier‑1 states “cryptocurrency can be used to purchase minutes”, but this is not equivalent to “payment specifically with the FAKEAI token”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Not established (there is no Tier‑1 description of staking/slashing/penalties as part of the protocol).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a specific Tier‑1 description of an incentive mechanism via collateral/penalties we set 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of a governance function of the token was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without documentation on governance mechanics we set 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): Not established (a Tier‑1 analysis is needed of whether the token can be replaced by a subscription/fiat without loss of meaning).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without an explicit Tier‑1 comparison of alternatives we set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://deepfakeai.gitbook.io/deepfakeai Description of the product as a cloud‑based deepfake clip creation solution; access via the Web App and Telegram bot.
Tier‑1 https://deepfakeai.gitbook.io/deepfakeai/features/quickstart-guide The presence of a quickstart guide (how to get started and create a clip).
Tier‑1 https://fakeai.io/app “What you can touch”: the web application (app surface).
Tier‑1 https://deepfakeai.gitbook.io/deepfakeai/about-deepfakeai/pricing Access model: purchase of minutes for cryptocurrency; holding the token grants free videos/access to features (as claimed in pricing).
Tier‑1 https://etherscan.io/token/0x5aef5bba19e6a1644805bd4f5c93c8557b87c62c Onchain fact: the ERC‑20 token (contract, max total supply 1,000,000,000 FakeAI).
Tier‑1 https://fakeai.io/whitepaper_2.pdf Whitepaper: generative process, HD lip-sync, web app / API / Telegram bot, payment structure (minutes vs holding).
Tier‑1 — No Tier‑1 source for claim “metrics/benchmarks of the AI model quality” was found.

No comments to display

Back to top