Oasis × ROFL × Hyperliquid — Telegram Trading Agent

Oasis - Trading Bot

What it can do.

Agent registration on Oasis Sapphire (testnet):
- Stores agent metadata and encrypted strategies on a confidential EVM (Sapphire).
- Strategy bytes encrypted with AES‑GCM, keys managed via ROFL enclave.
Telegram onboarding & control:
- One chat for connect wallets, **set risk, **trade, and **track portfolio.
- Manual mode (place trades from latest signal) or Auto‑trade (polls signals every 30 min).
Hyperliquid integration:
- Place/manage perps orders using user’s API wallet; track positions on **API + Main wallets.
TEE‑backed secret handling (ROFL):
- User pastes HL API secret & wallet addresses once; bot calls ROFL Gateway → ROFL TEE app to encrypt/decrypt.
- Bot/database only ever store ciphertexts; decryption occurs **inside the enclave on demand.
Risk & portfolio tools:
- Apply ZkAGI defaults or set leverage/size caps; unified balances & open positions.

Secrets are end‑to‑end encrypted before persistence; only ROFL enclave holds keys.
Least‑privilege: API keys scoped to HL perps; operational errors are redacted in chat.
Users are prompted to delete sensitive messages after onboarding.

Policy‑as‑proof: ZK attestations that trades respect user risk limits (leverage/size) without revealing positions.
Account abstraction: Wallet‑less onboarding via session keys; bundled tx on Sapphire.
Multi‑venue routing: Extend beyond Hyperliquid to additional perps/spot venues with best‑execution logic.
Strategy marketplace: Publish encrypted strategies with verifiable performance hashes; users opt‑in to auto‑follow.
Invariant guards: On‑chain or enclave checks for max drawdown / VaR before order submission.
Compliance hooks: Export auditable trails (hash‑chained) without revealing user PII or raw orders.
Mobile PWA: Client‑side signing and optional local MPC shares for API keys.