Skip to main content

Lithium Finance

Lithium Finance (LITH) — 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).

Lithium Finance — an AI/Other / DeFi project in the EVM ecosystem (token on Ethereum; the app/activity is also mentioned for Polygon). The project positions itself as a protocol for valuing illiquid assets (primarily NFTs) that combines machine learning and the “wisdom of the crowd” (pricing quests with expert participation and staking).

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 protocol/service for estimating the price of illiquid assets (for example, NFTs) through a combination of ML models and “collective valuation”.
  • Who it’s for: users/teams who need a reference point for valuing an asset; “expert” participants who are willing to provide valuations for a reward.
  • Why onchain/token: onchain is used for quests/staking/accounting of participation and rewards; the LITH token — for incentives and governance (DAO).
  • What you can actually touch (Tier‑1): the “Pricing Quests” web app — https://lith.finance/app

How it works (very briefly)

  1. The user does: creates a valuation request (pricing quest) or participates in existing quests as a “price expert”.
  2. The system does: ML models build baseline valuation intervals and flag cases where human valuations are needed; participants submit valuations/stakes.
  3. The user gets: an aggregated valuation (and/or indicators) and the quest results; participants receive rewards according to the protocol rules.
  4. Where the blockchain is: the creation/accounting of quests and participation/staking are recorded onchain; part of the quest data references a content identifier (an IPFS approach in the description).
  5. Token role (if any): LITH is used in the quest economy (reward pool/incentives) and in DAO voting.

Quick links: AI thesis fit

Project passport

Field Value
Project name Lithium Finance
Also known as (aliases) LITH
Logo (logo) —
Token symbol (ticker) LITH
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 (based on the presence of docs/app)
Token (standard) ERC-20
Token contract 0x188e817b02e635d482ae4d81e25dda98a97c4a42
Token model (token_type) utility (payments + staking + governance)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) the token participates in reward pools/staking; governance via a DAO
Governance DAO
Admins/keys —
Audit yes
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) ML price estimation + human-in-the-loop quests
Use‑case (use_case) pricing NFTs/illiquid assets
DecAI Fit — AI thesis fit 6/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 3 / 3
Last verified 2026-02-11

General project overview

Lithium Finance describes itself as a decentralized protocol for valuing illiquid assets (primarily NFTs), where the “baseline” valuation is built by quantitative models on trading data, and in cases with a shortage of data, valuations from participants (“price experts”) are used via Pricing Quests. The documentation also describes staking/reputation mechanics and the aggregation of valuations.

Features/modules

  • Pricing Quests: valuation requests and expert participation via the web app.
  • ML models: baseline intervals/predictions and flagging of “difficult” cases.
  • Valuation aggregation and reputation mechanics (described in “Pricing Mechanism”).
  • Governance: Lithium DAO (voting with the LITH token).

Typical scenarios

  • Scenario 1: a team/user initiates a pricing quest → participants provide valuations and stake → the protocol aggregates the results.
  • Scenario 2: a participant enters the app → selects a quest → submits “buy/sell” valuations and a stake → after the quest ends, checks the result and collects the stake/rewards.

Getting started (wallet/network)

  • What you need: an EVM wallet; for participation in the app, the documentation specifies the Polygon network and the need for MATIC for gas.
  • Network/chain: Ethereum (token), Polygon (app usage in the guide).
  • Fees: network fees of the respective network + possible protocol fees (if applicable).

Architecture/tech (non‑AI)

  • Components: quest/staking smart contracts; web interface; storage of the quest description via a content identifier (an IPFS approach in the docs).
  • Participant roles: price seeker (the valuation requester), price experts (participants submitting valuations), DAO members.
  • Where logic runs: onchain — quest/staking/accounting contracts; offchain — the UI and part of the computation/analytics.
  • Dependencies: EVM networks and their RPCs; IPFS identifiers (per the description in the docs).

Token/economics (expanded, no forecasts)

  • Token utility: rewards in quests and participation in governance; also used for staking/a confidence signal (per the guide).
  • Protocol necessity drivers: reward pools and access/participation in quests (per the pricing quest/earn rewards description).
  • Who pays fees: participants pay network fees; possible protocol fees are described as “access fees collected from Price Seekers” (in the docs).
  • Where fees go: the docs state that access fees from price seekers fund prize pools for regular quests.
  • Issuance/burn: not established per Tier‑1 sources.
  • Security/incentive mechanisms: staking (LITH/MATIC) and reputation/weight of valuations (description in “Pricing Mechanism”).
  • Distribution and token issuance schedule: not established per Tier‑1 sources.
  • Treasury: the DAO docs describe management of the treasury and possible service fees.

Governance

  • Who makes decisions: DAO members; voting with the LITH token.
  • How protocol parameters change: via DAO proposals/votes (described in the docs at the level of principles).
  • Where decisions are discussed/made: the project’s official channels (Discord/Telegram) + the governance section in the official docs (see links_*).

Security and incidents

  • Audits: there is a public link to an audit (Hacken) in links_*.
  • Bug bounty: there is a bug bounty page in the official docs.
  • Incidents: not established per Tier‑1 sources.
  • Threat model: the key risks are typical for smart contracts (bugs in contracts, vulnerabilities in staking/accounting, UX phishing risks); no additional Tier‑1 materials on incidents/postmortems were found.

Project status and timeline

  • Current status: mainnet (based on the presence of contracts/an explorer and a working app in the docs).
  • Key releases/milestones: — (not established per Tier‑1 sources).
  • Roadmap: — (in links_*).

Ecosystem/integrations

  • Integrations: the web app and interaction with EVM wallets; other integrations are not established per Tier‑1 sources.
  • Where it’s actually used: the docs describe the scenario of participating in Pricing Quests and receiving rewards.

AI component of the project

  • What is real AI here? ML models analyze trading data and build baseline valuation intervals, and also flag anomalies/cases where human valuations are needed.
  • What is truly onchain? quests/participation/staking and the accounting of results rely on smart contracts and transactions; part of the quest description references a content identifier (an IPFS approach per the docs).
  • Why is a token needed? LITH is used in the quest economy (reward pool/incentives) and in DAO governance.
  • Red flags (based on the information found): part of the logic/analytics is offchain (web interface + ML computation); to assess robustness, public artifacts on contracts/model versioning and the parameters of the economic mechanisms are needed.

DecAI Fit component summary

  • DecAI Fit: 6/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity medium 2
Token necessity high 3
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 a working approach (not only an “intent”).
  • Evidence: Tier‑1 — https://docs.lith.finance/overview/what-is-lithium-finance
  • Why sufficient / why not (one line): AI_0 is used for “intent without evidence”; here Tier‑1 directly describes the ML approach as part of the protocol.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): ML models analyze historical/trading data and provide a baseline valuation/intervals, and also flag problematic data cases.
  • Evidence: Tier‑1 — https://docs.lith.finance/overview/what-is-lithium-finance ; https://docs.lith.finance/overview/how-it-works
  • Why sufficient / why not (one line): the official docs explicitly describe the role of ML in valuation and in identifying data problems/anomalies.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a web app where one can participate in Pricing Quests and submit valuations/a stake.
  • Evidence: Tier‑1 — https://docs.lith.finance/guides/earn-rewards
  • Why sufficient / why not (one line): the Tier‑1 guide directly gives the link to the app https://lith.finance/app and the participation steps.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: — (no quantitative quality metrics/benchmarks were found in Tier‑1 sources).
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.lith.finance/machine-learning/our-approach
  • Why sufficient / why not (one line): the docs describe the approach, but without explicit numerical quality metrics/comparisons.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): a hybrid ML + human‑in‑the‑loop approach and its operating principles are described (baseline prediction intervals + engaging experts).
  • Evidence: Tier‑1 — https://docs.lith.finance/machine-learning/our-approach
  • Why sufficient / why not (one line): there is a technical description of the logic of the ML part and of its interaction with the collective valuation.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (token); Polygon (app usage in the guide)
  • Addresses/identifiers: 0x188e817b02e635d482ae4d81e25dda98a97c4a42 (LITH ERC‑20)
  • Evidence: Tier‑1 — https://etherscan.io/token/0x188e817b02e635d482ae4d81e25dda98a97c4a42 ; https://docs.lith.finance/guides/earn-rewards
  • Why sufficient / why not (one line): there is an explorer link to the token contract and a Tier‑1 indication of the network (Polygon) for interacting with the app.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: quests/participation/staking/aggregation in the protocol, described as operating via smart contracts and transactions (quest creation/accounting of stakes).
  • Evidence: Tier‑1 — https://docs.lith.finance/protocol/pricing-quest ; https://docs.lith.finance/protocol/pricing-mechanism
  • Why sufficient / why not (one line): Tier‑1 describes that creating a quest generates a smart contract transaction and that the valuation mechanism relies on onchain accounting of reputation/weight.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: some functions (accounting of participation/staking/transparency of results) would degrade if replaced by a centralized server, but Tier‑1 has no strict justification that “without the blockchain the product breaks down”.
  • Evidence: Tier‑1 — https://docs.lith.finance/protocol/pricing-quest
  • Why sufficient / why not (one line): the documentation describes the onchain mechanics, but does not formulate the need for “trustless” as a critical property.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the LITH token exists (ERC‑20 contract).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x188e817b02e635d482ae4d81e25dda98a97c4a42
  • Why sufficient / why not (one line): an explorer link to the token contract is given.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): quest rewards/pools are described as a “bounty denominated in LITH”; access fees from price seekers are also described.
  • Evidence: Tier‑1 — https://docs.lith.finance/protocol/pricing-quest
  • Why sufficient / why not (one line): Tier‑1 describes that the reward pool in quests can be denominated in LITH and that fees fund prize pools.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): participants stake LITH (and MATIC for gas/a possible stake) and receive rewards for participation/results.
  • Evidence: Tier‑1 — https://docs.lith.finance/guides/earn-rewards
  • Why sufficient / why not (one line): the guide describes the process of staking and receiving rewards based on the quest results.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): DAO governance uses a voting model with the LITH token.
  • Evidence: Tier‑1 — https://docs.lith.finance/governance/lithium-dao
  • Why sufficient / why not (one line): Tier‑1 explicitly specifies token‑based governance, where LITH is used as the vote.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): no statement was found in Tier‑1 that the token can be fully replaced without loss of protocol functions.
  • Evidence: Tier‑1 — https://docs.lith.finance/governance/lithium-dao ; https://docs.lith.finance/guides/earn-rewards
  • Why sufficient / why not (one line): the token is used in governance and staking; replaceability requires separate proof/a model.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.lith.finance/overview/what-is-lithium-finance ML + crowd wisdom as the basis of the protocol; the role of ML in valuation/detecting data problems
Tier‑1 https://docs.lith.finance/overview/how-it-works hybrid approach: ML provides a baseline valuation and engages the community in “difficult” cases
Tier‑1 https://docs.lith.finance/machine-learning/our-approach description of the hybrid pricing model and the human‑in‑the‑loop logic
Tier‑1 https://docs.lith.finance/guides/earn-rewards the presence of the app (https://lith.finance/app) and the steps for participation/staking/receiving rewards
Tier‑1 https://docs.lith.finance/protocol/pricing-quest quests create an onchain contract transaction; reward pools/fees and the role of LITH
Tier‑1 https://docs.lith.finance/governance/lithium-dao governance via a DAO and voting with the LITH token
Tier‑1 https://etherscan.io/token/0x188e817b02e635d482ae4d81e25dda98a97c4a42 the address of the LITH ERC‑20 token (a verifiable onchain fact)
Tier‑1 https://hacken.io/audits/lithium/sca-lithium-staking-token-sales-aug2021/ the presence of a public audit (a Tier‑1 security artifact)
Tier‑2 https://www.coingecko.com/en/coins/lithium-finance aggregator reference page (context)
Tier‑2 https://coinmarketcap.com/currencies/lithium/ aggregator reference page (context)

No comments to display

Back to top