Skip to main content

Quranium

Quranium — 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).

Quranium — an AI/Other project on the Quranium network, token (symbol: QRN).

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 Layer‑1 blockchain that, per Tier‑1 sources, is positioned as “quantum‑secure” and EVM‑compatible for deploying Solidity contracts.
  • Who it’s for: smart contract developers and teams that need an L1 with a focus on cryptographic resilience and EVM compatibility (per Tier‑1).
  • Why onchain/token: onchain — the network itself/contract execution; the role of the QRN token (payment/incentives/governance) is not confirmed by Tier‑1 sources.

How it works (very briefly)

  1. The user does: deploys an EVM contract/application or uses ecosystem applications (per the Tier‑1 description).
  2. The system does: executes EVM contracts and stores state/transactions on the L1 network.
  3. The user gets: onchain execution of logic and a verifiable state.
  4. Where the blockchain is: Quranium L1 (the network explorer is in links_*).
  5. Token role: not confirmed by Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name Quranium
Also known as (aliases) QRN
Logo (logo) ../assets/819_quranium_logo.svg
Token symbol (ticker) QRN
Category AI/Other | Infra
Primary chain (chain) Quranium
Type L1
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) —
Token (standard) native
Token contract —
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI smart contract deployment (QRemix)
Use‑case (use_case) quantum-secure EVM-compatible L1
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 3 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Per Tier‑1 sources, Quranium is positioned as a Layer‑1 blockchain with a focus on cryptographic resilience to future threats and compatibility with the EVM (the ability to deploy Solidity contracts). SLH‑DSA (hash‑based signatures; SPHINCS+) is mentioned on the website/in the materials as the cryptographic foundation.

The Tier‑1 description separately mentions application products/modules of the ecosystem: a wallet, a DEX and an AI tool for deploying smart contracts (QRemix AI). Details of the onchain mechanics of the QRN token and specific tokenomics parameters are not confirmed by Tier‑1 sources.

Features/modules

  • L1 network (EVM compatibility): deployment of Solidity contracts (claimed, Tier‑1).
  • QSafe wallet (claimed): the ecosystem wallet (Tier‑1).
  • QRemix AI (claimed): an “AI Smart Contract Deployment” tool (Tier‑1).
  • QxSwap (claimed): the ecosystem DEX module (Tier‑1).

Typical scenarios

  • Scenario 1: a developer deploys a Solidity contract on the Quranium network → gets onchain execution and state on the L1 network.
  • Scenario 2: a user uses the ecosystem wallet/DEX → transactions are reflected onchain (UX details are not confirmed by Tier‑1 sources).

Getting started (wallet/network)

  • What you need: access to the Quranium network and a wallet/infrastructure (see the Tier‑1 website/docs).
  • Network/chain: Quranium.
  • Fees: network fees on the Quranium network (parameters are not confirmed by Tier‑1 sources).

Architecture/tech (non‑AI)

  • Components: an L1 network (consensus/validators are not confirmed by Tier‑1 sources), EVM contract execution (claimed), explorer, ecosystem applications (wallet/DEX).
  • Participant roles: users, smart contract developers, network infrastructure operators.
  • Where logic runs: onchain — transactions and contract execution on L1; offchain — clients/wallets and services.
  • Dependencies: — (dependencies and requirements are not confirmed by Tier‑1 sources).

Token/economics (expanded, no forecasts)

  • Token utility: not confirmed by Tier‑1 sources.
  • Who pays fees: network users (within L1 mechanics; details are not established).
  • Where fees go: to validators/network participants (details are not established per Tier‑1).
  • Issuance/burn: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks of L1 networks (consensus/clients/validators) and risks of ecosystem applications; without public audits, conclusions are limited.

Project status and timeline

  • Current status: mainnet (based on the presence of a public explorer; status details require re‑checking).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: ecosystem applications (wallet/DEX/AI tool) are mentioned in Tier‑1 materials; integration details are not confirmed by Tier‑1 sources.
  • Partners: —.
  • Where it’s actually used: the network state and activity are observable via the explorer (see links_*).

AI component of the project

  • What is real AI here? Tier‑1 materials mention QRemix AI as an “AI Smart Contract Deployment” tool (claimed); however, no technical description/quality metrics of the AI component were found per Tier‑1 sources.
  • What is truly onchain? The Quranium L1 network (contract execution/transactions) and its state, observable via the explorer.
  • Why is a token needed? The role of the QRN token (payment/incentives/governance) is not confirmed by Tier‑1 sources.
  • Red flags (based on the information found): absence of public audits/bug bounty; insufficient data on tokenomics and the role of the token; absence of reproducible quality metrics (AI_3=0).

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 low 0
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): A Tier‑1 “AI intent/roadmap” is not identified as a separate plan.
  • Evidence: Tier‑1 — https://www.quranium.org/
  • Why sufficient / why not (one line): Tier‑1 mentions an AI tool (QRemix AI) as an ecosystem component, so we use AI_1=1 instead of “intent”.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Tier‑1 materials describe QRemix AI as an “AI Smart Contract Deployment” tool.
  • Evidence: Tier‑1 — https://www.quranium.org/
  • Why sufficient / why not (one line): Tier‑1 directly claims an AI feature (smart contract deployment via an AI tool), which is sufficient for AI_1=1.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No verifiable Tier‑1 demo/app for the AI tool was found.
  • Evidence: Tier‑1 — https://www.quranium.org/
  • Why sufficient / why not (one line): There is no confirmation of an available demo/example of the AI tool in operation per Tier‑1 sources.
  • 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 (one line): No reproducible set of quality metrics/benchmarks was found per Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The tech description/architecture of the AI tool are not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No technical specification at the architecture/version level was found per Tier‑1 sources.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Quranium
  • Addresses/identifiers: — (in this card we record the existence of the network/explorer; addresses depend on specific contracts)
  • Evidence: Tier‑1 — https://qrnscan.com/ ; https://www.quranium.org/
  • Why sufficient / why not (one line): The existence of the network is confirmed by a public explorer and a Tier‑1 description of L1.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: EVM contract execution and the state of the L1 network (claimed, Tier‑1).
  • Evidence: Tier‑1 — https://www.quranium.org/ ; https://www.quranium.org/whitepaper
  • Why sufficient / why not (one line): Tier‑1 describes EVM compatibility and deployment of Solidity contracts.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: replacing the L1 network with a regular server removes state verifiability/contract execution as a blockchain.
  • Evidence: Tier‑1 — https://www.quranium.org/ ; https://www.quranium.org/whitepaper
  • Why sufficient / why not (one line): Since the product is an L1 blockchain, onchain is a fundamental property.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a claimed token, QRN.
  • Evidence: Tier‑1 — https://www.quranium.org/
  • Why sufficient / why not (one line): Tier‑1 materials mention $QRN, but the functions of the token in the protocol are not confirmed by Tier‑1 sources.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): The use of the token as mandatory payment for the service is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of payment/fee mechanics specifically in QRN.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Mechanisms of incentives/collateral/penalties with QRN are not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no verifiable description of incentives/security via the token per Tier‑1 sources.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of a governance process with a role for QRN.
  • 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 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without confirmed utility, replaceability cannot be correctly assessed.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.quranium.org/ Tier‑1 description of the L1 network, EVM compatibility and mention of QRemix AI/QSafe/QxSwap (claimed).
Tier‑1 https://www.quranium.org/whitepaper Tier‑1 whitepaper (design/goal context).
Tier‑1 https://qrnscan.com/ Explorer of the Quranium network (onchain observability of state/transactions).
Tier‑1 — No Tier‑1 source for claim “the role of the QRN token (payment/incentives/governance) as a mandatory protocol mechanic” was found.
Tier‑2 https://coinmarketcap.com/currencies/quranium/ Token profile (for reference).
Tier‑2 https://www.coingecko.com/en/coins/quranium Token profile (for reference).