Skip to main content

Clore.ai / CLORE

Clore.ai / CLORE — 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).

Clore.ai — an AI/Compute / Infra project (a marketplace for renting GPUs/servers for Docker workloads: AI training, rendering, mining), native network coin CLORE (symbol: CLORE).

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 marketplace where hardware owners rent out GPU servers, and users run containers (Docker) for their tasks (including model training).
  • Who it’s for: ML engineers/teams (GPU rental for training/inference), 3D/video rendering, miners; GPU/farm owners (renting out resources).
  • Why onchain/token: CLORE is the native coin, used as a payment method and as part of the incentives/discounts (Proof‑of‑Holding) within the ecosystem.

How it works (very briefly)

  1. The user does: selects a server/GPU on clore.ai and launches a container (or rents out their own GPU as a provider).
  2. The system does: orchestrates the rental/payment/access to the container and accrues bonuses/discounts for holders (Proof‑of‑Holding).
  3. The user gets: compute “by the hour” (AI training / render / mining), while the provider gets income/bonuses.
  4. Where the blockchain is: the CLORE network handles the issuance and circulation of the coin; the onchain explorer shows issuance/circulation/transactions.
  5. Token role: payment in the ecosystem, bonuses/discounts (PoH), and also a “transparently mined” asset with a capped issuance (per the website).

Quick links: AI thesis fit

Project passport

Field Value
Project name Clore.ai / CLORE
Also known as (aliases) Clore, CLORE coin
Logo (logo) —
Token symbol (ticker) CLORE
Category AI/Compute | Infra
Primary chain (chain) CLORE
Type non-EVM
Network status mainnet
Consensus (consensus) PoW
Launch date (launch_date) 2022-12 (marketplace “publicly opened”, per the roadmap on the website)
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (discounts + payments + incentives)
Max supply 1.3B coins (per the website)
Issuance halving / issuance via mining (per the website)
Tokenomics (tokenomics, brief) no premine/ICO; 50% of the block to miners, 40% hosters, 10% team; PoH bonuses/discounts for holders (per the website)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) GPU compute for AI training
Use‑case (use_case) GPU rental marketplace (Docker workloads)
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 1 / 2 / 1
Last verified 2026-02-11

General project overview

Clore.ai is a marketplace for renting compute resources that directly targets GPU workloads and “anything that runs in Docker”. The website lists the use‑cases: AI training, rendering, mining. The website separately describes a “Proof of Holding” system: CLORE holders receive bonuses/discounts, while “money is not blocked” (per the description of the mechanics on the website).

From the crypto side, CLORE is described as a “transparently mined cryptocurrency” with a capped issuance (cap 1.3B) and the claims “no premine or ICO”, “ASIC‑resistant”, as well as a distribution of the block reward between miners/hosters/the team.

Features/modules

  • Marketplace: rental of GPUs/servers for containers, API, port forwarding (described in the FAQ).
  • Proof‑of‑Holding: a CLORE bonus for leasing and discounts on the service fee for holders.
  • Coin/tokenomics: capped issuance, halving, “no premine/ICO”, reward distribution.

Typical scenarios

  • Scenario 1: an ML team rents GPUs → launches a Docker environment for model training → pays for the rental time.
  • Scenario 2: a GPU owner rents out a machine → receives payment/bonuses; when participating in Proof‑of‑Holding, receives increased bonuses/discounts.
  • Scenario 3: a user holds CLORE → receives a discount on the fee (up to 50% per the website) and bonuses in the ecosystem.

Getting started (wallet/network)

  • What you need: an account/access to the clore.ai marketplace; to work with the coin — a CLORE wallet.
  • Network/chain: the CLORE network (native coin).
  • Fees: service fees (fee models are mentioned on the website) + network fees (coin transactions).

Architecture/tech (non‑AI)

  • Components: the marketplace (ordering/access to a container), GPU hosters, tenant users, the CLORE coin/network for payments/incentives, the explorer for onchain metrics.
  • Where logic runs: compute (training/render) — offchain on the rented servers; accounting of issuance/transfers — onchain on the CLORE network.

Token/economics (expanded, no forecasts)

Per the clore.ai website:

  • Max supply: 1.3 billion coins.
  • Launch: “no premine or ICO”.
  • Block distribution: 50% to miners, 40% to hosters, 10% to the team.
  • PoH: bonuses and discounts for holders (for example, up to a 50% discount on the service fee).

Governance

  • Who makes decisions: — (not confirmed by the Tier‑1 sources in this card).

Security and incidents

  • Audits/bug bounty: no public Tier‑1 links are recorded.

Project status and timeline

  • Current status: the marketplace is active; the CLORE network is active (there are live metrics in the explorer).
  • Protocol releases: GitHub Releases contains alpha releases about PoS/staking and a hybrid consensus (dev/testnet context).
  • Roadmap: https://www.clore.ai/#roadmap

Ecosystem/integrations

  • Integrations: Docker workloads; the website mentions an API and port forwarding; CEX listings are mentioned on the website (icons/links).

AI component of the project

  • What is real AI here? The project does not “do AI” as a protocol; it provides GPU infrastructure/a marketplace that is used, among other things, for training AI models (the “AI Training” use‑case on the website).
  • What is truly onchain? The native coin and the CLORE network (issuance/circulation/transactions are visible in the explorer).
  • Why is a token needed? On the website, CLORE is described as the main asset of the ecosystem: payments, bonuses and discounts (Proof‑of‑Holding), economic incentives.
  • Red flags (based on the information found): the AI part here is mainly “infrastructure for training”, not a decentralized AI protocol; “compute marketplace” must be carefully separated from “decentralized AI”.

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 medium 1
Token necessity medium 2
Evidence Tier‑1 present 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is listed here as a use‑case (AI Training), not as a separate AI protocol/roadmap.
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): the website describes the use of GPUs for AI training, but does not promise to “build an AI protocol”.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): Clore.ai does not claim its own ML/models; it provides infrastructure (GPUs) for running third‑party AI workloads.
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): on the website, AI is a “use case” of GPU rental, not AI functionality of the protocol.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): within the rubric there is no Tier‑1 “AI demo” (model/inference); there is a marketplace where one can run containers for one’s own tasks.
  • Evidence: Tier‑1 — https://clore.ai/marketplace
  • Why sufficient / why not (one line): the marketplace is an infrastructure entry point, not a demonstration of an AI component as a product.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): there are no AI quality metrics, since the project is not about models but about compute rental.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the compute part is described (Docker workloads, use‑cases), but there is no technical description of AI models/architecture, since the project does not do AI.
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): AI architecture is not within the project’s domain.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: CLORE
  • Addresses/identifiers: — (for a native coin there is no “contract”; there is a chain explorer)
  • Evidence: Tier‑1 — https://clore.cryptoscope.io/
  • Why sufficient / why not (one line): the explorer shows live blocks/transactions/issuance of the network.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: in the extracted Tier‑1 sources, onchain logic on top of the “native coin” (smart contracts/protocols) as part of the compute marketplace is not confirmed.
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): the website focuses on the offchain compute marketplace, and onchain — on the coin/issuance/payments.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the marketplace could technically work with centralized accounting; the Tier‑1 sources do not show what exactly “breaks” without the blockchain.
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): there are arguments about tokenomics/incentives, but no strict OC_3 proof.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): Clore has a native coin, CLORE.
  • Evidence: Tier‑1 — https://www.clore.ai/ ; https://clore.cryptoscope.io/
  • Why sufficient / why not (one line): the website describes the CLORE coin; the explorer shows supply/circulation.
  • 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): CLORE is used to pay for services within the ecosystem (the compute rental marketplace).
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): the website states that the service accepts CLORE and positions it as the “heart of ecosystem”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Proof‑of‑Holding gives bonuses/discounts to holders (the more you hold, the more bonuses; up to a 50% discount on the fee).
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): the website has a “Proof of holding system” section describing the incentives/discounts mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance with the token is not confirmed in the Tier‑1 sources.
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): the website talks about payments/incentives, not about governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the token is embedded in the incentives/discounts and positioned as the key payment asset, but no strict irreplaceability test is given.
  • Evidence: Tier‑1 — https://www.clore.ai/
  • Why sufficient / why not (one line): the utilities are described, but it is not proven that “it cannot be replaced with a stablecoin/fiat”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.clore.ai/ use‑cases (AI training, render), PoH incentives/discounts, max supply 1.3B, “no premine/ICO”, reward distribution
Tier‑1 https://clore.cryptoscope.io/ existence of the network: live blocks/txs, coin circulation, address count
Tier‑1 https://github.com/Clore-ai/Clore/releases development/protocol releases (alpha: PoW+PoS, cold staking, testnet context)

No comments to display

Back to top