去中心化知识图谱

3. Build a DKG-enabled app

Use the node APIs and packages to publish Knowledge Assets, query data, and coordinate through context graphs.

Setup guides

---

Quick Start

Prerequisites: Node.js 22.13+ (or 23.4+), npm 10+. macOS, Linux, and Windows (PowerShell 5.1+ or WSL2) all supported.

Typical use cases

Async publisher (optional, for batching)

dkg publisher enable # enable the async publisher dkg publisher publish-async <cg> <name> [--publisher-node-identity-id 0] # alias for dkg ka publish-async dkg publisher jobs # list publisher jobs dkg publisher stats # publisher throughput stats

publisher wallets need native gas plus PCA registration or TRAC; node identity is optional attribution

CLI commands

```bash dkg init # interactive setup — network, node name, role, triple-store backend dkg start [-f] # start the node daemon (-f for foreground) dkg stop # graceful shutdown dkg status # node health, peer count, store status dkg logs # tail the daemon log dkg peers # list discovered agents on the network dkg peer info <peer-id> # inspect a peer's identity and addresses

API authentication

Node APIs use bearer token auth by default.

The token is created on first run and stored in:

~/.dkg/auth.token

Example:

TOKEN=$(dkg auth show)
curl -H "Authorization: Bearer $TOKEN" http://127.0.0.1:9200/api/agents

The dashboard signs in with this token automatically only when it is opened on the node host itself (http://127.0.0.1:9200/ui or http://localhost:9200/ui). Opened from another machine or under another host name, it asks for the token instead; an SSH tunnel to the API port keeps the automatic sign-in. A reverse proxy that adds forwarding headers (Forwarded, any X-Forwarded-*, X-Real-IP, X-Client-IP, True-Client-IP, CF-Connecting-IP, Via) is treated as remote. One on the node host that forwards with a loopback Host and adds none of them (e.g. nginx's default proxy_set_header Host $proxy_host) still looks like a local caller, so keep authentication in front of any proxy that exposes the dashboard beyond the node host.

Operations that act on the whole node (node settings and logs, shutdown, agent registration, local agent integrations, bulk publisher-queue changes) require this node-level token. Agent-scoped tokens receive 403 there.

The full node API surface (assertions, memory layers, context graphs, file ingestion, querying) is documented in packages/cli/skills/dkg-node/SKILL.md — this is the canonical reference loaded by any DKG-aware agent.

---

Community integrations

Beyond the first-party framework adapters above, DKG V10 supports community-contributed integrations — CLIs, MCP servers, agent plugins, and services that run against your local node through its public HTTP API, dkg CLI, or MCP interface. They live in contributor-owned repositories and are discovered through the OriginTrail/dkg-integrations registry.

dkg integration list                              # list verified + featured tiers (default)
dkg integration list --tier community             # include community-tier (contributor-submitted) entries
dkg integration info <slug>                       # inspect a single entry
dkg integration install <slug>                    # install — automates `cli` and `mcp` install kinds
dkg integration install <slug> --allow-community  # required to install a community-tier entry

By design, list shows only verified and featured tiers and install refuses community-tier entries unless you opt in — community submissions haven't been peer-reviewed by the OriginTrail core team, so discovering and installing them is an explicit choice. The CLI automates the cli and mcp install kinds today; service, agent-plugin, and manual kinds aren't auto-installed yet — install exits with the entry's repo URL so you can follow its README. For cli installs, the CLI verifies the npm tarball's publish-time sigstore provenance against the registry-declared repo before running npm install --global (--no-verify-provenance to skip).

Building one: fork the minimal, zero-dependency reference template at OriginTrail/dkg-hello-world, which demonstrates a full Working Memory write → read round trip. Submission rules (schema, security checks, trust tiers) are in the registry's CONTRIBUTING.md.

---

Community integrations (registry: OriginTrail/dkg-integrations)

dkg integration list [--tier community] # default tier filter is verified+ dkg integration info <slug> # show details for one entry dkg integration install <slug> # install cli/mcp kind; --allow-community for community-tier entries

Core packages

@origintrail-official/dkg                    CLI and node lifecycle (daemon, HTTP API, file store)
@origintrail-official/dkg-core               P2P networking, protocol, crypto, memory model types
@origintrail-official/dkg-storage            Triple-store interfaces and adapters
@origintrail-official/dkg-chain              Blockchain abstraction
@origintrail-official/dkg-publisher          Publish and finalization pipeline (SWM → VM)
@origintrail-official/dkg-query              Query execution and retrieval
@origintrail-official/dkg-agent              Identity, discovery, messaging, wallet keys
@origintrail-official/dkg-node-ui            Web dashboard, chat memory, SPARQL explorer
@origintrail-official/dkg-node-store         Daemon protocol persistence (outbox, sync checkpoints, cursors, KA numbers, chain log)
@origintrail-official/dkg-graph-viz          RDF visualization
@origintrail-official/dkg-evm-module         Solidity contracts and deployment assets
@origintrail-official/dkg-network-sim        Multi-node simulation tooling
@origintrail-official/dkg-epcis              EPCIS → RDF supply-chain adapter
@origintrail-official/dkg-mcp                MCP server for Cursor / Claude Code / coding agents