Skip to main content

Mirror Finance

Mirror 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).

Mirror Finance — an AI/Other | DeFi project on the Ethereum network, token (symbol: MFI).

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 protocol that claims “AI‑powered decentralized trading” and an “intelligence layer” for executing strategies onchain.
  • Who it’s for: users who want to use the protocol’s “vault/strategy” mechanics (per the project’s description) and developers/operators of dApp components (if supported).
  • Why onchain/token: per Tier‑1 sources, there is an MFI ERC‑20 token on Ethereum; the detailed necessity of onchain “other than the token” is not established per the available sources.

How it works (very briefly)

  1. The user does: sets the strategy/risk parameters (per the project’s description) and places capital in the protocol mechanics.
  2. The system does: claims that the “intelligence layer” processes data and supports onchain execution of strategies.
  3. The user gets: the results of the strategy/protocol mechanics (without assumptions about returns/forecasts).
  4. Where the blockchain is: the MFI token (ERC‑20) and (per the project’s claims) onchain execution of strategies/operations.
  5. Token role (if any): Tier‑1 describes MFI as the “native utility asset” of the ecosystem; detailed mechanics (payment/staking/governance) are not established per the available sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name Mirror Finance
Also known as (aliases) Mirror, MirrorAI, MFI
Logo (logo) ../assets/672_mirror-finance_logo.svg
Token symbol (ticker) MFI
Category AI/Other | DeFi
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 0xe5d817B48D1B28A9cde3d5001a2B7047F28d5376
Token model (token_type) —
Max supply 1 000 000 000 MFI (total supply; fixed)
Issuance fixed
Tokenomics (tokenomics, brief) Tier‑1 gives the total supply and the distribution by allocations (seed/ecosystem/advisory/…).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI "intelligence layer" for DeFi strategies
Use‑case (use_case) on-chain execution of trading/DeFi strategies
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 0
Last verified 2026-02-11

General project overview

In the Tier‑1 documentation, Mirror Finance is described as a DeFi protocol, an “autonomous capital layer” and “AI‑powered decentralized trading”. In particular, the project highlights the “Intelligence Layer” as a component that “embeds intelligence” into strategy execution and relies on its own AI models (model names are mentioned).

At the same time, no Tier‑1 demonstration (app/demo) was found per the available sources, and no verifiable metrics of the quality/effectiveness of the AI part are recorded.

Features/modules

  • Protocol layer / strategies: protocol mechanics for executing strategies (per the description in the documentation).
  • Intelligence layer: the claimed AI subsystem that “turns data into insights/strategy logic” (per Tier‑1).
  • MFI token: the ecosystem’s utility token with a fixed supply and allocations (per Tier‑1).

Typical scenarios

  • Scenario 1: a user chooses the strategy/risk parameters → interacts with the protocol (vault/strategy) → receives the execution result (without assumptions about returns).
  • Scenario 2: a developer studies the documentation → integrates/uses the protocol primitives in their own dApp (if supported).

Getting started (wallet/network)

  • What you need: an EVM wallet for working on Ethereum and access to the project’s interface/instructions.
  • Network/chain: Ethereum.
  • Fees: Ethereum network fees + (possible) protocol fees (details are not established per the available sources).

Architecture/tech (non‑AI)

  • Components: the protocol’s smart contracts (addresses other than the token are not recorded), documentation, the MFI token.
  • Participant roles: users, liquidity providers/vault participants (by the nature of a DeFi protocol), developers.
  • Where logic runs: the claimed “on-chain strategy execution” — onchain; AI analysis/models — probably offchain (not established strictly).
  • Dependencies: integrations with external protocols are listed in Tier‑1 (as the project’s claims).

Token/economics (expanded, no forecasts)

  • Token utility: Tier‑1 describes MFI as a “native utility asset” intended to support protocol usage/liquidity/ecosystem growth.
  • Protocol necessity drivers: the detailed “necessity” (what breaks down without the token) is not established per the available sources.
  • Who pays fees: — (not established).
  • Where fees go: — (not established).
  • Issuance/burn: the supply is fixed (1 000 000 000 MFI).
  • Security/incentive mechanisms: — (not established).
  • Distribution and token issuance schedule: per Tier‑1, allocations are given (seed/ecosystem/advisory/operations/team/treasury/liquidity pool/reserve).
  • Treasury: there is a “treasury” allocation (as a tokenomics category; without governance details).

Governance

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

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: — (not found per the available sources).
  • Threat model: in this card there are no Tier-1 artifacts (code/addresses of key contracts/audits) and no quality metrics of the AI part; the role of AI, onchain and the token requires separate confirmation.

Project status and timeline

  • Current status: active (there is public documentation and a token).
  • Key releases/milestones: — (not established).
  • Roadmap: see links_* (the roadmap exists as a Tier‑1 link).

Ecosystem/integrations

  • Integrations: Tier‑1 claims integrations with external protocols (the list is given in the documentation as the project’s claim).
  • Partners: — (not established).
  • Where it’s actually used: — (not established).

AI component of the project

  • What is real AI here? The Tier‑1 documentation describes “AI‑powered decentralized trading” and an “Intelligence Layer” with internal models, but without published quality metrics.
  • What is truly onchain? the MFI token on Ethereum is confirmed; and, per the project’s description, “on-chain strategy execution” (without recorded addresses of key contracts).
  • Why is a token needed? Tier‑1 describes MFI as the ecosystem’s utility token; the strict necessity (what breaks down without the token) is not established per the available sources.
  • Red flags (based on the information found): the absence of a demo/public artifacts (AI_2=0) and quality metrics (AI_3=0); possible AI‑washing (many claims without measurable proof); possible onchain‑washing (if onchain boils down to the token); possible token‑washing (the role of the token is described in general terms).

DecAI Fit component summary

  • DecAI Fit: 2/6 — low 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 0
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as an operating component of the protocol (“intelligence layer”), not just as an intent.
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/ ; https://wp.mirrorai.finance/foundations/intelligence-layer
  • Why sufficient / why not (one line): There is a Tier‑1 description of the AI subsystem; this does not replace metrics (AI_3).
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The “Intelligence Layer” AI subsystem is claimed as data processing and support of logic/decisions for DeFi strategies.
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/foundations/intelligence-layer
  • Why sufficient / why not (one line): Tier‑1 explicitly describes the purpose of the AI layer; without a demo/metrics this remains a description, but it is sufficient for AI_1.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No public demo/app for checking the operation of the AI part was found per the available sources.
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/
  • Why sufficient / why not (one line): 1 requires a specific demo/examples (App/Demo) in Tier‑1.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/foundations/intelligence-layer
  • Why sufficient / why not (one line): no Tier‑1 set of quantitative quality metrics/benchmarks was found per the available sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The Tier‑1 documentation describes the “Intelligence Layer”, the data sources and the internal models (named).
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/foundations/intelligence-layer
  • Why sufficient / why not (one line): This provides technical context at the documentation level (without code and metrics).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: MFI ERC‑20 token: 0xe5d817B48D1B28A9cde3d5001a2B7047F28d5376
  • Evidence: Tier‑1 — https://etherscan.io/token/0xe5d817B48D1B28A9cde3d5001a2B7047F28d5376
  • Why sufficient / why not (one line): There is an onchain artifact (the token) on a public network.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: per the available sources, not established (other than the existence of the token).
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/
  • Why sufficient / why not (one line): 1 requires Tier‑1 addresses/a description of useful protocol logic onchain (access/accounting/rules), not general claims.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established what breaks down without onchain (no Tier‑1 argument for criticality was found).
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/
  • Why sufficient / why not (one line): Under the conservative rule — 0 without proof.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, MFI (ERC‑20 on Ethereum).
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/tokenomics/usdmfi ; https://etherscan.io/token/0xe5d817B48D1B28A9cde3d5001a2B7047F28d5376
  • Why sufficient / why not (one line): The Tier‑1 tokenomics + the onchain contract confirm 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): The use of MFI as a mandatory payment for the service is not established in Tier‑1.
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/tokenomics/usdmfi
  • Why sufficient / why not (one line): 1 requires an explicit mechanic “you pay MFI → you get access/service”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Staking/penalties/collateral tied to MFI are not established in Tier‑1.
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/tokenomics/usdmfi
  • Why sufficient / why not (one line): Without explicit rules/mechanics we set 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): A governance role of the MFI token is not established in Tier‑1.
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/tokenomics/usdmfi
  • Why sufficient / why not (one line): 1 requires an explicit description of governance via 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 is not established (insufficient Tier‑1 specifics on the utility).
  • Evidence: Tier‑1 — https://wp.mirrorai.finance/tokenomics/usdmfi
  • Why sufficient / why not (one line): Without a clear role of the token, “replaceable/irreplaceable” cannot be decided correctly.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://wp.mirrorai.finance/ Description of the project as “AI-powered decentralized trading” and the general positioning of the protocol.
Tier‑1 https://wp.mirrorai.finance/foundations/intelligence-layer Tier‑1 description of the “Intelligence Layer”, the data sources and the internal AI subsystem.
Tier‑1 https://wp.mirrorai.finance/tokenomics/usdmfi Tier‑1: the MFI token as the ecosystem’s utility asset; total supply (fixed) and allocations.
Tier‑1 https://etherscan.io/token/0xe5d817B48D1B28A9cde3d5001a2B7047F28d5376 Onchain fact: the MFI ERC‑20 token on Ethereum.
Tier‑1 — No Tier‑1 source for claim “a public demo/app for checking the AI part” was found per the available sources.
Tier‑1 — No Tier‑1 source for claim “what useful logic is onchain other than the token” was found per the available sources.