Skip to content

Repository files navigation

Tesseract — Tap Trading on DCAI

tes Tesseract is a tap trading app for both web and mobile, where users place rapid positions on a live grid.
The product is built on DCAI L3 with account abstraction, session-authorized execution, and batched position opens so gameplay feels real-time while settlement and balances remain enforced onchain.

Table of Contents

Features

tes feature overview

Instant settlement feel

  • User signs once to activate a short-lived session.
  • Taps are accepted immediately and executed through batched onchain opens.
  • Chain latency is abstracted away from gameplay.

Account abstraction

  • Smart-wallet-first onboarding and execution.
  • Lower signing friction for frequent actions.
  • Better UX for both new and advanced users.

OpenClaw ready

tes openclaw

  • Agent-compatible architecture.
  • Installable skills can automate workflows around trading, ops, and analysis.
  • Clean extension points for autonomous strategy layers.

Leaderboard

tes leaderboard

  • Competitive ranking by PnL, consistency, and streak performance.
  • More interactive gameplay loop with repeat-session incentives.
  • Ready for seasons and tournament formats.

User Flow (What Users Experience)

  1. User connects/signs in.
  2. User deposits into vault balance.
  3. User taps grid blocks and sees positions appear instantly.
  4. User keeps trading without waiting on per-tap confirmations.
  5. User sees only final gameplay outcomes: live, won, lost.
  6. User climbs leaderboard and shares results.

System Flow (What Happens Behind the Scenes)

  1. Session Authorization
    • User grants short-lived signature authority for many taps.
  2. Intent to Position
    • Each tap is transformed into a signed position intent.
    • Intents are grouped for batch execution.
  3. Onchain Open (DCAI L3)
    • Batched transaction calls market open methods (openPositionBySig / batch variants).
    • TreasuryVault reserves required liability before final acceptance.
  4. Onchain Settlement
    • Settlement transaction resolves positions by rule (expiry/target path).
    • Payouts and retained losses are applied in contract state.
  5. Onchain Fee Routing
    • FeeRouter distributes protocol and treasury fees deterministically.
  6. Final State
    • Position status, user balance impact, vault accounting, and fee outcomes are all committed on DCAI L3 state.

How We Use DCAI

DCAI L3 is the execution and truth layer for the trading lifecycle. images (3)

  • TreasuryVault (Capital + Risk State)
    • Custodies deposited trading collateral.
    • Tracks internal balances and reserved liability.
    • Enforces withdrawability against outstanding risk.
  • TapTradingMarket (Trade State Machine)
    • Verifies authorized opens from signed/session-backed intents.
    • Stores position fields (stake, barrier, entry snapshot, expiry, multiplier).
    • Enforces open/close validity and settlement transitions.
    • Writes final win/loss outcomes as onchain state.
  • FeeRouter (Protocol Economics)
    • Applies fee policy at settlement points.
    • Routes fee shares to configured recipients with deterministic accounting.
  • Why this matters on L3
    • Fast, low-cost transaction environment suitable for high-frequency tap flow.
    • Core game economics (reserves, payouts, fees, outcomes) remain enforceable in contracts.
    • Auditable and replayable lifecycle from open to settlement at the chain-state level.

How We Solve DCAI Constraints (High Block Time)

DCAI confirmation cadence is slower than user tap cadence, so we separate interaction speed from finality:

  • One-time session authorization replaces full signing per tap.
  • Multiple taps are batch-opened in fewer onchain transactions.
  • Vault reserve accounting protects solvency before/at open.
  • Settlement commits final outcomes onchain in deterministic state transitions.
  • UX remains instant, while financial correctness remains anchored to L3 final state. tes constraints

Releases

Packages

Contributors

Languages