search

Strict Client-Side Execution (SCE)

Monkey OS radically departs from the traditional Web2 backend-frontend dichotomy. We employ Strict Client-Side Execution (SCE) to eliminate centralized attack vectors and custodial risk.

hashtag
2.1 The Non-Custodial Security Model

  1. Zero Backend Custody: Monkey OS does not possess a backend database. We do not store session tokens, OAuth keys, IP addresses, or raw transaction logs. The server only delivers static assets; the intelligence runs locally in your machine's volatile memory.

  2. In-Browser VFS (Virtual File System): Monkey OS simulates a complete desktop environment using a sandboxed Virtual File System. Applications (agents) communicate via an isolated, strictly typed in-memory event bus. When the browser tab is closed, the heap is flushed, and the session evaporates entirely.

  3. Transaction Formulation: The intelligent agents formulate raw, serialized Solana transactions (Transaction or VersionedTransaction buffers) locally. The LLM cortex determines the intent, but the deterministic payload generation happens within the client-side sandbox.

  4. Delegated Signing: The serialized buffer is passed to the user's injected wallet provider (e.g., Phantom, Solflare, Backpack) via the standard window.solana provider interface. Your keys, your signature, your execution. Monkey OS can never sign a transaction without explicit user approval via the wallet extension.

hashtag
2.2 Progressive Web App (PWA) Capabilities

Designed for high-frequency traders and mobile-first users, Monkey OS is fully responsive and supports PWA installation. Users can "install" the OS directly to their mobile home screens. This provides a native application experience with full hardware acceleration (WebGL/Canvas for the Sanctuary map) while strictly maintaining the security sandbox of the mobile browser environment.

Previous1.1 The Story of Punch and ClawdNextx402 Protocol

Last updated