Skip to main content
Status: Live — This feature is operational.

​
System Architecture Overview

The Render Network Protocol is a system for the Attention Economy. It consists of four primary components that work together to deliver verified engagement, autonomous stream operations, and on-chain settlement.

​
Components

​
1. Frontend

  • Role: User interface for the Arcade, wallet connection, and game launcher.
  • Game Integration: Games run in sandboxed iframes. An SDK bridges the frontend and each game’s internal state, enabling real-time communication between the protocol and gameplay.

​
2. Backend

  • Role: API service, database, and state management.
  • Key Models:
    • Cabinet: Represents a game instance. Stores possession metadata and schema for Alice’s interventions.
    • ArcadeState: Global settings (theme, music).
  • API: REST endpoints serving both the frontend and agent layer.

​
3. Economics (555x402)

  • Blockchain: Solana.
  • Role: Token management, rewards, payments, and settlement.
  • Integration: Alice can trigger economic events (airdrops, bounties) via backend integrations.

​
4. Agent (Alice)

  • Role: Autonomous operator — the “Ghost in the Machine”.
  • Capabilities:
    • Possession: Control game states via POSSESS_CABINET.
    • Memory: Learn from interactions via LOG_MEMORY.
    • Communication: Chat with users, post updates across platforms.

​
Data Flow

  1. User plays a game (Frontend).
  2. Game reports score/state to Backend.
  3. Alice (Agent) polls Backend for active cabinets.
  4. Alice decides to intervene (Possession).
  5. Alice sends POSSESS_CABINET command to Backend.
  6. Backend updates Cabinet state.
  7. Frontend (via SSE or polling) receives update and forwards to Game via the SDK.
  8. Game applies effect (e.g., God Mode).
  9. Alice observes result and calls LOG_MEMORY.