Skip to main content

Lunos

Lunos (UNO / UnoRe) — 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).

Lunos positions itself as onchain insurance/risk coverage, where the evaluation/processing of claims is automated by AI agents; a web‑app for viewing/buying coverage is available, as well as a separate governance section with UNO staking (veUNO).

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 dApp for onchain coverage (insurance/risk protection) + a governance module with token staking.
  • Who it’s for: users who need to buy risk coverage; DAO/voting participants.
  • Why onchain/token: onchain coverage and governance via veUNO; the UNO token exists as an ERC‑20 on Ethereum.
  • What you can actually touch (Tier‑1): https://app.lunos.xyz/ (Coverage) and https://app.lunos.xyz/governance (veUNO).

How it works (very briefly)

  1. The user does: chooses a risk type in the web‑app and buys coverage (per the Coverage interface).
  2. The system does: keeps the accounting/terms of the coverage onchain (judging by the form of the product) and provides governance mechanics via veUNO.
  3. The user gets: coverage (a policy) and/or the right to vote when staking the token.
  4. Where the blockchain is: the UNO token (ERC‑20) and the dApp interactions (buying coverage/staking/DAO).
  5. Token role (if any): the governance section states that staking UNO gives voting power (veUNO).

Quick links: AI thesis fit

Project passport

Field Value
Project name Lunos
Also known as (aliases) UnoRe; UNO
Logo (logo) ../assets/398_unore_logo.svg
Token symbol (ticker) UNO
Category AI/Agents | DeFi | Insurance
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active (web‑app available)
Token (standard) ERC-20
Token contract 0x474021845c4643113458ea4414bdb7fb74a01a77
Token model (token_type) utility (governance)
Max supply 384,649,206
Issuance —
Tokenomics (tokenomics, brief) max supply is given in the explorer; there are veUNO mechanics for voting
Governance DAO
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agents for application evaluation/processing
Use‑case (use_case) on-chain coverage + DAO governance
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 2 / token_score 2 / evidence_score 2
Last verified 2026-02-11

General project overview

Per the Tier‑1 Lunos website, the project offers onchain risk coverage (insurance) and describes the use of AI agents to automate the evaluation/verification of claims. A web‑app is available where one can view the available coverage types (for example, “Smart Contract Vulnerability”, “Stablecoin DePeg”) and a separate governance section.

Important for DecAIHub: the onchain existence of the UNO token (ERC‑20) and the existence of a dApp interface are confirmed; at the same time, the details of “verifiable AI” and of the AVS/operator architecture are described at the level of website claims and require further verification against the implementation/contracts (if/when they are public).

Features/modules

  • Coverage dApp: choosing a risk type and buying coverage via app.lunos.xyz.
  • Governance / veUNO: staking UNO to obtain voting power and vote (via veUNO).
  • AI agents for claim assessment: claimed as a component for automating evaluation/verification.
  • Security Hub: a separate “Security Hub” page (content/services rather than a protocol module).

Typical scenarios

  • Scenario 1: a user connects a wallet → chooses a risk type → buys coverage.
  • Scenario 2: a token holder stakes UNO → receives veUNO → votes on proposals (per the governance description).
  • Scenario 3: a protocol/project looks at “For protocols” and considers listing coverage.

Getting started (wallet/network)

  • What you need: web access to https://app.lunos.xyz/ and an EVM wallet.
  • Network/chain: Ethereum (the UNO token).
  • Fees: Ethereum fees for onchain interactions (purchase/staking/transactions).

Architecture/tech (non‑AI)

  • Components: the web‑app (Coverage/Governance), the UNO token (ERC‑20).
  • Where logic runs: buying coverage/staking/voting imply onchain interactions; the AI agents and data verification — probably offchain.

Token/economics (expanded, no forecasts)

  • Onchain fact: the UNO token is an ERC‑20; max total supply is given in the explorer.
  • Staking/voting (Tier‑1): the governance page describes staking UNO to obtain veUNO and voting power.
  • Payment for coverage with the token: No Tier‑1 source for claim “coverage is bought with UNO” was found (the interface shows “Buy cover”, but the terms/currency were not extracted as a rule).

Governance

  • Who makes decisions: DAO (per the governance/veUNO interface).
  • Where decisions are discussed/made: Snapshot is mentioned (in the governance interface).

Security and incidents

  • Security Hub: there is a separate “Security Hub” page with content and partners (rather a service part).
  • Audits / bug bounty: not established per Tier‑1 sources.
  • Incidents: — (not established per Tier‑1 sources).

Project status and timeline

  • Current status: the web‑app is available (Coverage/Governance).
  • Roadmap: there is a Medium post (Tier‑2).

Ecosystem/integrations

  • Integrations/partners: the website lists partners/logos; this is context and requires targeted verification against agreements/integrations.

AI component of the project

  • What is real AI here? AI agents are claimed that analyze policies/terms and evaluate claim events (per the website description).
  • What is truly onchain? the dApp for coverage and the governance module; the UNO token (ERC‑20).
  • Why is a token needed? staking UNO gives veUNO and voting power (Tier‑1 governance interface).
  • Red flags (based on the information found): “verifiable AI / AVS” are described at the level of claims; they should be double‑checked against the contracts/operators/implementation docs.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim: AI is described as part of the current product (agents for claims), not only as a plan.
  • Evidence: Tier‑1 — https://lunos.xyz/
  • Why sufficient / why not: the intent flag applies in the absence of a description of AI features.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim: AI agents scan policies and evaluate terms/events for processing claims (per the website description).
  • Evidence: Tier‑1 — https://lunos.xyz/
  • Why sufficient / why not: the Tier‑1 website describes the role of the AI agents in the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim: a public web‑app for risk coverage (Coverage) and a governance interface (veUNO).
  • Evidence: Tier‑1 — https://app.lunos.xyz/ ; https://app.lunos.xyz/governance
  • Why sufficient / why not: there is an accessible product interface; at the same time, no separate demo of the “AI pipeline” itself is visible in the UI.
  • 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: the Tier‑1 sources do not record reproducible quality metrics of the AI agents.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim: no Tier‑1 tech description of the architecture of the AI part (models/versions/operators) was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: the public pages describe the concept, without engineering specifications.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0x474021845c4643113458ea4414bdb7fb74a01a77
  • Evidence: Tier‑1 — https://etherscan.io/token/0x474021845c4643113458ea4414bdb7fb74a01a77
  • Why sufficient / why not: the explorer confirms the existence of the token and the contract address.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the dApp for buying coverage and the governance module with staking/voting.
  • Evidence: Tier‑1 — https://app.lunos.xyz/ ; https://app.lunos.xyz/governance
  • Why sufficient / why not: the existence of dApp interfaces points to onchain interaction beyond just “the token exists”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: a strict test of onchain criticality is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: without a description of the contracts/threat model, no strict conclusion about criticality can be drawn.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim: the project has a token, UNO (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x474021845c4643113458ea4414bdb7fb74a01a77
  • 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: No Tier‑1 source for claim “coverage/the service is paid for with the UNO token” was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: the available Tier‑1 pages contain no rule of payment in UNO.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim: staking/locking UNO to obtain veUNO and accruals/rewards (per the governance interface).
  • Evidence: Tier‑1 — https://app.lunos.xyz/governance
  • Why sufficient / why not: the Tier‑1 interface explicitly describes staking/lock and the veUNO parameters.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim: stake UNO → receive veUNO → voting power for the DAO/proposals (per the governance interface).
  • Evidence: Tier‑1 — https://app.lunos.xyz/governance
  • Why sufficient / why not: the interface explicitly links UNO/veUNO to voting.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim: a strict conclusion about the replaceability of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: even with governance utility present, a separate analysis of alternatives is required (offchain memberships, reputation, etc.).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://lunos.xyz/ description of the product (onchain insurance) and of the role of the AI agents in the evaluation/processing of claims
Tier‑1 https://app.lunos.xyz/ an accessible Coverage dApp interface (“what you can touch”)
Tier‑1 https://app.lunos.xyz/governance staking UNO → veUNO → voting power (token utility / governance)
Tier‑1 https://unore.gitbook.io/uno-re/governance-and-dao/veuno description of the veUNO model: lock UNO → veUNO, voting power and rewards (protocol documentation)
Tier‑1 https://etherscan.io/token/0x474021845c4643113458ea4414bdb7fb74a01a77 the UNO token (ERC‑20): address and max total supply
Tier‑1 — No Tier‑1 source for claim “coverage/the service is paid for with the UNO token” was found.
Tier‑2 https://medium.com/uno-re publications/updates of the project
Tier‑2 https://www.coingecko.com/en/coins/uno-re reference profile of the token/project
Tier‑2 https://coinmarketcap.com/currencies/unore/ reference profile of the token/project

No comments to display

Back to top