Skip to main content

Flux

Flux (FLUX) — 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).

Flux — an AI/Compute | Infra project: its own L1 blockchain and an ecosystem of decentralized cloud services (FluxCloud/FluxEdge/FluxNodes) + a set of AI products (FluxAI). Token: FLUX (native; there is also an ERC‑20 parallel asset).

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 decentralized cloud and compute marketplace for running applications and AI workloads on distributed nodes.
  • Who it’s for: developers/teams that need cheap and censorship‑resistant infrastructure; node operators/hardware providers.
  • Why onchain/token: the token is needed as the network currency and the incentive mechanism (collateral for nodes, rewards/fees) and for payment for cloud services (per the MiCA whitepaper).
  • What you can actually touch (Tier‑1): cloud.runonflux.com (deployment/dashboards), console.fluxedge.ai (compute marketplace), the FluxAI products (ai.runonflux.com).

How it works (very briefly)

  1. The user does: deploys an application/container in FluxCloud or connects to the FluxEdge compute market; an operator connects a FluxNode.
  2. The system does: distributes compute/hosting across independent nodes; the network provides accounting/incentives via consensus and rewards.
  3. The user gets: infrastructure for applications/AI workloads (GPU/CPU), scaling and fault tolerance (as claimed).
  4. Where the blockchain is: the Flux blockchain records the network rules and issuance/rewards (PoUW v2) and is used for onchain governance/economics (per the MiCA whitepaper).
  5. Token role: payment for services, collateral for FluxNodes, rewards and governance (Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name Flux
Also known as (aliases) ZEL | ZelCash | RunOnFlux | FLUX
Logo (logo) ../assets/50_zel_logo.svg
Token symbol (ticker) FLUX
Category AI/Compute | Infra
Primary chain (chain) Flux
Type Appchain
Network status mainnet
Consensus (consensus) PoW (PoUW v2)
Launch date (launch_date) 2018
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (payments + staking + governance)
Max supply 440,000,000
Issuance PoW emissions (PoUW v2)
Tokenomics (tokenomics, brief) token for paying for FluxOS/Cloud, collateral for FluxNodes and governance (MiCA)
Governance community governance (XDAO; MiCA)
Admins/keys —
Audit yes (Halborn 2025)
Bug bounty yes (Flux bug bounty)
Team (team) InFlux Technologies Ltd. (MiCA)
Funding (investors/funding) —
AI component (ai_component) GPU/compute for AI/ML workloads
Use‑case (use_case) decentralized cloud + GPU marketplace
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 3 / token_score 3 / evidence_score 2
Last verified 2026-02-11

General project overview

Flux is an ecosystem around its own blockchain (Flux) and a set of cloud services that run on a distributed network of independent nodes (FluxNodes). Per Tier‑1 sources, the project is positioned as decentralized cloud infrastructure: deployment and management of applications (FluxCloud/FluxOS), a compute marketplace with an emphasis on GPU/AI workloads (FluxEdge), as well as separate AI products (FluxAI).

Features/modules

  • Flux Blockchain: the base L1, economics/accounting, onchain governance and parallel assets (MiCA).
  • FluxNodes: three node tiers (Cumulus/Nimbus/Stratus) with collateral and rewards; PoUW v2 (Tier‑1).
  • FluxCloud / FluxOS: container deployment and application management via dashboards/interfaces (Tier‑1).
  • FluxEdge: a compute marketplace, including for AI workloads; Kubernetes integration is claimed (Tier‑1).
  • FluxAI: a private set of AI services (chat/documents/images/agents) based on open‑source LLMs (Tier‑1).

Typical scenarios

  • Scenario 1 (app deployment): a developer registers/deploys an application in FluxCloud → gets hosting/scaling on the distributed network of nodes.
  • Scenario 2 (compute for AI): a team connects to FluxEdge/uses GPU resources → runs AI workloads on capacity provided by providers.
  • Scenario 3 (AI products): a user/team uses FluxAI (chat/document intelligence/image generation) → gets a “private” AI toolkit (as claimed by Tier‑1).

Getting started (wallet/network)

  • What you need: for the products — an account in the respective web interfaces (FluxCloud/FluxAI/FluxEdge); for onchain operations — a wallet/address on the Flux network.
  • Network/chain: the primary network is Flux (mainnet); “parallel assets” exist on other networks (MiCA).
  • Fees: onchain — Flux network fees (and/or fees on the parallel asset networks); product — payments for services (MiCA) and the cost of resources/subscriptions (per the interfaces).

Architecture/tech (non‑AI)

  • Components: the Flux blockchain (L1), FluxOS/FluxCloud (orchestration/deployment), FluxNodes (execution/storage infrastructure), FluxEdge (compute marketplace), web portals and API (Tier‑1).
  • Participant roles: cloud developers/users; FluxNodes operators (with collateral) and participants receiving block rewards (FluxNodes page; MiCA).
  • Where logic runs: onchain — consensus/accounting/issuance/transactions and governance; offchain — the actual compute/hosting on nodes and the operation of the web portals.
  • Dependencies: GitHub integrations (Deploy with Git), third‑party networks for parallel assets/bridges (MiCA mentions interoperability via parallel assets and the Fusion bridge).

Token/economics (expanded, no forecasts)

  • Token utility: payment for cloud services on FluxOS/FluxCloud, participation in governance, collateral for FluxNodes (MiCA).
  • Protocol necessity drivers: without FLUX one cannot run a node (collateral) or participate in the claimed payment/governance mechanics (MiCA).
  • Who pays fees: users of the Flux network (tx fees) and users of the services/cloud (payments for services; MiCA).
  • Where fees go: to miners/node operators as part of the incentive model (MiCA; the FluxNodes page describes the distribution of block rewards).
  • Issuance/burn: PoW/PoUW emissions; max supply 440,000,000 (MiCA); PoUW v2 describes updated issuance parameters/reward pools (FluxNodes page).
  • Security/incentive mechanisms: collateral (for FluxNodes tiers) + per‑block rewards; risks — economic parameters and centralization of large operators (Tier‑1).
  • Distribution and token issuance schedule: all tokens are obtained via block rewards; MiCA states that the remaining unissued tokens are “locked until their respective blocks are mined”, and a reserve of 23,520,000 via governance is also mentioned.
  • Treasury: some tokens are held for ecosystem purposes/liquidity (MiCA); treasury management details were not extracted.

Governance

  • Who makes decisions: community governance via XDAO is claimed (MiCA).
  • How protocol parameters change: via governance processes/proposals reflected in XDAO (per MiCA, without a detailed procedural part).
  • Where decisions are discussed/made: — (specific venues/procedures not extracted).
  • Keys/multisig: — (not established per Tier‑1).

Security and incidents

  • Audits: there is a public audit report (Halborn 2025; link in links_*).
  • Bug bounty: yes (Flux Bug Bounty Program; Tier‑1).
  • Incidents: — (no public post‑mortems extracted from the reviewed sources).
  • Threat model: quality/honesty of compute providers, web panel and supply‑chain risks, economic attacks via node concentration, vulnerabilities of containerization/orchestration and access keys.

Project status and timeline

  • Current status: a mainnet ecosystem (Flux blockchain + FluxNodes + cloud interfaces available; Tier‑1).
  • Key releases/milestones: the PoUW v2 soft fork (FluxNodes page); an active product line FluxCloud/FluxEdge/FluxAI (Tier‑1).
  • Roadmap: timeline/roadmap on the Flux website (Tier‑1: runonflux.com/timeline/).

Ecosystem/integrations

  • Integrations: GitHub deployment (FluxCloud “Deploy with Git”), Kubernetes setups (FluxEdge), parallel assets/bridges (MiCA), product web dashboards.
  • Partners: the FluxNodes/FluxCloud pages list partners/brands, but legal details were not verified.
  • Where it’s actually used: as a platform for deploying applications and as a compute marketplace for GPU/AI workloads; also as an AI suite (FluxAI) with a web interface.

AI component of the project

  • What is real AI here? Flux publishes a set of AI products (FluxAI: chat/documents/images/agents) and positions FluxEdge/FluxCloud as infrastructure for AI workloads and GPU access (Tier‑1).
  • What is truly onchain? Flux is its own L1 with PoUW and a node economy; MiCA describes that the blockchain supports onchain governance and the ecosystem economy.
  • Why is a token needed? Per MiCA, the FLUX token is used to pay for cloud services, as collateral for FluxNodes and for participation in governance.
  • Red flags (based on the information found): AI‑washing (no Tier‑1 model quality metrics; the AI part is product/infra, not an “own” model), onchain‑washing (part of the service logic is inevitably offchain), token‑washing (a subscription model is possible in a number of services; it is important to check where FLUX is mandatory); what to double‑check: the actual terms of paying for FluxCloud/FluxEdge with the token, SLA/market parameters, the privacy boundaries of FluxAI.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI relevance is confirmed not only by intent but by the existence of public AI products (FluxAI) and a compute layer for AI workloads.
  • Evidence: Tier‑1 — https://runonflux.com/flux-ai/, https://ai.runonflux.com/
  • Why sufficient / why not (one line): the intent flag is not needed, since there are verifiable product artifacts (AI_2=1).
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): FluxAI provides AI functions (chat/document intelligence/images/agents), and FluxEdge/FluxCloud are positioned as infrastructure for AI workloads on GPUs.
  • Evidence: Tier‑1 — https://runonflux.com/flux-ai/, https://runonflux.com/fluxedge/, https://runonflux.com/fluxcloud/
  • Why sufficient / why not (one line): Tier‑1 describes specific AI products and the purpose of the compute layer for AI.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): public UI artifacts are available: the FluxAI web application, the FluxCloud dashboard and the FluxEdge console.
  • Evidence: Tier‑1 — https://ai.runonflux.com/, https://cloud.runonflux.com/, https://console.fluxedge.ai/
  • Why sufficient / why not (one line): this is “what you can touch” and reproducible entry points into the product.
  • Conflict note (if any): some features require a login/plan.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://runonflux.com/flux-ai/
  • Why sufficient / why not (one line): Tier‑1 has no published model quality metrics/benchmarks.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): there is a Tier‑1 technical description of the ecosystem (Flux blockchain/FluxOS/FluxNodes/FluxEdge) and official docs/repositories.
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/, https://docs.runonflux.com/, https://github.com/runonflux
  • Why sufficient / why not (one line): MiCA and the docs provide architecture‑level technical context + dev artifacts.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Flux (L1); also a parallel asset on Ethereum
  • Addresses/identifiers: native coin FLUX (no contract); ERC‑20: 0x720cd16b011b987da3518fbf38c3071d4f0d1495
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/, https://etherscan.io/token/0x720cd16b011b987da3518fbf38c3071d4f0d1495
  • Why sufficient / why not (one line): Tier‑1 confirms the existence of its own blockchain and the identifier of the parallel asset.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: consensus/issuance/accounting of transactions and reward mechanisms; onchain governance/ecosystem economics (MiCA).
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/, https://runonflux.com/fluxnodes/
  • Why sufficient / why not (one line): Tier‑1 describes that the blockchain supports the economy and governance, not just a “token on someone else’s network”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the Flux L1, the consensus/issuance/reward model rules and governance, which Tier‑1 describes as the foundation of the ecosystem, break down.
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/
  • Why sufficient / why not (one line): the project is an appchain ecosystem where the L1 is the “core” of incentives and governance.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token/coin, FLUX (native on Flux), and parallel assets on other networks.
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/
  • Why sufficient / why not (one line): the existence of the token is confirmed in MiCA.
  • 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): FLUX is used for payment/deployment and management of applications/services on FluxOS (decentralized cloud services).
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/
  • Why sufficient / why not (one line): in MiCA this is directly listed as a utility of the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): FLUX is needed as collateral for FluxNodes and as part of the incentive model (block rewards are distributed among the tiers).
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/, https://runonflux.com/fluxnodes/
  • Why sufficient / why not (one line): both Tier‑1 sources describe collateral and reward distribution.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the token is used for participation in governance (MiCA mentions community governance via XDAO).
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/
  • Why sufficient / why not (one line): governance is directly listed as a utility of 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 confirmed by Tier‑1: it is embedded in payments/collateral/governance and in the L1 economy.
  • Evidence: Tier‑1 — https://runonflux.com/flux-token-mica-whitepaper/
  • Why sufficient / why not (one line): without a comparison with alternatives and given the L1 economy, we record 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://runonflux.com/flux-token-mica-whitepaper/ Tier‑1: purpose of the token (payments/collateral/governance), max supply 440M, description of the Flux blockchain/FluxOS/FluxNodes and the economics.
Tier‑1 https://runonflux.com/fluxnodes/ Tier‑1: PoUW v2, FluxNodes tiers, collateral and distribution of block rewards, the claim that FluxNodes participate in block production/validation.
Tier‑1 https://runonflux.com/fluxcloud/ Tier‑1: FluxCloud as the product layer for deploying/managing applications and the cost/mechanics of deployment (including Deploy with Git).
Tier‑1 https://runonflux.com/fluxedge/ Tier‑1: FluxEdge as a compute marketplace for GPU/AI workloads, Kubernetes integration, links to the console/docs.
Tier‑1 https://runonflux.com/flux-ai/ Tier‑1: the FluxAI suite (FluxGPT/Agents/FluxONE/FluxINTEL/FluxGrader), claims about privacy/in‑memory.
Tier‑1 https://ai.runonflux.com/ Tier‑1: the available FluxAI web interface (product artifact) and versions (v0.5.3 in the UI).
Tier‑1 https://cloud.runonflux.com/ Tier‑1: the FluxCloud dashboard (product artifact).
Tier‑1 https://console.fluxedge.ai/ Tier‑1: the FluxEdge console (product artifact).
Tier‑1 https://runonflux.com/bug-bounty/ Tier‑1: the bug bounty program and payouts (in FLUX), scope (blockchain/nodes/FluxOS/website/Zelcore).
Tier‑1 https://etherscan.io/token/0x720cd16b011b987da3518fbf38c3071d4f0d1495 Tier‑1: identifier of the FLUX ERC‑20 parallel asset on Ethereum (contract/address).
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top