↦ Arbitrage Bot

Select which pairs the bot scans and trades. Only pairs available on both exchanges are shown.

Gross and net (after fees) spread for every enabled route across all exchanges.

Each limit route is enabled per ROW, not per platform — a row disabled at row level renders "disabled" regardless of the platform's own state. Each platform also has a Monitoring switch (whether the engine connects to it at all; a separate gate applied on top of the row flags below) and a one-click Disable limit routes action — a convenience that turns off every currently-enabled route touching that platform, and never turns one on. Re-enabling a route is always an individual click on its own row in the expandable list under each platform. A route is evaluated only when its row is enabled, both its platforms are monitored, it is supported on both legs, and its adapters are ready. The table below is read-only; use the per-platform controls above it to change enablement. The OTC route has its own toggle on the Runtime Config tab's OTC Desk card (operator-only) and is unaffected by these controls.

The date range below filters both this P&L summary and the Trade History table. "Today's P&L" always reflects today regardless of the range.

Every window the market showed at your configured trade size, traded or not. Blocked rows are windows your balances or the order book could not take; their figures are at the configured size and never count as viable capacity, and they appear only when the window cleared your spread threshold.

Total size deployed per arbitrage window. A window opens on the first trade and spans the selected length (a 12:21 trade with a 1-hour window covers 12:21–13:21); the first trade after it closes opens the next window. Size = executed buy notional (MYR) per arb.

The spread charges every trade a transfer fee as if it moved its own funds back. In reality OTC returns come home in one on-chain move and the desk is settled by one bank transfer, so the REAL fee is recorded when you settle. Every row here is bound to the settlement that created it: Mark all complete or Mark complete on a transfer (the on-chain or bank fee, against those transfer ids) and Record settlement on the desk credit (the Luno withdrawal fee and the bank fee, against that ledger entry). Nothing is typed in here directly; a wrong row is voided on this table and re-entered from its settlement on the Inventory tab. The P&L above shows actual against assumed and nets the actual figure.

Exchange verification is required before the halted engine can resume.

One card per coin — loading…. Enter each deposit as the exchange shows it (amount, price, fee); the ledger works out what you hold and what it cost. Observation only.

Auto transfers resolve themselves; manual rows need you to move funds and then mark them complete. OTC return rows do NOT halt trading — let them accumulate, then settle the batch in one move.

Credit drawn from the Sinegy InstaTrade desk. Settled in two legs — Luno → bank (a MYR withdrawal you make by hand; Luno charges a fee) and bank → Sinegy (you pay the desk). Record each payment once, with both fees, so the outstanding figure and the real settlement cost stay true. At 100% the OTC route stops being executable (the bot pauses that route and keeps scanning; it does not halt).

While Dry Run is on, the bot evaluates and logs every trade but places no orders and makes no withdrawals. The one exception is the admin's Test withdrawal (RM1) in Settings → Luno MYR Auto-Withdrawal, which always sends real money. Switch Dry Run off only after you have checked the API keys, fees and balances. The change applies from the next engine cycle, with no restart.

Taker fees per (exchange, pair) used in spread math. A manual row is locked — the engine never overwrites it. An api row is auto-seeded from the exchange's fee API on each engine boot. Editing a row locks it (manual); use Set auto / Lock in the Source column to switch modes (auto is only available for exchanges with a fee API).

Which kind of arbitrage the engine evaluates. Exactly one at a time, applied on the next engine cycle — no restart. Your per-route enable switches are never changed by this, so switching back restores the same selection.

Sell BTC at Luno, buy it back at the Sinegy InstaTrade desk on credit. The route needs all of: both exchanges enabled, this toggle on, a desk fee below, and a positive otc_credit_limit_myr. The desk fee is operator-entered — Sinegy has no fee API — and a missing row means the route is never evaluated (0 is a valid fee, a missing row is not). Every OTC arb ends with a manual Sinegy→Luno return transfer, which does not halt trading: the rows accumulate while the bot keeps trading, and you settle the desk, bring the coins home in one move, then Mark all complete on Transfers.

Last 300 lines from logs/engine.log. Refreshes on demand.

Logs will appear here once the engine is started.

Exercises the adapter endpoints on this bot's loopback listener and shows the raw results. The key auto-fills from the bot; enable/disable/stop change the run state and ask to confirm.