Skip to main content

Qubic

Qubic (QUBIC) — 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).

Qubic — an L1 network for smart contracts/oracles/applications, where validators (“Computors”) execute tasks and vote in a quorum. The network’s native “energy” is $QUBIC: it is used to execute smart contracts and services and is burned when used (Tier‑1 docs).

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: an L1 blockchain for smart contracts/oracles/dApps, where “Computors” execute tasks and participate in quorum votes.
  • Who it’s for: smart contract and dApp developers; participants running nodes/miners (in the project’s terminology).
  • Why onchain/token: the blockchain is the basis for execution and accounting; $QUBIC is used as “energy” for services/smart contracts and is burned, and is also issued on a schedule (Tier‑1 tokenomics).

How it works (very briefly)

  1. The user does: sends transactions/interacts with smart contracts/uses oracles.
  2. The system does: Computors execute tasks (including smart contracts), form “ticks” (blocks) and vote in a quorum.
  3. The user gets: execution of contract logic and a verifiable history on the Qubic network.
  4. Where the blockchain is: smart contracts, contract IPOs, votes/proposals and accounting on the network — onchain.
  5. Token role: $QUBIC is spent as “energy” (burn) when executing contracts/services; issuance is distributed to participants/funds according to the network rules.

Quick links: AI thesis fit

Project passport

Field Value
Project name Qubic
Also known as (aliases) QUBIC
Logo (logo) ../assets/qubic_logo.svg
Token symbol (ticker) QUBIC
Category AI/Compute | Infra
Primary chain (chain) Qubic Network
Type Appchain
Network status mainnet
Consensus (consensus) quorum of Computors (451 votes; up to 676)
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (energy for smart contracts; burn)
Max supply 200,000,000,000,000 QUBIC (cap)
Issuance inflationary + burn (halvings by schedule)
Tokenomics (tokenomics, brief) transfers feeless; QUBIC used for services is burned; emissions per epoch with halving schedule
Governance onchain (Quorum votes by Computors)
Admins/keys Arbitrator (mining parameters; can be overridden by the consensus of Computors)
Audit —
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI training tasks (mentioned; no details)
Use‑case (use_case) smart contracts + decentralized computation
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 3 / 2 / 3
Last verified 2026-02-11

General project overview

Qubic is an L1 network that, in its Tier‑1 documentation, describes its own role model: Computors (validators) and miners, as well as a decision‑making mechanism via the Quorum. In addition to transactions and smart contracts, the system description includes a “task‑based” model, where Computors perform a variety of tasks, while miners solve computational tasks that raise the Computors’ score.

Features/modules

  • Smart contracts (C++ structs): contract functions are called via transactions with the contract’s destinationPublicKey (Tier‑1 docs).
  • Quorum voting: decisions and proposals are adopted provided there is a sufficient number of Computor votes (Tier‑1).
  • Contract IPOs: a contract must go through a proposal/vote and an IPO via a Dutch auction; QUBIC spent on the IPO is burned (Tier‑1).
  • Tokenomics: $QUBIC as “energy” with burn mechanics, issuance per epoch and a halving schedule (Tier‑1).

Typical scenarios

  • Scenario 1 (user): calls a smart contract function → the contract executes on the network → the result is recorded onchain.
  • Scenario 2 (developer): prepares a contract → initiates the proposal/vote process and an IPO → the contract becomes available for calls.
  • Scenario 3 (operator): participates as a Computor/miner → receives a share of the issuance/pool payouts according to the network economy.

Getting started (wallet/network)

  • What you need: a client/wallet for the Qubic network (in the project’s terminology) and access to the network.
  • Network/chain: Qubic Network.
  • Fees: transfers on the network are claimed to be feeless; the “fee” for smart contract execution is denominated in QUBIC and is burned (Tier‑1 tokenomics).

Architecture/tech (non‑AI)

  • Participant roles: Computors (validators) and miners; the quorum of Computors participates in decision‑making.
  • Where logic runs: smart contract execution and the IPO/voting rules — on the Qubic network.
  • Dependencies: the official code as a “living whitepaper” (the Tier‑1 docs point to the GitHub core).

Token/economics (expanded, no forecasts)

  • Token utility: $QUBIC is used as “energy” for executing smart contracts/services and is “burned when used”.
  • Issuance: epoch = 7 days; the docs provide a halving schedule and a cap on circulating supply of 200 trillion QUBIC.
  • Where smart contract “fees” go: the Tier‑1 docs state that $QUBIC is burned rather than paid out to Computors.

Governance

Governance is described via the Quorum: decisions/proposals are adopted with the participation of Computors and a vote threshold (Tier‑1).

Security and incidents

  • Bug bounty: the program rules are published in the Tier‑1 docs.
  • Audits/incidents: no public Tier‑1 reports/postmortems recorded (—).

Project status and timeline

  • Current status: the network and releases are published in the official repository (GitHub Releases).
  • Roadmap: no separate roadmap page was found in Tier‑1; the release history is used as the “roadmap” (Tier‑1).

Ecosystem/integrations

  • Where to view the network state: explorer.qubic.org.

AI component of the project

  • What is real AI here? The Tier‑1 tokenomics mentions that the Arbitrator “oversees the assignment of AI training tasks”, but without a description of models/metrics/demos.
  • What is truly onchain? the Qubic network with smart contracts, contract IPOs and quorum votes.
  • Why is a token needed? $QUBIC is described as “energy” for executing contracts/services and as a unit that is burned when used; issuance and a cap are also described.
  • Red flags (based on the information found): AI‑washing (AI is mentioned as tasks, but there are no Tier‑1 artifacts on models/metrics); check where exactly the “AI training tasks” are described (which tasks/how the result is verified) and whether there are public artifacts/repositories for this.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): the Tier‑1 docs mention AI training tasks in the context of the Arbitrator role.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/
  • Why sufficient / why not (one line): this records an AI direction/applicability, but does not prove a working AI component of the protocol.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): no Tier‑1 description of specific models/algorithms/training pipeline was found.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/
  • Why sufficient / why not (one line): there is a mention of “AI training tasks”, but without technical specifics.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no public Tier‑1 demos/examples of AI tasks were found.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/
  • Why sufficient / why not (one line): the tokenomics page contains no demos/examples of AI task execution.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/
  • Why sufficient / why not (one line): AI quality metrics are not presented.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is no Tier‑1 architecture of an AI component/model versions.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/
  • Why sufficient / why not (one line): the mention of AI contains no architecture.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Qubic Network
  • Addresses/identifiers: the network’s public explorer
  • Evidence: Tier‑1 — https://explorer.qubic.org/
  • Why sufficient / why not (one line): the existence of the network and verifiable data via the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: smart contracts, proposals/votes, contract IPOs.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/smart-contracts/ ; https://docs.qubic.org/learn/ipo/
  • Why sufficient / why not (one line): onchain logic beyond “token issuance” is described.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the Qubic network the key property breaks down — trustless execution/accounting of smart contracts and votes.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/smart-contracts/
  • Why sufficient / why not (one line): the product is defined as a network for smart contracts/accounting.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the network has native $QUBIC units.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/
  • Why sufficient / why not (one line): the tokenomics page describes $QUBIC as an “energy unit”.
  • Conflict note (if any): —

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): $QUBIC is spent to execute smart contracts/services.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/
  • Why sufficient / why not (one line): it is stated directly: “fuel for executing smart contracts… burned when used”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): issuance is distributed to Computors and other destinations per epoch.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/
  • Why sufficient / why not (one line): the distribution of issuance serves as an incentive for participants.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance is described as quorum voting by Computors; the role of the token in governance is not explicitly fixed in Tier‑1.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/quorum/
  • Why sufficient / why not (one line): the document speaks of voting by Computors, but not of token‑weighted governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): in Tier‑1, $QUBIC is built into the mechanics of contract execution/IPOs and burning.
  • Evidence: Tier‑1 — https://docs.qubic.org/learn/tokenomics/ ; https://docs.qubic.org/learn/ipo/
  • Why sufficient / why not (one line): replacing it with an external asset changes the base economy (burn/IPO).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.qubic.org/learn/tokenomics/ $QUBIC as an “energy unit”, burn mechanics, cap 200T, issuance/halving schedule; mention of AI training tasks
Tier‑1 https://docs.qubic.org/learn/nodes/ the Computors/Miners roles and limits (676/451)
Tier‑1 https://docs.qubic.org/learn/quorum/ quorum voting and the role of Computors in decision‑making
Tier‑1 https://docs.qubic.org/learn/smart-contracts/ smart contracts, the proposals/IPO process, use of QUBIC
Tier‑1 https://docs.qubic.org/learn/ipo/ contract IPOs and the burning of QUBIC in the process
Tier‑1 https://docs.qubic.org/developers/bug-bounty the existence of a bug bounty program
Tier‑1 https://github.com/qubic/core/releases node software releases (changelog)
Tier‑1 https://explorer.qubic.org/ the network explorer

No comments to display

Back to top