Athlerse Whitepaper
  • INTRODUCTION
    • Introducing Athlerse
    • Disclaimer
    • Our Vision
    • Target Market & Sectors
    • Existing Problems
    • Product Proposition
    • Why Athlerse?
    • Definitions
  • HOW DOES IT WORK?
    • Top-quality Workouts for Free
    • Get Rewarded for Your Training
    • Extend Fitness Functionality
    • Discover Full Web3 Potential
    • Social Interaction with Athletes
    • Go-to-Market Strategy
  • Technical Aspects of Athlerse
    • Technology Stack
    • Web3 Tech Aspects
    • Blockchain Infrastructure
    • Trackers Integration
  • Athlerse AI Initiatives
    • Athlerse AI Functions
    • Personal Workout Plans
    • Smart AI Workout Analysis
    • Posture Analysis and Correction
    • AI-Powered Predictive Analytics
    • Voice Guidance & Virtual Trainer
    • AI-Powered Nutrition
    • Technical Overview
    • Athlerse AI Summary
  • Tokenomics
    • Tokenomics: Introduction
    • Tokenomics and Valuation
    • GYM Coin
    • $ATHL Token
  • Business Model
    • Product Financials & Monetisation
  • Roadmap
    • Roadmap
  • TEAM & PARTNERS
    • Meet the Core Team
    • Incubators & Partners
  • Use Cases
    • Use Case 1: Fit Mum
    • Use Case 2: 18 Years Old Teenager
    • Use Case 3: Trainer
  • OFFICIAL LINKS
    • Athlerse Website
    • Athlerse for Coaches & Athletes
Powered by GitBook
On this page
  • Web2 Simplicity meets Web3 Functionality
  • Transition from Web2 to Web3
  1. Technical Aspects of Athlerse

Web3 Tech Aspects

As Athlerse operates at the intersection of Web 2.0 and Web 3.0, it is crucial to develop a technology stack that seamlessly bridges the gap between these two worlds while providing an exceptional experience for both types of users.

Web2 Simplicity meets Web3 Functionality

The Athlerse app is designed to prioritize Web 2.0 simplicity while encapsulating most Web 3.0 functionality under the hood. Upon registration, the app generates a wallet for the user and stores it locally on the user's device, while also saving a password-encrypted private key on the server side. Each time the user signs in from a new device (e.g., after changing devices), the encrypted key is retrieved from the server and decrypted locally using the user's password. This approach ensures that Athlerse does not openly possess the keys while allowing flexibility and easy onboarding for regular Web 2.0 users, who are expected to constitute the core user base of the app.

When a user performs an action that requires interaction with the underlying wallet (e.g., spending $ATHL tokens from the user's balance or sending other transactions), the app facilitates this on the user's behalf by signing the required transactions with the keys stored locally on the user's device. This process is entirely transparent to the user to the extent that Web 2.0 users may likely be unaware of such technicalities. Nevertheless, this approach generates blockchain activity and provides traction proof for the entire Athlerse ecosystem.

Transition from Web2 to Web3

As Web 2.0 users become more familiar with Web 3.0 technology, they will be presented with the option to access Web 3.0 functionalities such as the in-app wallet and the ability to export their private key. This exported key can then be added to MetaMask or any other wallet of their choice, allowing users to fully engage with the Web 3.0 ecosystem. With that users will get the possibility to deposit, transfer, withdraw and exchange crypto tokens.

PreviousTechnology StackNextBlockchain Infrastructure

Last updated 1 year ago