Ecosystem Architecture

PolyOrbit operates as a non-custodial middleware layer that sits between the user, the blockchain, and the Polymarket protocol. The architecture is designed for speed, security, and transparency.

High-Level Data Flow

  1. User Interface (Web/Telegram): The user defines their strategy (the Chain) and signs a Session Key permission.

  2. PolyOrbit Engine (The Watchtower): This off-chain infrastructure monitors the Polymarket API 24/7 for specific resolution events and price conditions.

  3. Execution Module: Once a condition is met, the engine constructs the transaction payload.

  4. Blockchain Layer (Polygon): The transaction is broadcasted to the Polygon network using the user's Session Key.

  5. Polymarket Protocol: The smart contracts (CTF Exchange) execute the trade, redemption, or swap.

Architecture Diagram

The flow operates as follows:

  1. Configuration: User connects Wallet -> Generates Session Key -> Configures Chain Logic.

  2. Monitoring: The Watchtower Node polls the Polymarket CLOB API and Graph API for market resolution data.

  3. Trigger: Event Detected (e.g., "Market X Resolved YES").

  4. Action: The Executor Node uses the Session Key to call the Polymarket Proxy Contract.

  5. Settlement: Funds move directly from the Polymarket Smart Contract to the User Wallet (or back into the next Contract). PolyOrbit never holds user funds.

Technology Stack

  • Network: Polygon PoS (for low-cost, high-speed settlement).

  • Data Feed: Polymarket CLOB (Central Limit Order Book) API.

  • Auth: EIP-712 Signatures for secure, scoped session management.

PreviousKey FeaturesNextUse Cases

Last updated