Skip to main content

YfDAI.finance

YfDAI.finance — 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).

YfDAI.finance, judging by public traces, looks like a DeFi project/token on Ethereum. The public pages of the website/documentation required a login at the time of the check, so the verifiable conclusions are limited to onchain facts (the token contract) and the existence of GitHub repositories.

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 DeFi token/project on Ethereum (per the onchain explorer data).
  • Who it’s for: DeFi users (staking/farming/pools — per the general positioning; the details require Tier‑1).
  • Why onchain/token: the ERC‑20 token Yf‑DAI is confirmed; protocol onchain logic beyond the token is not established per Tier‑1.

How it works (very briefly)

  1. The user does: interacts with the ERC‑20 token (transfers/DEX/staking — if applicable).
  2. The system does: onchain records the token operations on Ethereum.
  3. The user gets: the token at an address and possible DeFi scenarios (the details require access to the documentation/contracts).
  4. Where the blockchain is: Ethereum (the ERC‑20 contract).
  5. Token role (if any): a Tier‑1 source for claim “the token is used for payment for the service/staking/governance” is not confirmed.

Quick links: AI thesis fit

Project passport

Field Value
Project name YfDAI.finance
Also known as (aliases) YfDAI; Yf-DAI
Logo (logo) ../assets/399_yfdai-finance_logo.png
Token symbol (ticker) Yf-DAI
Category DeFi
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) —
Token (standard) ERC-20
Token contract 0xf4CD3d3Fda8d7Fd6C5a500203e38640A70Bf9577
Token model (token_type) —
Max supply 21,000
Issuance —
Tokenomics (tokenomics, brief) max supply is given in the explorer; the utility requires Tier‑1 confirmation
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) DeFi token
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 1
Last verified 2026-02-11

General project overview

Per the Tier‑1 observations at the time of the check, the website and docs lead to a login page, so it was not possible to extract a verifiable description of the product/token utility. Only the existence of the ERC‑20 token Yf‑DAI on Ethereum and the existence of a repository with the smart contract on GitHub are reliably confirmed.

Features/modules

  • ERC‑20 token: an onchain contract on Ethereum.
  • Smart contract repository: a public GitHub repository yfdai.sol (a separate check of conformance to the deployment is required).
  • Documentation/whitepaper: the links require a login/were not extracted.

Typical scenarios

  • Scenario 1: a user interacts with the token → transfers/trades it on a DEX/CEX (as an asset).
  • Scenario 2: a researcher/developer reads the contract in the repository → checks it against onchain.

Getting started (wallet/network)

  • What you need: an EVM wallet.
  • Network/chain: Ethereum.
  • Fees: Ethereum fees for operations with the token.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 contract; potential DeFi contracts/products are not confirmed by Tier‑1.

Token/economics (expanded, no forecasts)

  • Onchain fact: max total supply is given in the explorer.
  • Token utility: not confirmed by Tier‑1 (the documentation is unavailable without a login).

Governance

  • Who makes decisions: — (not established per Tier‑1 sources).

Security and incidents

  • Security advisories: there is a security page in the GitHub repository.
  • Audits / bug bounty / incidents: — (not established per Tier‑1 sources).

Project status and timeline

  • Current status: the token is active onchain; the web links require a login.
  • Roadmap: there is a Medium post (Tier‑2).

Ecosystem/integrations

  • Integrations/partners: — (not established per Tier‑1 sources).

AI component of the project

  • What is real AI here? Tier‑1 confirmation of AI functionality is not established.
  • What is truly onchain? an ERC‑20 token on Ethereum.
  • Why is a token needed? the utility of the token is not confirmed per Tier‑1.
  • Red flags (based on the information found): the docs/whitepaper links are behind a login; without Tier‑1 confirmations of AI/token utility the conclusions are limited.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality low 0
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim: a Tier‑1 statement/roadmap about AI is not confirmed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there are no available Tier‑1 materials about AI on the public pages.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim: a Tier‑1 description of AI features is absent.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: without Tier‑1 sources we do not set the flag.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim: a Tier‑1 demo/guide of the AI part is not confirmed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: the public pages require a login; “what you can touch” is not recorded.
  • 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: no Tier‑1 AI metrics were found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim: no Tier‑1 tech description of the AI component was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: without available Tier‑1 materials we do not set the flag.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0xf4CD3d3Fda8d7Fd6C5a500203e38640A70Bf9577
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf4CD3d3Fda8d7Fd6C5a500203e38640A70Bf9577
  • Why sufficient / why not: the explorer confirms the token address and the network.
  • 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: the existence of the token by itself does not prove protocol onchain logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

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

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim: the project has a token, Yf‑DAI (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf4CD3d3Fda8d7Fd6C5a500203e38640A70Bf9577
  • Why sufficient / why not: the explorer shows the name/symbol and the parameters 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: a Tier‑1 source on the token utility (payments for the service) is not confirmed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there is no available Tier‑1 documentation on the rules of token use.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim: Tier‑1 confirmation of incentives/collateral/penalties via the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there are no available Tier‑1 materials.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim: Tier‑1 confirmation of governance use of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there are no available Tier‑1 materials.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim: a conclusion about the replaceability of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: without Tier‑1 token utility, no strict conclusion can be drawn.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0xf4CD3d3Fda8d7Fd6C5a500203e38640A70Bf9577 the Yf‑DAI token (ERC‑20): address and max total supply
Tier‑1 https://github.com/yfdaifinance/yfdai.sol public repository of the smart contract (requires a separate reconciliation with the deployment)
Tier‑1 — No Tier‑1 source for claim “the token has a confirmed utility (payments/staking/governance)” was found.
Tier‑2 https://yfdaifinance.medium.com/ publications/updates of the project
Tier‑2 https://www.coingecko.com/en/coins/yfdai-finance reference profile of the token/project
Tier‑2 https://coinmarketcap.com/currencies/yfdai-finance/ reference profile of the token/project

No comments to display

Back to top