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
  4. KDrop

Technical Implementation and System Design

PreviousUser WorkflowNextGames API Integration

Last updated 4 months ago

Following are some key notes on the architecture below:

  • K-Drop system is designed for real-time validations, many design choices were based on this requirement.

  • On completing the campaign, the gamer earns points in addition to USDT or Kcash based on the type of campaign. K-Points is maintained as a standalone module and the K-Drop system interacts with that module. For Kcash rewards, K-Drop system interacts with lazychain.

  • To do campaign task validations, K-Drop system interacts with different social APIs(twitter, discord, telegram, google, steam, wallets) and game APIs.

  • K-Drop is integrated with the following games to do real-time game activity validation - Mighty action heroes, Guild of guardians, Angry dynamites lab, Beacon, Fableborne, Seraph, Mystery Society, Bason family, Overtake, Wanderers, Galfi, Super champs, LHU, Zerosum, Duper. This list keeps growing. We have kept the architecture modular so that it's very easy to add a new game to our system.

  • The referral module keeps track of referral invites and provides additional rewards points for the referrer.

The following architecture shows how we built the realtime validation system. This module is used across different systems like K-Drop and K-Quests.