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. Random Sampling DKG Proof System

Random Sampling FAQ

PreviousRandom sampling rolloutNextDKG Sync

Last updated 1 day ago

Was this helpful?

How do I choose which Core node to delegate my TRAC to?

The system is designed in such a way to incentivise positive network behavior (see more in Random Sampling DKG Proof System). That means your delegated TRAC will help increase a Core node's chances of receiving rewards, while the nodes with the best characteristics receive a higher share of the rewards. To pick a node, consider the following metrics (available in the )

  • Node Power – Shows how competitive the node is in earning rewards. Higher Node Power means higher chance of rewards.

  • Node Health – Reflects reliability and uptime. Higher Node health means higher chance of rewards

  • Operator Fee – The percentage cut the node takes from rewards to cover the cost of its operations (e.g. blockchain transaction fees).

You’re generally looking for a node with high Power, high Health, and a reasonable fee.

Can a node operator take my stake?

No. Delegated TRAC tokens are locked in smart contracts. Node operators cannot access or withdraw your stake. You can withdraw your tokens yourself after initiating a withdrawal and completing the 28-day unstaking period.

What happens if my Core node goes offline during an upgrade?

DKG is designed to be resilient. If your node goes offline (e.g., for maintenance), it won’t be slashed, but it may miss proof submissions during that downtime. This means:

  • Your node’s Node Health score may decrease.

  • You may receive lower rewards for that epoch.

As a node operator, maintaining your node uptime is one of the highest priorities and therefore it is incentivised. You can use the DKG Sync feature to catch up on missed data and rejoin the network without penalty.

Will my node be penalized if it misses a proof?

No, there is no slashing or loss of stake for missing a proof. However, missing proofs results in a zero score for that proof period, which reduces your total rewards for the epoch. Node Health will also decrease temporarily.

What’s the timeline for the V8.1 reward system rollout?

The rollout is structured as follows:

  1. V8.1.0 – Random Sampling live (current proofs and rewards)

  2. V8.1.1 – V6 rewards compatibility module

  3. V8.1.2 – Tuning Period rewards module

These are released in quick succession as development and testing complete, rolling out in June 2025.

How can I improve my node’s performance and earn more rewards?

Node rewards are based on three main factors:

  1. Uptime and proof submissions – Stay online and responsive to increase your Node health

  2. Ask price – Set a fair, competitive service fee, increasing your Node Power

  3. Set a low operator fee - making your node more interesting for delegators

  4. Promote your node - get TRAC holders excited to delegate their stake to your node to increase your Node Power

How are rewards collected for V6 and the Tuning Period?

Both the V6 rewards and the Tuning Period (between V8.0.0 and V8.1.0) are processed using the new Random Sampling reward system:

  • V6 rewards use a retroactive application of Random Sampling based on available historical data.

  • Tuning Period rewards assume all eligible nodes had full uptime and participation. Rewards for this period will be claimable once V8.1.2 is released.

Who is eligible for V6 era rewards?

Nodes that were active during the DKG V6 period (before the V8 upgrade) are eligible to earn accumulated rewards from that era. V6 rewards will be distributed via a compatibility module introduced in version V8.1.1, and are consolidated for the period of all 12 epochs in 2025 (1 year). Specifically, eligible nodes will be submitting proofs for upcoming epochs based on the same principles as for V8 era rewards.

Reward claiming for already elapsed epochs will assume 100% uptime for that period (all nodes will have equal Node Health), so nodes will compete on Node Power. Further technical details will be released with the V6 compatiblity module release on the DKG Testnet.

Publishing activity – Publish Knowledge Assets or for others to use to increase your Node Power

Staking UI
open your publishing API