> For the complete documentation index, see [llms.txt](https://docs.quicksync.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quicksync.me/framework/architecture.md).

# Architecture

Wallet-connected flow chart 

{% hint style="info" %}
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! 
{% endhint %}

<figure><img src="/files/05fTuTF4Ou4ovmwSZKII" alt=""><figcaption></figcaption></figure>

## No-Account access flow chart&#x20;

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.

<figure><img src="/files/2V6FE1g32KXYZHDmYUgb" alt=""><figcaption></figcaption></figure>

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.quicksync.me/framework/architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.