OriginTrail
  • Get started with OriginTrail
  • OriginTrail Ecosystem — Call for Papers (Coming Soon)
  • Key Concepts
    • Decentralized Knowledge Graph (DKG)
    • DKG key concepts
  • Build with DKG
    • Quickstart (test drive the DKG in 5 mins)
      • Quickstart with Node.js
      • Quickstart with Python
    • ChatDKG builder toolkit
      • DKG SDK
        • Development environment setup
        • DKG Javascript SDK (dkg.js)
          • Interact with DKG paranets
          • Knowledge submission & curation
          • Paranet's incentives pool implementation
        • DKG Python SDK (dkg.py)
      • DKG paranets
        • Deploying a DKG paranet
        • Building with DKG paranets
        • Syncing a DKG Paranet
        • Initial Paranet Offerings (IPOs)
          • IPO specification
          • Launching your IPO
          • Paranet's incentives pool
          • IPO voting
      • AI agents
        • ElizaOS DKG agent
        • Custom DKG Python agent
        • Custom DKG JavaScript agent
    • DKG Edge Node
      • DKG Edge Node architecture
      • Get started with the Edge Node boilerplate
        • Automated setup with the installer
        • Manual setup
        • Usage example
      • Customize & build with the Edge Node
      • Knowledge Mining and dRAG examples
      • Deploy your Edge Node based project
        • Automated deployment with installer
      • DKG Edge Node inception program
      • DKG Edge Node API documentation
    • DKG Core Node
      • Run a V8 Core Node on testnet
        • Preparation for V8 DKG Core Node deployment
        • V8 DKG Core Node installation
      • Run a V8 Core Node on mainnet
        • Preparation for V8 DKG Core Node deployment
        • V8 DKG Core Node installation
  • Delegated staking
    • Delegated staking—Introduction
      • Step-by-step staking
      • Redelegating stake
  • Integrated Blockchains
    • Base blockchain
      • Connect to Base
    • Gnosis chain
      • Connect to Gnosis
    • NeuroWeb
    • Teleport instructions - NeuroWeb
    • Bridging to Moonbeam
    • Deployed smart contracts
  • Bounties & rewards
    • General bug bounty
    • Code contributions & V8 bug bounty
  • Whitepapers & RFCs
    • OriginTrail whitepaper
    • OriginTrail RFCs
  • Useful Resources
    • What's new with OriginTrail V8
    • DKG V8 guidebook
      • Protocol updates
      • Feature roadmap
      • How to upgrade to V8?
    • Public nodes
    • Tutorials
    • Test token faucet
    • Development principles
    • Community created resources
    • Linked data & knowledge graphs
    • Available networks, network details and RPCs
    • OT Node Engine implementation details
      • Modules
      • Command Executor
    • Contribution guidelines
      • Guidelines for automated test contributions
    • Explore the OriginTrail ecosystem
Powered by GitBook
On this page
  • Querying paranets
  • Running paranet services
  • Paranet permissions

Was this helpful?

Edit on GitHub
  1. Build with DKG
  2. ChatDKG builder toolkit
  3. DKG paranets

Building with DKG paranets

PreviousDeploying a DKG paranetNextSyncing a DKG Paranet

Last updated 2 months ago

Was this helpful?

Paranets are like "virtual" knowledge graphs on the OriginTrail Decentralized Knowledge Graph (DKG). Building with them is quite similar to building on the DKG in general. However, paranets enable you to contain your operations services on these "virtual" graphs, e.g., querying a specific paranet with SPARQL or adding a knowledge collection* to a specific paranet.

*A knowledge collection (KC) is a collection of Knowledge Assets. It refers to structured data that can be stored, shared, and validated within a distributed network.

To gain access to the paranet knowledge graph, you can use one of the , or deploy a and set it up to host the paranet (or "sync" it). More information is available on the page.

A direct code example of paranets in use can be found here -

Querying paranets

Once you have access to the paranet knowledge graph via a gateway node, you can use one of the to interact with it. It is also possible to open up your triple store SPARQL endpoint directly and query the paranet knowledge graph in its own repository (the paranet repository name is equivalent to the paranet profile Knowledge Asset UAL, with dash characters instead of slash).

Using SPARQL, it is possible to query and integrate knowledge from multiple paranets and whole DKG in one query using SPARQL federated queries.

Running paranet services

Paranets enable registering and exposing both on-chain and off-chain services associated with it. A paranet service can be identified by all users of the paranet via its registry Knowledge Asset and can have multiple on-chain accounts associated with it, enabling them to engage in economic activity within the DKG. Examples of paranet services are AI agents (e.g., autonomous reasoners mining knowledge collections), chatbots (e.g., ), oracle feeds, LLMs, dRAG APIs, etc.

Paranet operators manage the services through the Paranet Services Registry smart contracts or DKG SDK.

Paranet permissions

There are three permission policies for paranet:

  • Nodes access policy—defines which nodes can sync the paranet:

    • OPEN—Any node can sync the paranet.

  • Miners access policy—defines which knowledge miners can add knowledge to the paranet:

    • OPEN—Any address can submit a knowledge asset to the paranet.

  • Knowledge asset submission access policy:

    • OPEN—Any knowledge asset can be added to the paranet.

    • STAGING—Knowledge miners first submit the knowledge asset to staging, where it is reviewed by curators chosen by the paranet owner. The curators can approve (and automatically add knowledge asset to the paranet) or deny staged knowledge asset(which then doesn't get added to the paranet).

public DKG nodes
DKG node
Sync a DKG Paranet
Paranet Demo
DKG SDKs
Polkabot