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. Adoption
  3. Web3 and Wallet Integrations

Foundation

KGeN has 2 kinds of wallet:

  1. Gamer wallet - This wallet gets created when the gamer is interacting with the game but has not connected their credentials to the KGeN ecosystem. This wallet is created on the respective chain associated with the game. This wallet is identified by the gamer credentials inside the game. The gamer’s kcash rewards get accumulated in the gamer wallet which can be withdrawn to their user wallet when the threshold is reached. There is a N:1 mapping between gamer wallet and user wallet where multiple gamer wallets can be connected to a single user wallet.

  2. User wallet - This wallet gets created when the gamer connects to the KGeN ecosystem using KGeN login credentials. This wallet is a multi-chain wallet across EVM and non-EVM chains. All KGeN wallet applications work on the user wallet.

KGeN wallet is designed to support multiple block chains. Using chain abstraction, we simplify the gamer experience and don’t expose the complexities of multiple block chains.

Chains integrated:

  • Aptos

  • Polygon

  • Base

  • Klaytn

  • Haqq

  • ZkSyncEra

  • Kroma

Aptos smart contracts are written in move language and EVM smart contracts are written in Solidity.

PreviousWeb3 and Wallet IntegrationsNextWeb3 Toolkit

Last updated 4 months ago