OriginTrail
  • Get started with OriginTrail
  • OriginTrail Ecosystem — Call for Papers (Coming Soon)
  • Key Concepts
    • Decentralized Knowledge Graph (DKG)
    • DKG key concepts
  • TRAC: DKG utility token
  • Build with DKG
    • Quickstart (test drive the DKG in 5 mins)
      • Quickstart with Node.js
      • Quickstart with Python
    • Querying the DKG
    • 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
      • How to open up your node for publishing
    • DKG 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
      • Using the DKG with MCP
    • Ecosystem call for papers
  • DKG under the hood
    • Introduction
    • Delegated staking
      • Step-by-step staking
      • Redelegating stake
  • Random Sampling DKG Proof System
    • Random sampling rollout
    • Random Sampling FAQ
  • DKG Sync
  • 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

Was this helpful?

Edit on GitHub
  1. Build with DKG
  2. DKG Core Node

How to open up your node for publishing

Help publishers by providing API access to the DKG and increase your node reward potential

One way to increase your Node Power is to make your DKG Core node endpoint publicly accessible to enable publisher access to the DKG. This servers a useful purpose to the network by opening access to the DKG, enabling easier usage and sharing resources, for which Core nodes are incentivised through increasing Node power.

To make your DKG Core node endpoint publicly accessible, all you need to do is disable both IP-based and token-based authentication. This is done by setting ipBasedAuthEnabled and tokenBasedAuthEnabled to false in the .origintrail_noderc file located inside your ot-node directory.

ipBasedAuthEnabled and tokenBasedAuthEnabled fields are not present by default, so you must add them manually.

Below is an example of how your "auth" section should be configured in order to disable IP-based and token-based authentication.

...
    },
    "auth": {
        "ipBasedAuthEnabled": false,
        "tokenBasedAuthEnabled": false,
        "ipWhitelist": [
            "::1",
            "127.0.0.1",
            "<any_whitelist_ip_of_choice>"
        ]
    }
...

Opening your node endpoint by disabling authentication is considered a safe operation. This configuration exposes the node’s API to the public but does not expose any sensitive data such as your node wallets, private keys, or tokens.

Managing rate limits and protecting the endpoint excessive requests is the responsibility of the node operator.

Changes to .origintrail_noderc only take effect after a restart. Once the node is back online, its endpoint will be accessible without authentication restrictions.

const dkg = new DKG({
    endpoint: 'https://super-dkg-node.com',  // your node URL
    port: 8900 // your node DKG Port
});

const nodeInfo = await dkg.node.info(); 
// if successfully connected, the will return an object indicating the node version
// { 'version': '8.X.X' }
PreviousV8 DKG Core Node installationNextDKG toolkit

Last updated 1 day ago

Was this helpful?

Anyone can now use one of the to connect to your Core node an publish through it. So if for example your node URL is https://super-dkg-node.com, this is how dkg.js can connect to it:

dkg clients