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. KQuest

User Workflow

PreviousKQuestNextTechnical Implementation and System Design

Last updated 3 months ago

Viewing Quest List

Users can Filter or Sort Quest List

Starting A Quest

Submit Proof Of Completion

Starting the Quest:

  • User accesses quest details page and starts the quest.

  • If proof of work (POW) submission is enabled, a process is initiated.

Login Method Selection:

  • User selects a login method from a dropdown.

  • Standard validation is applied to the entered details.

  • If validation fails, an error message is shown, and the "Submit" button remains disabled.

POW Submission:

  • User sees a pop-up to upload the proof of work.

  • User selects an image file from their device and submits it.

  • The system confirms successful submission or provides an error message.

Clan Chief Referral:

  • If required, the user is prompted to provide the mobile number of their clan chief.

  • Standard validation is applied to the mobile number.

  • If the number is invalid or not registered, the system provides an error message.

  • Alternatively, the user can select an option indicating they do not have a clan chief.

Final Steps:

  • Once validated, the proof of submission and additional details are recorded.

  • If the user closes the pop-up or encounters errors, they can retry the process or abandon it.

Users can Share a Quest

K-Quest Leaderboard Score Update Flow