> For the complete documentation index, see [llms.txt](https://kinbex.gitbook.io/kinbex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kinbex.gitbook.io/kinbex-docs/part-ii-system-architecture/01-client-runtime-and-enclave.md).

# 4. Client Runtime & Enclave

[← Previous: Competitive Matrix](/kinbex-docs/part-i-protocol-thesis/03-competitive-matrix.md) | [Next: Telemetry & Data Fabric →](/kinbex-docs/part-ii-system-architecture/02-telemetry-and-data-fabric.md)

***

## 1. Technical Stack Overview

Kinbex is engineered as a zero-install, single-page responsive terminal accessible globally via `kinbex.com`. The front-end architecture is optimized for high-frequency trading telemetry and synchronized social interaction.

```
┌─────────────────────────────────────────────────────────────┐
│                    KINBEX CLIENT ARCHITECTURE               │
├─────────────────────────────────────────────────────────────┤
│  Presentation: React 18 Concurrent + TanStack Router        │
│  Design Tokens: Tailwind CSS + Radix UI Primitives          │
│  State Management: TanStack Query + WebSocket Synchronizer   │
│  Cryptographic Vault: WebCrypto API (AES-GCM-256)            │
│  Communications: WebRTC Mesh + DTLS/SRTP Media Rails        │
└─────────────────────────────────────────────────────────────┘
```

### 1.1 Core Technologies

* **Presentation Layer:** TanStack Router combined with React 18 concurrent rendering, providing seamless micro-page transitions without full browser reloads.
* **Component Design System:** Tailwind CSS paired with Radix UI headless primitives and Lucide icons, styled in the signature Kinbex **Electric Cobalt (`#0047FF`)** and **Radiant Gold (`#FFB800`)** color palette.
* **State & Data Synchronization:** TanStack Query client-side cache coupled with dedicated WebSocket workers, handling up to 10,000 tick updates per second without UI stutter.

***

## 2. Sovereign Cryptographic Key Enclave

Kinbex enforces strict non-custodial custody. Unlike custodial exchange terminals or Telegram bots, user credentials and seed phrases are never transmitted across the network.

### 2.1 Client-Side Key Generation & Encryption

* **Entropy Generation:** Cryptographically secure pseudorandom numbers generated via the browser `window.crypto.getRandomValues` WebCrypto API.
* **Symmetric Encryption:** Private keys and mnemonic seed phrases are encrypted using **AES-GCM-256** with unique initialization vectors (IVs) derived via PBKDF2 with 100,000 iterations.
* **Multi-Chain Signing Support:**
  * **EVM Chains:** Ethereum, BNB Chain, Base, Arbitrum (secp256k1 curves).
  * **Solana:** Ed25519 high-velocity transaction signing.
  * **TON:** Telegram Open Network multi-chain signer.

```mermaid
sequenceDiagram
    participant User
    participant Client Enclave
    participant Blockchain RPC

    User->>Client Enclave: Input Master PIN / Biometrics
    Client Enclave->>Client Enclave: Decrypt Private Key via AES-GCM-256
    Client Enclave->>Client Enclave: Sign Transaction Hash Client-Side
    Client Enclave->>Blockchain RPC: Broadcast Signed Raw Payload
    Blockchain RPC-->>Client Enclave: Return Block Transaction Hash
    Client Enclave-->>User: Instant Confirmation & Multiplier Tracking
```

{% hint style="info" %}
**Zero Server Knowledge:**\
At no point do Kinbex servers, backend APIs, or database clusters hold, log, or store unencrypted user private keys. Loss of device access requires the user to restore their wallet using their offline seed phrase.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kinbex.gitbook.io/kinbex-docs/part-ii-system-architecture/01-client-runtime-and-enclave.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.