Coinsori
تسجيل الدخول
About coinsoriMarket data & premiumCommunity & newsGetting started with tradingSecurity — non-custodialLocal agentStrategy API (ctx)AI Strategy WizardFor AI assistants

Getting started with trading

Recommended path: paper → backtest → live.

1. Paper trading

Practice with virtual funds on real prices and orderbooks. Wallets are separated per exchange (same shape as live), with realistic fees and slippage. Deposit/reset/transfer via the wallet's fund management.

2. Strategy studio

A strategy is a single JavaScript function onUpdate(ctx). The editor has autocompletion, and the full API is in the strategy API docs. The AI-prompt button builds a prompt to paste into ChatGPT/Claude — coinsori never calls AI for you (always verify generated code with a backtest).

3. Backtest

Runs your strategy over historical candles with the exact same ctx interface. The orderbook is synthesized from candle volatility, so treat slippage as an estimate.

Dev notes — version control for your strategy

Select a strategy in the studio and open the Dev notes tab. Entries from the AI (automated development) and from you stack up in order, and every entry stores the code as of that moment — the timeline IS the version history. Backtest history keeps a per-job code snapshot too.

The three buttons on each entry:

  • Code — read-only view of that version. Nothing changes.
  • Load into editor — puts that version into the editor temporarily. Your saved strategy is untouched; run a backtest on it right away. It disappears when you switch strategies or reload (temporary until saved).
  • Restore this code — overwrites the saved strategy with that version. Use it when the AI broke the code; the restore itself is recorded in the notes, so history never breaks.

In short: just looking = Code, try it = Load into editor, real recovery = Restore.

4. Live deployment

Install the agent on your own server (agent docs) and deploy. Default is dry-run; live orders require guardrail consent + the live switch + a registered API key. A fee-aware loss kill-switch stops the strategy automatically.

Caps vs. returns — a common misreading: live default caps are deliberately conservative (e.g. KRW total exposure 300k). Even with 10M in the account, the strategy only works up to the cap — so low account-wide returns may be the cap, not the strategy. Read performance against exposure. Raise the caps at deploy time once you trust the strategy; the low default is intentional damage-limiting for your first live runs. Paper defaults to your full paper cash, so validation isn't distorted.