LogoLogo
Visit the KGeN website
  • Introduction
  • POG
    • Five Key Dimensions
    • POG Score
    • Gamer Profile Mint, Updation, Data Ownership & Rights
    • Publishers & Brands: Data Access & Rights
    • POG-E: Augmented Gaming LLM
      • Foundational Elements
      • Key Components of POG-E tech stack
      • Foundational Data powering POG-E
      • Agent Development Framework
      • Data Orchestration
      • Developer Tools
      • Deployment, Scalability, Monitoring, Maintenance and Future Enhancements
      • AI Agent Use Cases
  • Tokenomics
    • r-KGeN
    • $KGeN
      • $KGeN Allocation and Unlock Schedule
      • $KGeN token utility
        • Demand Lever : Product
        • Demand Lever : Staking
        • Demand Lever : Business Model
  • Kratos Oracle Network
    • Oracles
    • Oracle Functionality
    • Consensus Mechanism
    • Oracle Acquisition and Staking Requirements
    • Key Purchase and Multichain Support
    • KGeN Sale and Staked Keys Growth
    • Oracle Reward Structure
    • Oracle Hardware and Software Deployment
  • Kratos Stack
    • Stack Composition and Interaction
    • Engagement
      • Play
        • KQuest
          • User Workflow
          • Technical Implementation and System Design
        • KDrop
          • User Workflow
          • Technical Implementation and System Design
        • Games API Integration
      • Compete
        • Klash
        • Protocols
          • ESports Protocol
            • User Workflow
          • Loyalty Protocol
            • User Workflow
      • Rewards
      • Redeem
        • E-Commerce
          • System Design
    • External Partner Interfaces
    • Reputation
      • The POG Engine
      • The POG Attribution
        • System Overview
      • Impact of The POG
    • Adoption
      • Web3 and Wallet Integrations
        • Foundation
        • Web3 Toolkit
        • Tokens
        • Chain abstraction
        • Solutions for Gamers
      • Clan Tools
        • Clan Chief and Member Overview
        • User Workflow
        • System Architecture
      • Profile
      • Leaderboards
    • Infrastructure and Scalability
      • Data
      • Frontend Architecture
      • Devops & Security
      • AI
  • Publishers
    • Self Serve
      • Technical Implementation
      • Publishers Flow
  • Appendix
Powered by GitBook
On this page
  1. Kratos Oracle Network

Oracle Reward Structure

PreviousKGeN Sale and Staked Keys GrowthNextOracle Hardware and Software Deployment

Last updated 3 months ago

Reward Calculation Formula

The rewards an Oracle operator earns are determined by the following formula: Reward Points ~ (Base Reward × Keys Staked × Performance)

  • Base Reward: The base reward is a network-defined value that scales with the overall health and transaction volume of the PoG network.

  • Keys Staked: The total Stablecoin, ETH, APT or KGeN tokens staked by the Oracle operator directly influences the reward size.

  • Performance: Performance is measured through metrics such as:

    • Oracle Uptime: Consistently online and synchronized Oracles are considered high-performing.

    • PoG Computation Accuracy: Oracles that calculate and submit PoG scores efficiently and accurately are rewarded proportionally.

Leaderboard and Ranking

Oracle operators are ranked on a global leaderboard based on their points. Higher-ranked Oracles receive larger shares of the reward pool. Leaderboards will be activated post the public sale of keys.

Reward System Validity

The current reward system will operate for a period of 3 years post the launch of the PoG. Following this period, the system will transition to a Proof of Stake (PoS) model, outlined below:

Proof of Stake Transition: After 3 years, the rewards system will shift to a PoS-based mechanism, where rewards and governance rights are directly tied to the amount of KGEN staked.