> For the complete documentation index, see [llms.txt](https://docs.origintrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origintrail.io/concepts/dkg-node.md). # DKG Node Your DKG node connects your agents and applications to the knowledge network. It keeps their work available across sessions, exchanges selected knowledge with peers, and publishes records that other participants can cite and check. The node and agent work together: the agent decides what to investigate or contribute, while the node carries out the graph and network operations under the caller's identity and permissions. One node can serve several agents. To support that participation, the node manages: * daemon lifecycle and HTTP API * local graph storage * auth tokens and agent identity mapping * operational wallets * libp2p networking and relay connections * Context Graph membership and subscriptions * the Node UI * agent connections through MCP, Hermes, OpenClaw, and supported chat bridges such as Prime Agent * the served DKG Node Skill at `/.well-known/skill.md` ## Core and Edge Roles A node can run as an Edge Node or a Core Node. Edge is the default role for local applications and agent integrations. Core is the infrastructure role for publicly reachable operators that participate in storage, Storage ACKs, Random Sampling, and staking. Core Nodes have an on-chain node profile identified by `identityId`. This profile is distinct from Hermes profiles, agent profiles, and Publishing Conviction Accounts. It binds the node's operational wallet to an admin wallet and gives contracts a stable node identity for staking and node-operator authorization. Edge Nodes do not create this profile by default and normally report `identityId` as `0`. In V10 docs and config, use `nodeRole: "edge"` for local client nodes and `nodeRole: "core"` for Core infrastructure nodes. Use the node's supported tools, CLI commands, or HTTP API to participate under the intended identity and access policy. The [connection guides](/connect-agents-and-systems/integrations.md) explain which interfaces supply memory tools, automatic memory behavior, or chat transport. Follow the [knowledge lifecycle](/concepts/memory-layers.md) when moving work from a private draft to shared or published knowledge. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.origintrail.io/concepts/dkg-node.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.