Skip to main content

Idena

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

Idena — an L1 blockchain project about Sybil‑resistant identity (Proof‑of‑Person consensus) with the native coin iDNA.

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 public blockchain that attempts to provably maintain “one person = one vote” via Proof‑of‑Person and synchronous checks (Turing test) without collecting personal data.
  • Who it’s for: network participants (validators/miners in the project’s terms) and developers/applications that need Sybil‑resistant identity.
  • Why onchain/token: onchain is needed for consensus and the identity registry; iDNA is the native coin of the network (used for fees/stake and the protocol’s economic mechanisms, see Tier‑1 economics).

How it works (very briefly)

  1. The user does: runs a node and passes the network checks to obtain/maintain a cryptoidentity (per the documentation).
  2. The system does: conducts a synchronous Turing test for participants and updates the identity state in the network.
  3. The user gets: identity status and participation in the network consensus (in the project’s terms).
  4. Where the blockchain is: the identity registry, consensus and network events — onchain in the Idena network.
  5. Token role: iDNA is the native coin of the network.

Quick links: AI thesis fit

Project passport

Field Value
Project name Idena
Also known as (aliases) iDNA; Idena Network
Logo (logo) ../assets/318_idena_logo.svg
Token symbol (ticker) iDNA
Category Infra
Primary chain (chain) Idena
Type Appchain
Network status mainnet
Consensus (consensus) Proof-of-Person (PoP)
Launch date (launch_date) 2018
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (payments + staking)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) iDNA is the native coin of the network; Tier‑1 economics lists a premint of 36,000,000 iDNA and a daily minting cap (51,480 iDNA/day), as well as the fee model (90% fees burn).
Governance —
Admins/keys —
Audit —
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) Sybil-resistant identity
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 3 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

Idena is an open‑source blockchain project (per the documentation: started in October 2018) that builds identity at the level of “one person = one vote” via Proof‑of‑Person consensus. The whitepaper section of the documentation states that each node is linked to a cryptoidentity and participation is confirmed via a synchronous Turing test without collecting PII.

Features/modules

  • Proof‑of‑Person consensus: links participation in consensus to a cryptoidentity.
  • Synchronous checks (Turing test): a mechanism for confirming the uniqueness/“humanness” of participants (per the whitepaper).
  • Open source: the code and releases are available in the official organization on GitHub.

Typical scenarios

  • Scenario 1: a network participant runs a node and passes the checks → obtains/maintains a cryptoidentity and the right to participate (per the documentation).
  • Scenario 2: a developer/project uses the network as a source of Sybil‑resistant identity → relies on the publicly verifiable identity state (as the idea/purpose of the network).

Getting started (wallet/network)

  • What you need: an Idena client/node (see GitHub/releases).
  • Network/chain: Idena mainnet.
  • Fees: network fees in iDNA (details — in the project documentation).

Architecture/tech (non‑AI)

  • Components: the L1 network + participants’ nodes + network explorer/statistics (scan.idena.io).
  • Participant roles: nodes/participants with a cryptoidentity (in the whitepaper’s terms).
  • Where logic runs: consensus/identity registry — onchain.

Token/economics (expanded, no forecasts)

  • Network token: iDNA — the native coin of the network.
  • Token utility (Tier‑1): transaction fees (with a calculation formula; part of the fees is burned), staking rewards and other economic funds/distributions (see economics).

Governance

  • Who makes decisions: —.
  • Updates/changes: via client/protocol releases (see GitHub Releases).

Security and incidents

  • Audits: —.
  • Bug bounty: links_* lists a contribute section (the bounty format/terms require re‑checking).
  • Incidents: —.
  • Threat model: risks of Sybil attacks and of the correctness of the checking mechanism; details — in the whitepaper/documentation.

Project status and timeline

  • Current status: mainnet.
  • Releases: published in the GitHub Releases of the official client.
  • Roadmap: published in the documentation’s whitepaper section.

Ecosystem/integrations

  • Integrations: —.
  • Where it’s actually used: the network/participant state and statistics are available in the official explorer/dashboards (scan.idena.io).

AI component of the project

  • What is real AI here? In Tier‑1 sources the project is described as blockchain identity (Proof‑of‑Person); an AI component as part of the product is not claimed.
  • What is truly onchain? Consensus/identity registry and the state of the Idena network.
  • Why is a token needed? iDNA is the native coin of the network; the detailed role of the token in the protocol requires a separate Tier‑1 extraction.
  • Red flags (based on the information found): —.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality absent 0
Onchain necessity high 3
Token necessity low 2
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI intent is not identified in the project’s Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): In the whitepaper section AI is described only as an external risk (deepfakes), not as a component of the product.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): An AI component of the product is not described.
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): The Tier‑1 source contains no description of “what the AI does” as part of the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): There is no demo of an AI part (an AI part is not claimed).
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): No claimed AI component.
  • 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.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): AI metrics are not applicable (no AI component).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of an AI component is not applicable (no AI component).
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): No AI component.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Idena
  • Addresses/identifiers: the native coin iDNA; network explorer/statistics — scan.idena.io
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/ ; https://scan.idena.io/
  • Why sufficient / why not (one line): The Tier‑1 whitepaper describes the network and the native coin; the official explorer provides onchain verification of the network state.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: Proof‑of‑Person consensus and the network’s identity registry (cryptoidentity).
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): The whitepaper describes onchain identity/consensus logic that is broader than “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without public consensus and an onchain identity registry, the key property of a “permissionless and verifiable registry” for Sybil‑resistant identity is lost.
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): The whitepaper explicitly formulates the requirements “global/verifiable/permissionless/decentralized”.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a native coin, iDNA.
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): The whitepaper section explicitly lists iDNA as the native coin.
  • 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): iDNA is used to pay transaction fees in the network.
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/economics#transaction-fees
  • Why sufficient / why not (one line): Tier‑1 economics describes the fee calculation and the gasPrice/txFee parameters, which confirms the payment use‑case.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Tier‑1 economics describes staking rewards and mining penalties (penalties paid via burn coins), as well as the distribution of rewards across funds.
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/economics
  • Why sufficient / why not (one line): Reward/stake mechanics and penalties are described as part of the network’s economic model.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of iDNA for governance is not established per Tier‑1 in this card.
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): The governance mechanics are not described in the extracted Tier‑1 text.
  • 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 established per Tier‑1 in this card.
  • Evidence: Tier‑1 — https://docs.idena.io/docs/wp/summary/
  • Why sufficient / why not (one line): Insufficient data for a conclusion.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.idena.io/docs/wp/summary/ Description of Idena, Proof‑of‑Person consensus and the fact that iDNA is the native coin.
Tier‑1 https://docs.idena.io/docs/wp/economics Tier‑1 economics/tokenomics: premint, minting cap, reward distribution, fees, iDNA utility.
Tier‑1 https://docs.idena.io/docs/wp/economics#transaction-fees The formula and principles for calculating transaction fees; 90% fees burn (the economic role of iDNA).
Tier‑1 https://scan.idena.io/ Tier‑1 onchain context: the official network explorer/statistics.
Tier‑1 https://github.com/idena-network/idena-go/releases Releases of the official client (life cycle and updates).
Tier‑1 https://www.idena.io/contribute The Contribute section (including on vulnerability reports/rewards — the format requires re‑checking).

No comments to display

Back to top