Skip to main content

dKargo

dKargo (DKA) — 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).

dKargo — an Infra project: an EVM‑compatible Layer 3 blockchain (built on Arbitrum L2), positioned as a network/platform for logistics Web3 services. Token: DKA (ERC‑20 on Ethereum; there are also ERC‑20 versions for the L2/L3 environment).

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 EVM‑compatible Layer‑3 blockchain (built on Arbitrum L2), a “blockchain designed for logistics”.
  • Who it’s for: dApp developers/integrators in logistics and infrastructure operators (nodes/validators).
  • Why onchain/token: the network provides onchain execution of smart contracts and verifiability of state; the DKA token is used as the utility asset of the ecosystem (payments/rewards/collateral/fees/governance — per Tier‑1).

How it works (very briefly)

  1. The user does: connects a wallet to the dKargo network (for example, the Warehouse testnet), deploys/calls a smart contract as in a regular EVM stack.
  2. The system does: executes transactions/contracts on the L3, while the connection to L2/L1 is provided through a set of core contracts (rollup/inbox/outbox/bridge, etc.) and gateways/routers (Tier‑1).
  3. The user gets: onchain state/logs and the ability to build applications on top of the dKargo network (including logistics scenarios).
  4. Where the blockchain is: transactions/smart contracts and some of the infrastructure contracts (rollup/bridge/gateway) are onchain; the addresses are published (Tier‑1).
  5. Token role: DKA is the utility token of the ecosystem: settlements/rewards/collateral and participation in governance; in the documentation it is also listed as the currency symbol of the network (Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name dKargo
Also known as (aliases) DKA
Logo (logo) ../assets/72_dkargo_logo.webp
Token symbol (ticker) DKA
Category Infra
Primary chain (chain) dKargo
Type EVM
Network status testnet
Consensus (consensus) L3 (Arbitrum Orbit on Ethereum)
Launch date (launch_date) 2020-05
Project status (status) active
Token (standard) ERC-20
Token contract 0x5dc60C4D5e75D22588FA17fFEB90A63E535efCE0
Token model (token_type) utility (payments + staking + governance)
Max supply 5,000,000,000
Issuance capped
Tokenomics (tokenomics, brief) total supply 5B (minted 2020‑05); the whitepaper has a plan of additional issuance/unlocks until 2025‑06.
Governance DAO
Admins/keys —
Audit —
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) L3 blockchain for logistics
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 3 / evidence_score 3
Last verified 2026-02-11

General project overview

dKargo describes itself as a “blockchain designed for logistics” and as an EVM‑compatible Layer 3 blockchain built on Arbitrum (Layer 2). At the product level this is an infrastructure network: the documentation focuses on nodes/validators, RPC, bridges/gateways, validator staking and smart contract deployment (Remix/Hardhat/Foundry).

From the DecAIHub perspective this is not an AI project: per Tier‑1 sources, dKargo is blockchain infrastructure for logistics scenarios, without a claimed “AI core”/models/agents as a base component.

Features/modules

  • dKargo Chain (L3, EVM compatibility): contract deployment/calls, web3 integrations, a Hardhat devflow (Tier‑1).
  • Nodes and roles: full/archive/validator node; validator operations (staking/unstaking/claim) (Tier‑1).
  • Bridging/Gateway: sections on ERC‑20 bridging and a list of core contracts (rollup/inbox/outbox/bridge/gateway/router, etc.) (Tier‑1).

Typical scenarios

  • Scenario 1 (dApp/dev): connects MetaMask to the Warehouse testnet → deploys a contract (Remix/Hardhat) → checks transactions in the dScanner block explorer (Tier‑1).
  • Scenario 2 (validator): sets up a validator node → runs the staking script from the official repository → participates in the verification of rollup batches (Tier‑1).
  • Scenario 3 (infra/integration): uses the published addresses of the core contracts and gateways/routers for bridging/operations (Tier‑1).

Getting started (wallet/network)

  • What you need: an EVM wallet (for example, MetaMask), an RPC endpoint.
  • Network/chain: for testing — Warehouse (testnet): RPC rpc.warehouse.dkargo.io, chain id 61022448, explorer warehouse.dscanner.io (Tier‑1).
  • Fees: onchain operations require gas; for staking, a validator needs funds for transactions (Tier‑1).

Architecture/tech (non‑AI)

  • Components: the L3 network + a set of core contracts (rollup/inbox/outbox/bridge, etc.) and a gateway/router for bridging (Tier‑1).
  • Participant roles: users/contract developers; validators (verification of rollup batches); node operators (Tier‑1).
  • Where logic runs: dApp business logic — in EVM contracts on the dKargo network; the infrastructure logic of the L3/L2 connection — via the core contracts (Tier‑1).
  • Dependencies: Arbitrum L2 as the base layer; RPC/explorer; bridging contracts (Tier‑1).

Token/economics (expanded, no forecasts)

  • Token utility: in the whitepaper, DKA is described as the “currency” of the ecosystem: rewards for services, payment for data usage, collateral for execution guarantees, as well as the network fee for contract execution and participation in governance (Tier‑1).
  • Who pays fees: users making transactions/executing contracts (the network fee in DKA — per Tier‑1).
  • Issuance: total supply DKA = 5,000,000,000; it is stated that no additional supply is planned (Tier‑1).
  • Distribution: the whitepaper describes the distribution shares (token sale/marketing/reserve/ecosystem/partners/team&advisors) (Tier‑1).
  • Circulation plan: the whitepaper specifies the planned dynamics until 2025‑06 (Tier‑1).

Governance

  • Who makes decisions: the whitepaper describes the dKargo DAO; at the same time, some powers may rest with a governance committee (Tier‑1).
  • Process: proposal → community discussion → committee review → execution/monitoring (Tier‑1).
  • Keys/multisig: — (not established per Tier‑1).

Security and incidents

  • Audits: — (not established per Tier‑1).
  • Bug bounty: there is a public program (Tier‑1).
  • Incidents: —.
  • Threat model: risks of L3/L2 bridging and the core contracts, risks of the validator infrastructure and bugs in nodes/scripts, risks of faucet/deposit‑withdrawal exploits (mentioned in the bug bounty criteria) (Tier‑1).

Project status and timeline

  • Current status: there is a Warehouse testnet; the mainnet is mentioned in the documentation as “scheduled for public release in 2025” (Tier‑1).
  • Roadmap: there is a separate roadmap page on the website (Tier‑1).

Ecosystem/integrations

  • Integrations: MetaMask, standard EVM tooling (Hardhat/Remix/Foundry), the dScanner explorer, bridging contracts (Tier‑1).
  • Partners: —.
  • Where it’s actually used: developer guides (deploy contract) and validator operations (staking scripts) (Tier‑1).

AI component of the project

  • What is real AI here? Per Tier‑1 sources, dKargo is a blockchain platform for logistics; an AI component (models/agents/metrics) as part of the base product is not described in Tier‑1.
  • What is truly onchain? The L3 network (EVM), the bridging/core contracts (rollup/inbox/outbox/bridge) and the DKA token contracts; the addresses are published (Tier‑1).
  • Why is a token needed? In the whitepaper, DKA is described as a utility token: payments/rewards, collateral, network fees, participation in governance (Tier‑1).
  • Red flags (based on the information found): AI‑washing — low (the project is not positioned as an AI core in Tier‑1); onchain‑washing — low (there is an L3 network and core contracts); token‑washing — low/medium (the token’s functions are described broadly, but without onchain usage metrics; the actual role of DKA in the current testnet/mainnet needs to be re‑checked).

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 high 3
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 roadmap/declaration of AI intent was found.
  • Evidence: Tier‑1 — https://docs.dkargo.io/docs2-eng
  • Why sufficient / why not (one line): Tier‑1 describes an L3 blockchain for logistics, without an AI plan as a separate direction.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): Tier‑1 does not describe the product as containing AI models/agents/inference as a protocol function.
  • Evidence: Tier‑1 — https://docs.dkargo.io/docs2-eng
  • Why sufficient / why not (one line): the descriptions concern L3/EVM/nodes/staking/bridges, not AI functions.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): there are no AI demos/guides in Tier‑1; there are only developer guides on the network/contracts.
  • Evidence: Tier‑1 — https://docs.dkargo.io/docs2-eng/deploy-contract/how-to-deploy-a-contract
  • Why sufficient / why not (one line): this is a demo of the network/smart contracts, but not of an 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.dkargo.io/docs2-eng
  • Why sufficient / why not (one line): Tier‑1 contains no AI quality metrics.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is a technical description of the network/nodes/bridges, but not of an AI module (there is no AI module in Tier‑1).
  • Evidence: Tier‑1 — https://docs.dkargo.io/docs2-eng
  • Why sufficient / why not (one line): AI technical descriptions are absent.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: dKargo (L3; Warehouse testnet / mainnet — per the docs).
  • Addresses/identifiers: chain id Warehouse 61022448; the core contracts (rollup/inbox/outbox/bridge, etc.) and the DKA tokens (L1/L2) are published (Tier‑1).
  • Evidence: Tier‑1 — https://docs.dkargo.io/docs2-eng/contract-address/contract-address-list , https://docs.dkargo.io/docs2-eng/wallet-setup/adding-the-dkargo-network
  • Why sufficient / why not (one line): there are published network identifiers and core contract addresses.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the L3 network and the infrastructure core contracts (rollup/inbox/outbox/bridge/gateway/router), plus users’ smart contracts (Tier‑1).
  • Evidence: Tier‑1 — https://docs.dkargo.io/docs2-eng , https://docs.dkargo.io/docs2-eng/contract-address/contract-address-list
  • Why sufficient / why not (one line): the onchain logic is the network/contracts themselves, not “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the blockchain/contracts, onchain execution and the verifiability of the network state and bridging infrastructure disappear; the product = a blockchain network (Tier‑1).
  • Evidence: Tier‑1 — https://docs.dkargo.io/docs2-eng
  • Why sufficient / why not (one line): Tier‑1 directly describes dKargo as an L3 blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, DKA (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x5dc60C4D5e75D22588FA17fFEB90A63E535efCE0
  • Why sufficient / why not (one line): the explorer records the DKA ERC‑20 contract and the max total supply.
  • 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): DKA is described as a means of settlement/payment in the ecosystem and as the network fee for smart contract execution.
  • Evidence: Tier‑1 — https://whitepaper.dkargo.io/platform-overview/tokenomics
  • Why sufficient / why not (one line): the whitepaper explicitly mentions “payment” and “network fee”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): in the whitepaper, DKA is mentioned as collateral for execution guarantees and as a means of rewards; validators must stake assets to participate in rollup verification.
  • Evidence: Tier‑1 — https://whitepaper.dkargo.io/platform-overview/tokenomics , https://docs.dkargo.io/docs2-eng/validator-operations/staking
  • Why sufficient / why not (one line): there are Tier‑1 statements about collateral/rewards and about staking for validators (asset‑level; the token specifics of the stake require further detail).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the whitepaper describes that DKA holders can participate in governance; the dKargo DAO process is also described.
  • Evidence: Tier‑1 — https://whitepaper.dkargo.io/platform-overview/tokenomics , https://whitepaper.dkargo.io/platform-overview/governance
  • Why sufficient / why not (one line): governance is mentioned in Tier‑1 (although the specific onchain mechanics/voting contracts are not disclosed).
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): in Tier‑1, DKA is described as the base currency/fee token of the ecosystem and of governance participation; replacement with a stablecoin is not described.
  • Evidence: Tier‑1 — https://whitepaper.dkargo.io/platform-overview/tokenomics
  • Why sufficient / why not (one line): the documents do not describe an equivalent “stablecoin only” mode.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.dkargo.io/docs2-eng dKargo is an EVM‑compatible Layer 3 blockchain built on Arbitrum; context: logistics, node/RPC/bridging/deploy.
Tier‑1 https://docs.dkargo.io/docs2-eng/wallet-setup/adding-the-dkargo-network Warehouse testnet: RPC/chain id/currency symbol DKA/explorer; mainnet “scheduled for public release in 2025”.
Tier‑1 https://docs.dkargo.io/docs2-eng/contract-address/contract-address-list addresses of the core contracts (rollup/inbox/outbox/bridge, etc.) and DKA (L1/L2) + addresses for the Warehouse testnet.
Tier‑1 https://whitepaper.dkargo.io/platform-overview/tokenomics the role of DKA (payments/collateral/network fees/governance), total supply 5B and the distribution/circulation plan.
Tier‑1 https://whitepaper.dkargo.io/platform-overview/governance a description of the DAO/committee and the decision‑making process.
Tier‑1 https://etherscan.io/token/0x5dc60C4D5e75D22588FA17fFEB90A63E535efCE0 the onchain fact of the DKA ERC‑20 token and the max total supply 5B.
Tier‑1 https://docs.dkargo.io/docs2-eng/validator-operations/staking validators “stake assets” to participate in the verification of rollup batches; a link to the official staking script repo.
Tier‑1 https://docs.dkargo.io/docs2-eng/deploy-contract/how-to-deploy-a-contract developer entrypoint: how to deploy a contract on dKargo Chain (Remix/Hardhat/Foundry).
Tier‑1 https://docs.dkargo.io/docs2-eng/bug-bounty/bug-bounty-program a public bug bounty program (with rules/grading/rewards).

No comments to display

Back to top