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 Stack
  2. Engagement
  3. Play

Games API Integration

The Instant Gratification streamlines the KQuest and KDrop validation and reward distribution process for integrated games. It automates the validation of kquests and campaigns submitted by players via game APIs, ensuring accurate and real-time proof verification. Once validated, it instantly distributes the corresponding rewards to users, enhancing player engagement through immediate feedback.

This system eliminates manual interventions in quest validation, reducing delays, and fostering a seamless gaming experience.

User Flow

  1. Submission Process:

    • Players complete associated task and click on "Validate" or submit proof of completion through the game interface.

    • Proofs include data such as quest IDs, user IDs, and relevant event details.

  2. Validation Status:

    • Users receive live feedback in the game UI.

    [Placeholder Validation success image from KDrop]

    • Upon successful validation, the quest status updates to "Validation Completed," visible in the user's history.

  3. Reward Distribution:

    • Rewards are credited instantly upon validation, with confirmation notifications displayed to the user.

////// TO CHANGE//////

System Architecture and Implementation Overview for Manual

  1. Lambda Function-Based Validation for manual submissions:

    • A Lambda function is invoked when users submit quest proofs.

    • The system dynamically determines the appropriate plugin based on the quest ID and event data to validate the submission.

    • Supported validations include API-based proof verification for achievements like kills, completed games, or damage dealt.

  2. API Endpoints:

    • Validation Endpoint: POST /admin/quests/proof-validation Processes quest proofs and updates the status.

      • Payload example:

        jsonCopy code{
          "questId": "uuid",
          "userId": "uuid",
          "stage": 1,
          "status": "VALIDATED PROOF"
        }
    • Reward Distribution API: After validation, triggers a platform rewards API to credit rewards.

  3. Backend:

    • Proof Submission: Captures and logs user proof submissions.

    • Validation Logic: Verifies proof authenticity via plugins like event-based or attribute-based validation.

    • Error Handling: Logs and reports validation failures for troubleshooting.

    • Reward Logic: Communicates with rewards systems to ensure instant distribution.

  4. Supported Use Cases: Currently implemented for quests such as:

    • Achieving a specific number of kills.

    • Completing a set number of tasks like connecting wallets or socials.

    • Completing tutorials on game website.

This scalable architecture supports modular plugin integration for future quests, ensuring adaptability and robustness.

PreviousTechnical Implementation and System DesignNextCompete

Last updated 4 months ago