LogoLogo
Developer API
QS Documentation
QS Documentation
  • Foundation
    • Abstract
    • Introduction
  • Framework
    • Overview
    • Partner Ecosystem
    • Architecture
    • For Developers
    • API Stack
    • For Creators
    • Features
    • Integrations
  • QS dApp Suite
    • Overview
  • QS Share
    • Overview
    • Getting Started
    • Access Options
    • Features
      • File Transfer
      • Notepad
      • Chat
    • Use Cases
    • Data Privacy
  • StageX
    • Overview
  • QS Marketplace
    • Overview
    • Features
  • QS Token
    • Token Utility
    • Revenue Model
    • Tokenomics
  • Market & Vision
    • Know the Market
    • Our Movement
    • High-Level Roadmap
    • Investor Deck
    • KYC Verification
  • Stay Connected
    • Team
    • Inquiries
    • Website
    • Twitter
    • Telegram
Powered by GitBook

Social Media

  • X

@2025 Quick Sync

On this page
  • Wallet-connected flow chart
  • No-Account access flow chart
  • Architecture Core Components
  1. Framework

Architecture

High-Level

PreviousPartner EcosystemNextFor Developers

Last updated 4 months ago

Wallet-connected flow chart

For users looking to unlock the full potential of QS Share, the connected wallet provides a feature-rich experience. You can still use the free dApp version!

No-Account access flow chart

Users can enjoy the the No-Account version of QS Share with full access to core functionalities, such as file sharing, notes sharing, and private chat rooms, all secured with decentralized servers for encryption and keyset exchanges.

Architecture Core Components

QS Build's foundation is made up of the following core components, which developers can leverage to create robust dApps:

1. Channel Represents the shared context for user interactions, defined by a lifecycle (session). It facilitates the establishment of a shared key between users and supports the creation of short-lived or long-lived sessions linked to media. This component serves as the foundation for secure and seamless user interactions within decentralized applications.

2. Key Establishment Protocol Handles the secure sharing of cryptographic keys to enable end-to-end encrypted and Zero-Knowledge (ZK) communication.

3. Content Processing Pipeline [Coming Soon] A set of functions or processes that handle data transformation and manipulation, enabling operations such as formatting or adjusting content while maintaining privacy.

4. Media Transmission A client side component responsible for the secure and efficient transmission of media (e.g., files, images, or videos) across the decentralized network, ensuring reliable delivery without compromising privacy.

5. Delivery Service Facilitates secure and efficient data transfer for files and text across multiple communication models. For files, it supports peer-to-peer sharing requiring online clients (using protocols like Waku or WebRTC) and decentralized buckets for uploads accessible even when clients are offline. For text, it offers peer-to-peer synchronization via wallet-based messaging and relay nodes that can forward or store messages, enabling offline communication with faster sync speeds.

These components provide the building blocks necessary to create highly secure, private, and efficient decentralized dApps.