Прављење сервера ↗Упутство са снимцима екрана: сервер (VPS) за ваше стратегије за 5–10 минута — на 10 језикаСпољна база SupabaseНаправите бесплатни Postgres и повежите га налогом само за читањеУчитавање јавних податакаУчитајте бесплатне податке као што су страх и похлепа, хешрејт, каматне стопе и друго у своју базу и користите их у стратегијамаБуђење у реалном времену преко RedisСтратегија реагује оног тренутка када стигне нова вредност — сопствена инсталација, више сервера или бесплатна управљана услугаПочетак са forex (MT5)Бектест на MT5 рачуну вашег брокера и покретање у симулацији → демо → реални рачунРегистрација уређаја за заштиту кодаКако одредити и проверити који уређаји могу да отворе заштићено сачувани код стратегијеWhen your agent goes offlineMove to a new server and reconnect keys and runs after the server stops or is reclaimedP2P WebSocket API (на енглеском) ↗Повежите свој бот или скрипту са P2P демоном и примајте потврђене сигнале WATCH TOGETHER — клијенти за JavaScript и Python
▶ Step-by-step videos (YouTube) ↗

Follow along from install to your first strategy. The YouTube playlist opens in a new tab.

Security — non-custodial

One-line principle

Both decision and execution (keys, signing, submission) happen on the agent on your device. soritrading servers are not in the trade path.

  • API keys never go to soritrading servers. Orders are signed and sent by your agent directly to the exchange.
  • The server holds no keys, so it cannot place orders at the exchange itself, and it does not place orders on your behalf.
  • Even if the soritrading backend is compromised, the server alone cannot command your agent — the agent only accepts connections signed by your trusted device.

What this does not stop — honestly

We do not say "absolutely safe". The remaining risks:

  • Malware on your own device (browser) · phishing sites — commands are signed on your trusted device, so whoever controls that device or screen can send them. Check the official domain in the address bar.
  • If the key itself is stolen, it can be used without our software. All that is left then are the limits the exchange put on the key (no withdrawal permission · IP restriction) — turn on IP restriction where the exchange supports it.
  • If your own server (VPS) is compromised — that is your responsibility.

E2E encrypted remote control

Commands from your browser to the agent (key registration · turning live orders on · remote control) travel with end-to-end encryption (ECDH P-256 + AES-256-GCM). The server relays ciphertext it cannot read. If the web UI and the agent show the same fingerprint, there is no one in the middle.

The scope, too: this encryption covers commands. Fills, balances, performance and logs that the agent reports to the server are received and stored by the server so the screens can show them.

Key safeguards

  • Keys without withdrawal permission are recommended. When registering a key, the agent asks the exchange about its permissions where it can, and a key with withdrawal enabled is registered only after a warning and your explicit consent (older agents reject it). Where the exchange cannot be asked, it shows "could not verify" (never drawn as safe). Either way the agent blocks withdrawal and transfer calls before they reach the network, but if the key leaks, whoever holds it can withdraw — which is why we recommend no-withdrawal keys.
  • Keys are stored encrypted only on the agent's machine. You can also enter them directly on your server (VPS) without going through the web (agent console command).
  • Exchanges that cannot separate withdrawal (e.g. decentralised exchanges signed with a wallet key) are supported too. In that case the key form warns you and asks for explicit consent, and the agent is designed to use only trading functions (orders, balances, positions) and block withdrawals and transfers. The key stays only on the agent, like any other key.
  • For decentralised exchanges a delegated key (a trade-only API key or agent wallet you approve from your own wallet on the exchange) comes first. Only where there is none do we take the private key of a dedicated wallet that holds just your trading funds. We never take seed phrases — anything that looks like a seed is blocked by the web before sending, and refused by the agent too. A Hyperliquid main wallet key is accepted after a warning and your consent, but not recommended — it can sign withdrawals, transfers and assets on other EVM chains that use the same key, so we recommend a delegated key (API wallet); the agent signs only trading actions.

Guardrails

Real orders need a wallet size (= the most it can lose) and live orders turned on separately. Order-rate limits, approval ceilings and manual stop still apply.

Security of your own server (VPS) is your responsibility. Keys without withdrawal permission are recommended; turn on IP restriction where the exchange supports it.
soritrading
Почните једноставно уз имејл