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
  • Flow Diagram
  • User Onboarding
  • Battle Pass Events
  • Daily and Weekly Pass Events
  • Special Events
  1. Kratos Stack
  2. Engagement
  3. Compete
  4. Protocols
  5. Loyalty Protocol

User Workflow

PreviousLoyalty ProtocolNextRewards

Last updated 3 months ago

The Loyalty protocol rewards dedicated players in the game. These players, who are consistently engaged and participate in quests and events, now receive extra rewards in the form of KCash.

Upon launching the game for the first time post-protocol implementation, a user's in-game wallet is automatically created, and an initial one time welcome bonus (eg. 50 KCash) is deposited.

Flow Diagram

User Onboarding

When a player launches the game for the first time the API creates a wallet for the user and deposits with one time welcome bonus (eg. 50 KCash). The player can opt-in to link their wallet with their phone number through an OTP validation to take custody of their wallet. However this is not a mandatory step during the onboarding. The user can opt-in again at the time of redemption.

Battle Pass Events

Players can earn KCash as they progress through the Battle Pass events.

Daily and Weekly Pass Events

Players have the opportunity to earn extra rewards through daily and weekly quests and other in-game events. These quests allow players to earn KCash as a reward for their participation and progress.

Special Events

Players have the opportunity to earn KCash by participating in Seasonal and Special events.