Mainnet live · Whitepaper v1.2
↻ Updated 12 Oct 2026

AIDAG-Chain

An independent Layer-1 DAG blockchain, written from scratch in Rust, built for real-world document and institutional verification.

GHOSTDAG consensus · one native coin (AIDAG) · EVM-compatible · mainnet network id 3474 · 615 tests in v81a9bac (589 run by default, 26 manual)

MAINNET LIVE — real-time from the chain
connecting…
vertices (blocks)
—
network / chain id
—
orphans
—
genesis
—

The panel reads the mainnet node directly (/rpc/status) — these numbers are live, not static; they grow with the chain.

Audit: the independent security audit is still pending. Until it is complete, treat all components — including document verification — as pre-audit.
00

What's new

This whitepaper was realigned with the live mainnet on 22 Sep 2026. The latest changes, all deployed to both mainnet nodes:

Custody hardeningNEW · 22 Sep 2026

Daily caps and time-based rules now follow the chain clock (highest timestamp in consensus order) — back-dated vertices can no longer bypass them. Reorg recompute and fresh-node start fixed.

01

Vision

Most blockchains revolve around financial speculation. AIDAG-Chain is built for what the real economy needs: verifiable documents and institutional trust. It is not a token on another chain — it is an independent Layer-1 with its own consensus (GHOSTDAG), its own native coin (AIDAG), and its own security layer, written from scratch in Rust.

Running today and on the roadmap are marked throughout — what is live now, and where it is headed.

02

How the chain works

Classic blockchains order blocks in a single chain — a bottleneck. AIDAG-Chain uses a DAG (Directed Acyclic Graph): each unit is a vertex that can reference multiple parents, enabling parallel production and higher throughput.

GGENESISTIPSvertexeach vertex can reference multiple parents
Figure 1 — The DAG network

Every vertex links back to one or more earlier vertices, all the way to the pinned genesis (gold). The moving light shows how references flow toward the newest vertices — the tips — which new vertices build on.

Every vertex is a small, cryptographically signed unit:

VERTEXid32-byte unique idparentsone or more parent idspayloadtransaction datasignatureed25519 producer signaturetimestampcreation time
Figure 2 — Anatomy of a vertex

The id is derived from the vertex content; the signature proves who produced it. Changing any field changes the id, so history cannot be edited silently.

Classic single chainone block at a timeDAG (AIDAG-Chain)many vertices in parallel
Figure 3 — Why a DAG

A single chain accepts one block at a time and discards competitors. A DAG keeps parallel vertices and orders them deterministically with GHOSTDAG, so honest work is not wasted.

03

Technical architecture

GHOSTDAG consensus selects a blue set among parallel vertices to produce a total order — embracing parallelism instead of fighting forks. On mainnet, a PoA committee weighting ensures only committee vertices add blue-work, which blocks blue-work inflation. Signatures use ed25519; hashing uses blake3.

ApplicationsExplorer · Document verification · KUBRA AIInterfacesEthereum eth_* JSON-RPC (MetaMask, ethers.js) · REST status / verify endpointsExecutionAVM (EVM-compatible, revm) + native registries: records, institutions, balancesConsensusGHOSTDAG total order · PoA committee weighting · deterministic state from orderNetwork & storagelibp2p gossip + pull-sync · signed vertices (ed25519, blake3) · disk persistence
Figure 4 — Architecture layers

Applications talk to the chain through standard Ethereum JSON-RPC. Execution combines an EVM-compatible machine (AVM, built on revm) with native registries. All state is derived deterministically from the consensus order, so every node that sees the same vertices reaches the same state.

Live on mainnet

Independent L1, GHOSTDAG, the AIDAG ledger, transfers with double-spend and replay protection, EVM-compatible AVM (MetaMask, Solidity / ERC-20), document and institution registries, disk persistence.

Determinism, proven

State is recomputed from the consensus order, not the arrival order. Before every consensus change, the real mainnet history is replayed with the old and the new code — the resulting state must match exactly.

04

Real-world use — by scenario

The real-world capability is first-class: document verification and institutional identity are native transaction types, not bolted-on contracts.

Institutionissues a documentHash + signblake3 + ed25519On-chaintx type 1 (RecordRegistry)Verifyrecompute hash, confirmtamper-evident, no trusted central server required
Figure 5 — Document verification flow

Only the document's fingerprint (hash) goes on-chain; the document itself never leaves the owner's device. If a single character changes, the fingerprint no longer matches and the forgery is detected.

Scenario · Diploma

A university records a diploma fingerprint on-chain (tx type 1). Any employer recomputes the hash and confirms authenticity in seconds — the fake-credential problem, solved without a trusted middleman.

Scenario · Bill of lading

A shipping company anchors a cargo document; forgery, double-selling, and loss become detectable. The maritime sector gains a verifiable, tamper-evident record.

Scenario · Institutional identity

Institutions hold a verifiable on-chain identity with a strict government/private distinction (tx type 5). Anyone can confirm a document's true source.

Scenario · Programmable (roadmap)

Payment releases when cargo reaches the destination port. A document becomes valid only when the authorized institution signs. Institutional logic, on-chain via the EVM layer.

Live on mainnet as a pilot: document verification (aidag-chain.com/belge) and institutional identity. Real adoption requires customers, legal frameworks, and field work — the next phase.

05

AIDAG & tokenomics

AIDAG is the only native coin of AIDAG-Chain. Supply: 21,000,000 (no mining, sealed at genesis). Staking and Kalkan collateral: infrastructure ready, not yet active.

Gas: AIDAG's gas role is active on testnet; the mainnet transition is planned.

AIDAG · 21,000,000 fixed supply · sealed at genesisTreasury · 25%unlockedEcosystem · 22%12-month linearLiquidity · 15%2-year linearFounder · 13%6-mo cliff + 24 moCommunity · 12%6-month linearSale pool (escrow) · 8%locked · terms via official channelsEarly supporters · 5%6-mo cliff + 24 mo
Figure 6 — AIDAG genesis distribution

These seven slices are fixed in the mainnet genesis and can never exceed 21,000,000 in total. Each colour shows its share of supply; the line beneath each label shows how that slice unlocks over time.

Token sale: in preparation — via RWA.inc and aidag-chain.com; the date will be announced through official channels.

06

Roadmap & progress

✓EVM layer
AVM (revm), MetaMask
✓MAINNET
genesis 26 Jul 2026 · id 3474
✓Hardening
custody + consensus fixes (Sep 2026)
Token sale
in preparation · RWA.inc
Audit
independent — pending
Listing
announced via official channels
Figure 7 — Where we are

Green steps are done and live; the glowing step is the mainnet (Mainnet genesis: 26 July 2026, network id 3474). Grey steps are still ahead: the token sale (in preparation), the independent audit and listing — announced through official channels.

donein progresspending

Mainnet is live and currently runs on nodes operated by the core team. Multi-node consensus has been tested with a remote node over the public internet. Onboarding independent node operators is on the roadmap.

07

Live now

Mainnet

Network id 3474, pinned genesis b82345008ae109d8, public JSON-RPC and explorer at aidag-chain.com. Mainnet is live and currently runs on nodes operated by the core team. Multi-node consensus has been tested with a remote node over the public internet. Onboarding independent node operators is on the roadmap.

MetaMask transfers

AIDAG moves between accounts on-chain (EIP-1559 + legacy), visible in the explorer.

Token sale

In preparation — via RWA.inc and aidag-chain.com; the date will be announced through official channels.

KUBRA

Under maintenance — coming soon. The network's AI assistant, built to answer from verified sources and verify document hashes on-chain.