Skip to main content

Dock

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

Dock — an infrastructure project about decentralized identity and verifiable credentials (the Truvera platform).

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 platform for issuing and verifying verifiable credentials (digital ID) and building an “ID ecosystem”.
  • Who it’s for: companies/organizations and developers that integrate the issuance/verification of digital credentials.
  • Why onchain/token: onchain is used as an infrastructure layer for identity/verifiable attributes; the DOCK token is used to pay for onchain write operations, for staking/validation and for participation in governance (per Tier‑1 docs).

How it works (very briefly)

  1. The user (organization) does: issues digital credentials (credentials/attributes) via the platform.
  2. The system does: enables verification of credentials and their use in onboarding/verification processes.
  3. The user gets: reusable credentials and faster checks.
  4. Where the blockchain is: the project positions the solution as decentralized ID; the network/activity is observable via the explorer.
  5. Token role: DOCK is used to pay for onchain write operations; the token also participates in PoS validation/staking mechanics and governance (voting on proposals).

Quick links: AI thesis fit

Project passport

Field Value
Project name Dock
Also known as (aliases) Dock Network, Truvera
Logo (logo) ../assets/692_dock_logo.svg
Token symbol (ticker) DOCK
Category Infra
Primary chain (chain) Dock
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (fees + staking + governance)
Max supply ~1 000 000 000 DOCK (emission schedule)
Issuance emission rewards (decrease over the years; up to 25% remaining supply per year)
Tokenomics (tokenomics, brief) Onchain write operations require DOCK (fees). Epoch rewards = tx fees + emission; distribution: 50% Treasury and 50% validators (then nominators in proportion to stake, minus commission).
Governance onchain (token holders vote on proposals; vote weight depends on locked tokens and the lock duration)
Admins/keys —
Audit —
Bug bounty —
Team (team) Dock Labs
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) verifiable credentials + digital ID
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 2 / token_score 3 / evidence_score 3
Last verified 2026-02-11

General project overview

Dock (Dock Labs) describes Truvera as a platform for issuing and verifying verifiable credentials and integrating “decentralized ID” into existing processes (IAM, KYC/IDV, KYB etc.). Within DecAIHub’s AI thesis, the project is considered an infrastructure project, without a confirmed AI component.

Features/modules

  • Issuance of verifiable credentials.
  • Verification of credentials and integration into business processes.
  • SDK/API (per the project’s claim).

Typical scenarios

  • Scenario 1: an organization issues a credential to a user → the user presents the credential during onboarding in another service.
  • Scenario 2: a verification provider verifies a credential → receives confirmation of attributes without re‑checking documents.

Getting started (wallet/network)

  • What you need: access to the platform’s documentation/SDK.
  • Network/chain: Dock.
  • Fees: onchain write operations require DOCK (fees); the amount depends on the operation’s resource consumption (size/disk/CPU) and includes a base fee.

Architecture/tech (non‑AI)

  • Components: the Dock network/protocol, SDK/API and the platform’s application services.
  • Participant roles: issuing organizations, credential‑holding users, verifiers.
  • Where logic runs: an onchain identity/verifiability layer + an application layer (API/SDK) — see the documentation for details.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: fees for onchain write operations; staking/validation (PoS) and emission rewards; governance (voting on proposals).
  • Protocol necessity drivers: write operations require the token (fees); the security of the PoS network and validator selection are tied to stake; governance uses locked tokens and lock duration for vote weight.
  • Who pays fees: users/integrators who perform onchain write operations (DID/keys, revocation registries, schemas etc.).
  • Where fees go: included in epoch rewards together with emission rewards; then 50% Treasury and 50% validators (and distribution among nominators after commission).
  • Issuance/burn: emission rewards per the schedule (decrease over the years; up to 25% remaining supply per year); also tx fees in epoch rewards.
  • Security/incentive mechanisms: NPoS: validator candidates and nominators lock/stake DOCK; rewards depend on performance; slashing for malicious behaviour is possible.
  • Distribution and token issuance schedule: —.
  • Treasury: Treasury receives 50% of epoch rewards (tx fees + emission).

Governance

  • Who makes decisions: token holders through voting on proposals (vote weight depends on locked tokens and the lock duration).
  • How protocol parameters change: through onchain proposals/voting by token holders.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: —.

Project status and timeline

  • Current status: mainnet (based on the presence of public materials and an explorer).
  • Key releases/milestones: see the project’s release notes/documentation (in links_*).
  • Roadmap: see the Roadmap link (in links_*).

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: use depends on organizations’ integrations with the platform.

AI component of the project

  • What is real AI here? No Tier‑1 confirmation of an AI component in the product was found.
  • What is truly onchain? Decentralized identity and verifiable credentials within the Dock/Truvera ecosystem (per the project’s claim).
  • Why is a token needed? DOCK is used for onchain write operation fees, staking/validation and governance (per Tier‑1 docs).
  • Red flags (based on the information found): mixing marketing claims with proof without Tier‑1 artifacts on tokenomics and onchain mechanics.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality low 0
Onchain necessity medium 2
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 mention of AI as intent/applicability was found.
  • Evidence: Tier‑1 — https://dock.io ; https://docs.dock.io/
  • Why sufficient / why not (one line): The project describes identity/credentials, not AI functionality.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): An AI component is not established per Tier‑1.
  • Evidence: Tier‑1 — https://dock.io ; https://docs.dock.io/
  • Why sufficient / why not (one line): There is no description of tasks/models/AI flow.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): An AI demo is not applicable: an AI component is not established.
  • Evidence: Tier‑1 — https://dock.io
  • Why sufficient / why not (one line): —.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://dock.io
  • Why sufficient / why not (one line): Not applicable without a confirmed AI component.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the AI architecture is not applicable: an AI component is not established.
  • Evidence: Tier‑1 — https://dock.io
  • Why sufficient / why not (one line): —.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Dock
  • Addresses/identifiers: — (addresses of specific modules were not recorded within this card)
  • Evidence: Tier‑1 — https://dock.subscan.io/
  • Why sufficient / why not (one line): The public explorer confirms the existence of the network/onchain state.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: verifiable credentials/decentralized ID infrastructure (issue/verify) as the claimed product layer.
  • Evidence: Tier‑1 — https://dock.io ; https://docs.dock.io/
  • Why sufficient / why not (one line): Official materials describe product logic on top of decentralized ID.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality was found.
  • Evidence: Tier‑1 — https://dock.io ; https://docs.dock.io/
  • Why sufficient / why not (one line): 1 requires an explicit argument “without the blockchain X breaks down”; not established.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The Dock network has a utility token, DOCK (used for fees/staking/governance), so “no token” = 0.
  • Evidence: Tier‑1 — https://docs.dock.io/dock-token/token-utility
  • Why sufficient / why not (one line): The official documentation directly describes the roles of the DOCK token in the network.
  • 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): Any onchain write operation on the Dock blockchain requires DOCK (fees).
  • Evidence: Tier‑1 — https://docs.dock.io/dock-token/token-utility
  • Why sufficient / why not (one line): The documentation directly records that onchain write operations are paid for with the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): DOCK is used for staking (NPoS) and emission rewards for validators/nominators; slashing is provided for.
  • Evidence: Tier‑1 — https://docs.dock.io/dock-token/emission-rewards ; https://docs.dock.io/dock-token/staking/staking-process
  • Why sufficient / why not (one line): Tier‑1 sources describe staking/emission rewards and slashing risks as part of network security.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): Token holders vote on proposals; vote weight depends on locked tokens and the lock duration.
  • Evidence: Tier‑1 — https://docs.dock.io/dock-token/token-utility
  • Why sufficient / why not (one line): The documentation explicitly describes governance mechanics via locked DOCK.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The token is built into the protocol mechanics of fees/staking/governance; replaceability without changing the protocol is not confirmed.
  • Evidence: Tier‑1 — https://docs.dock.io/dock-token/token-utility ; https://docs.dock.io/dock-token/emission-rewards
  • Why sufficient / why not (one line): Even with alternative payment tokens, stake/governance require native integration; conservatively TK_4=0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://dock.io Description of the Truvera platform: verifiable credentials/decentralized ID, issuance and verification scenarios.
Tier‑1 https://docs.dock.io/ Official product/platform documentation.
Tier‑1 https://dock.subscan.io/ Public explorer of the Dock network (the fact of an onchain network/state).
Tier‑1 https://docs.dock.io/dock-token/token-utility Roles of the DOCK token: fees for onchain write operations, staking/validators, governance via locked tokens.
Tier‑1 https://docs.dock.io/dock-token/emission-rewards Emission rewards, reward distribution (tx fees + emission), Treasury 50% / validators 50%, NPoS and slashing.
Tier‑1 https://docs.dock.io/dock-token/staking/staking-process Staking parameters (12 hour epochs, unbonding ~7 days, oversubscription and reward payout).

No comments to display

Back to top