# 3. Core Architecture & Capabilities

**1. The Kinetic Node Layer**

* **Native Core Daemon (Pro):** A background service for Windows/macOS/Linux users with powerful GPUs. Handles heavy workloads like LLM training subsets and 3D rendering.
* **Browser Extension (Light):** A "plug-and-play" node for casual users, handling lightweight data validation and web scraping tasks during browsing sessions.
* **Telegram Compute Bot (Social):** A revolutionary Mini-dApp integrated directly into Telegram. It allows users to contribute CPU cycles via a streamlined UI, merging social onboarding with infrastructure participation.

**2. Verifiable Workload Engine**

* **WASM Sandboxing:** All tasks execute within WebAssembly (WASM) environments. This ensures that the code running on your machine is strictly isolated from your OS, guaranteeing 100% security for the host device.
* **Proof of Compute (PoC):** A consensus mechanism where nodes cryptographically prove they performed the assigned work correctly.
* **Privacy-First:** User data never leaves the local environment; only the computation results are transmitted.

**3. Dynamic Dispatcher**

* **Intelligent Routing:** The protocol assesses node reputation, bandwidth, and hardware specs (e.g., VRAM availability) to route tasks to the most efficient provider.
* **Latency Optimization:** Workloads are matched to nodes geographically closer to the data source to minimize lag.

**Supported Task Categories**

* **AI Inference:** Running queries on pre-trained models (e.g., Llama, Stable Diffusion).
* **ZK-Proof Generation:** Outsourcing the heavy math required for Zero-Knowledge Rollups.
* **Data Processing:** ETL (Extract, Transform, Load) tasks for big data analysis.
* **Web3 Validation:** RPC request handling and blockchain indexing.

**Security Architecture**

* **Smart Contract Audits:** All Ethereum contracts governing rewards and staking undergo multiple external audits.
* **Slashing Conditions:** Malicious nodes attempting to submit false data face immediate slashing of their staked $KNTC.
* **End-to-End Encryption:** Data in transit is encrypted, ensuring requestor privacy.


---

# Agent Instructions: 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:

```
GET https://docs.kntctoken.xyz/3.-core-architecture-and-capabilities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.