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
  • Developer's Point of view
  • Player's Point of view
  1. Kratos Stack
  2. Engagement
  3. Compete
  4. Protocols

Loyalty Protocol

PreviousUser WorkflowNextUser Workflow

Last updated 2 months ago

Developer's Point of view

Loyalty protocol provides game developers with an easy-to-use API to integrate a new loyalty reward currency, KCash. This enables developers to incentivize players who participate in daily quests, battle pass challenges, and other game-specific LiveOps events with KCash. By leveraging it, developers can enhance the experience for their loyal and engaged players while also opening up new avenues for engagement and monetisation within their games.

The objective of this document is to give you a quick familiarity with the protocol. For deeper technical details, .

Player's Point of view

The Loyalty protocol values players' dedication in the game, rewarding their loyalty with KCash, a currency with tangible benefits. This currency can be redeemed for a diverse range of items available at the Kratos Store. The player's journey is as follows:

As players progress through their journey, they are motivated to play more and earn additional KCash, creating a positive feedback loop.

read here