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
  • Overview of Releases
  • Rollout Principles
  • What You Should Do

Was this helpful?

Edit on GitHub
  1. Random Sampling DKG Proof System

Random sampling rollout

PreviousRandom Sampling DKG Proof SystemNextRandom Sampling FAQ

Last updated 1 day ago

Was this helpful?

The deployment of the DKG Random Sampling system follows a carefully phased approach to ensure stability, fairness, and backward compatibility with earlier versions of the DKG. This page outlines the rollout timeline, what each release includes, and what node operators and delegators can expect.

Overview of Releases

✅ Phase 1: RFC Confirmation

  • Goal: Finalize community review of

  • Outcome: Approval of the Random Sampling design by the community and core development team

  • Phase status: Completed

🚀 Phase 2: V8.1.0 — Initial Rollout (Active Proof System)

  • Features Introduced:

    • Live Random Sampling challenge generation and proof submission

    • Score calculation per proof period

    • Epoch-based reward allocation system

    • DKG Sync system goes online

  • Who is affected:

    • Core Nodes begin submitting live proofs

    • Delegators start accruing rewards for the active epochs (but do not yet claim rewards for past epochs)

  • Purpose: Establish live PoK infrastructure and real-time score updates for staking participants

  • Phase status: Live on Testnet. Mainnet rollout expected in June 2025

🔄 Phase 3: V8.1.1 — V6 Compatibility Module goes online

  • Goal: Allow accumulated rewards from the DKG V6 era to be earned retroactively

  • How it works:

    • Applies the Random Sampling system retroactively for TRAC fees in the V6 period

    • Nodes that were active during the V6 phase can compete for retroactive rewards, claiming tokens for completed epochs and competing for upcoming epochs.

  • Compatibility Duration: Available for a limited window (12 months from V8.0 launch)

  • Phase status: Testnet & Mainnet rollout expected in June 2025

🛠 Phase 4: V8.1.2 — Tuning Period Module

  • Goal: Distribute locked fees for the period between V8.0.0 and V8.1.0 releases

  • How it works:

    • All active nodes during this period are considered to have 100% uptime for the purpose of reward allocation

    • The same score distribution and reward formula is applied as in the live Random Sampling system

  • Phase status: Testnet & Mainnet rollout expected in June 2025

Rollout Principles

  • Incremental Activation - Each module builds on the previous one, ensuring that no backward compatibility is broken

  • Transparency First - The DKG Staking UI will be upgraded to reflect:

    • Node power, which will represent the current node power in the network with regards to its stake, service ask and publishing factor

    • Node health, computed based on Proof submissions per epoch

    • Compatibility module reward status

  • Fail-Safe Participation - Delegators and Node Runners are protected from loss of eligibility due to technical transitions, with catch-up mechanisms in place for reward collection

What You Should Do

Node Runners

  • Make sure to follow the updates to update your node as soon as the V8.1 release goes live on mainnet

  • Once your node is update mane sure to monitor and maintain its proof submission health

  • Optionally enable auto-claiming for delegators via node services to automatically restake all rewards and increase your Node power

Delegators

  • You don’t need to take immediate action

  • Make sure you understand when rewards become claimable based on finalization rules

  • Use the upgraded Staking UI to track your delegator epoch scores and rewards

OT-RFC-24