Skip to main content

Lumerin

Lumerin (LMR) — 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).

Lumerin describes a protocol for controlling the routing of P2P data streams via smart contracts and products around Bitcoin hashpower (marketplace, futures) and validators, and also highlights the “Decentralized AI” direction as a use‑case of the infrastructure (users ↔ compute providers ↔ smart agents).

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 hashpower marketplace and a validator layer with staking/punishments + the “Decentralized AI” infrastructure direction.
  • Who it’s for: buyers/sellers of hashpower contracts, validators, participants of the compute ecosystem.
  • Why onchain/token: onchain is used for contracts/settlement and security rules (stake/complaints/punishments); LMR is used for validator staking and economic settlements in the products.

How it works (very briefly)

  1. The user does: buys/sells a hashpower contract or runs a validator node.
  2. The system does: records the rules/settlement via smart contracts; in the validator layer it applies stake/complaints/punishments.
  3. The user gets: an executed contract (hashpower/settlement) or validator rewards for correct operation.
  4. Where the blockchain is: EVM networks; the LMR token is on Ethereum, and a contract on Arbitrum is also listed on the tokenomics page.
  5. Token role (if any): LMR is used for validator staking/punishments and as the unit of the economy (prices/rewards in the docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name Lumerin
Also known as (aliases) LMR
Logo (logo) ../assets/301_lumerin_logo.svg
Token symbol (ticker) LMR
Category AI/Compute | DePIN | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active (website/docs available)
Token (standard) ERC-20
Token contract 0x4b1D0b9F081468D780Ca1d5d79132b64301085d1
Token model (token_type) utility (staking)
Max supply 1,000,000,000 LMR (Etherscan Max Total Supply)
Issuance fixed max total supply (per Etherscan)
Tokenomics (tokenomics, brief) the tokenomics page publishes the distribution and the EVM contracts (ETH + Arbitrum)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) decentralized AI data routing / AI marketplace (positioning only)
Use‑case (use_case) hashpower marketplace + validator staking
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 3 / 2 / 2
Last verified 2026-02-11

General project overview

On the Lumerin website, the protocol is described as a foundational layer that uses smart contracts to control how P2P data streams are routed, accessed and transacted. The tokenomics page publishes the token contract addresses (ETH + Arbitrum) and the LMR distribution.

The validator section of the GitBook describes the staking parameters and punishments (penalties for going offline after complaints), which points to protocol‑level onchain logic beyond the mere issuance of a token.

Features/modules

  • Hashpower marketplace (the product use‑case on the website).
  • Validator: stake/complaints/punishments (docs).
  • Tokenomics: distribution and contract addresses (website tokenomics).
  • The “Decentralized AI” direction as a use‑case of the infrastructure (website AI page).

Typical scenarios

  • Scenario 1: buying/selling a hashpower contract → settlement via smart contracts.
  • Scenario 2: a validator stakes LMR and runs a node → receives rewards while operating, and falls under punishments for violations (per the docs).

Getting started (wallet/network)

  • What you need: an EVM wallet; LMR for staking/operations (if applicable).
  • Network/chain: Ethereum/Arbitrum (per the tokenomics page), and the product’s EVM networks.
  • Fees: gas of the chosen network.

Architecture/tech (non‑AI)

  • Components: smart contracts, validator nodes, product web applications.
  • Participant roles: contract buyers/sellers, validators.
  • Where logic runs: settlement/economic rules — onchain; user interaction with the UI — offchain.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: validator stake and economic settlements (prices/rewards in the docs).
  • Issuance/burn: max total supply is fixed in Etherscan (1B).
  • Distribution: treasury/community/mineable, etc. are published on the tokenomics page.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.

Project status and timeline

  • Current status: mainnet (the token and products are available via the website/docs).
  • Roadmap: there is a roadmap page.

Ecosystem/integrations

  • Integrations: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? The website has Tier‑1 “Decentralized AI” positioning and a description of the protocol’s role as infrastructure for connecting users, compute providers and smart agents; at the same time, AI model quality metrics are not provided (the project is primarily infrastructural).
  • What is truly onchain? Smart contract settlement and validator security rules (stake/complaints/punishments), plus the LMR token and the published contract addresses.
  • Why is a token needed? The token is used as the unit of staking/punishments and economic settlements.
  • Red flags (based on the information found): the absence of public quality metrics for the AI part (as a model) — expected for an infrastructure layer, but it limits the verifiability of the AI claims.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity high 3
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
  • Evidence: —
  • Why sufficient / why not (one line): the intent flag is not applied separately, since the AI facts are recorded in AI_1/AI_4.

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the AI page describes the protocol’s role in the Morpheus AI Network and in a two‑sided market for AI services (users ↔ compute providers ↔ smart agents).
  • Evidence: Tier‑1 — https://lumerin.io/ai
  • Why sufficient / why not (one line): a functional AI context (infrastructure/marketplace) is described, albeit without model metrics.

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Evidence: —
  • Why sufficient / why not (one line): no reproducible demo of an AI module as a model/inference is identified in the sources of this card.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Evidence: —

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

  • AI_4 (decision): 1
  • Claim (one line): the AI page describes the architectural roles and the onchain/offchain split in the ecosystem.
  • Evidence: Tier‑1 — https://lumerin.io/ai
  • Why sufficient / why not (one line): there is a Tier‑1 architectural description at the system level.

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: LMR token (Ethereum): 0x4b1D0b9F081468D780Ca1d5d79132b64301085d1
  • Evidence: Tier‑1 — https://etherscan.io/token/0x4b1D0b9F081468D780Ca1d5d79132b64301085d1 ; https://lumerin.io/tokenomics
  • Why sufficient / why not (one line): the token contract and addresses are published in the explorer and on the tokenomics page.

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the validator mechanics include stake/complaints/punishments.
  • Evidence: Tier‑1 — https://gitbook.lumerin.io/lumerin-hashpower-marketplace/validator
  • Why sufficient / why not (one line): onchain actions beyond the token are described.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without publicly verifiable stake/punish rules and trustless settlement, the key property of the marketplace/security weakens.
  • Evidence: Tier‑1 — https://gitbook.lumerin.io/lumerin-hashpower-marketplace/validator ; https://lumerin.io/
  • Why sufficient / why not (one line): the protocol uses economic rules and settlement as the core of the product.

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Evidence: Tier‑1 — https://etherscan.io/token/0x4b1D0b9F081468D780Ca1d5d79132b64301085d1

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): the docs specify prices/settlements and validator rewards in LMR.
  • Evidence: Tier‑1 — https://gitbook.lumerin.io/lumerin-hashpower-marketplace/validator
  • Why sufficient / why not (one line): the protocol’s economic parameters are denominated in LMR.

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

  • TK_2 (decision): 1
  • Claim (one line): a validator stakes LMR and can be penalized (punishments) based on complaints.
  • Evidence: Tier‑1 — https://gitbook.lumerin.io/lumerin-hashpower-marketplace/validator
  • Why sufficient / why not (one line): stake and punish are described as part of security.

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Evidence: —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Evidence: —
  • Why sufficient / why not (one line): the protocol role of the token is described as part of staking/punishments and settlements.

Evidence (table)

Tier Source What it proves
Tier‑1 https://lumerin.io/ Description of the products and the “smart contract settlement” thesis.
Tier‑1 https://lumerin.io/ai AI positioning and the system‑level description of Morpheus/Lumerin.
Tier‑1 https://gitbook.lumerin.io/lumerin-hashpower-marketplace/validator Stake/complaints/punishments and the validator mechanics.
Tier‑1 https://lumerin.io/tokenomics Contract addresses (ETH + Arbitrum) and the token distribution.
Tier‑1 https://etherscan.io/token/0x4b1D0b9F081468D780Ca1d5d79132b64301085d1 The LMR contract and max total supply 1B.

No comments to display

Back to top