Answers first, then the issue tracker
The answers below describe what the code actually does, not what a settings page says. If yours is not here, the channels underneath reach the maintainer — in public for bugs and questions, privately for anything security-related.
Before a key is stored, the exchange is asked what the key may do. A key that can withdraw funds or transfer them to another account — or whose permissions the exchange will not confirm — is refused and nothing is saved. Create a new key with trading enabled and withdrawals and transfers disabled. A key that later gains one of those permissions is revoked the next time it is checked.
New entries pause while the market data is older than its timeframe allows, rather than trading on a gap. It clears by itself when fresh closed candles arrive; after a reconnect, missed candles are replayed in order first. Whether the feed is up is on the status page. Exits and protective stops on open paper positions are not blocked by it.
Several limits halt new entries on their own: the drawdown circuit breaker, the daily and weekly loss limits, the cooldown after consecutive losses, the trades-per-day cap, the trading-session and trading-day windows, economic-event blackouts, and stale market data. Each rejection carries a code such as DAILY_LOSS_LIMIT or EVENT_BLACKOUT. Exits are never blocked by any of them.
Every decision is recorded, rejected ones included, with the rule that blocked it and the reason it gave — for example INSUFFICIENT_RR, CORRELATED_EXPOSURE or PORTFOLIO_EXPOSURE. Look the decision up in the dashboard, or through GET /v1/decisions with verdict=rejected. For several of these rules the platform also follows the blocked trade as a virtual one, so you can see what the rule cost or saved.
Backtests run the code that is deployed now, so a change to a strategy or to the cost model changes historical results too. Results are not pinned to a code version: to compare, note the commit that produced each run, and check the repository history for what changed between them.
From the profile menu: your account data as JSON and your trade history as CSV. For everything, Settings → Security → Backups takes a snapshot of every database once a day and on demand — encrypted when the vault master key is set — and can check that the latest one actually restores. The audit log downloads from the same page.
The software is MIT-licensed and free to run yourself; the whole platform is in the public repository. Exchange fees, funding and spread are charged by the venue — and live order routing is locked today, so every strategy trades on a paper account.
Sign in with one of the recovery codes you were shown when you turned two-factor on. If those are gone too, only whoever runs the server can restore access — there is no shortcut, because this account can hold exchange credentials. Revoke your exchange keys at the venue in the meantime.
Reaching the maintainer
GitHub issues
Bugs, questions and proposals, in public, on the repository. The issue form asks for what is needed to reproduce the problem. Leave keys and account identifiers out.
Public · answered by the maintainer
Security report
Privately, through GitHub's Report a vulnerability form. Only the maintainer and you can see it. Never open a public issue for a vulnerability.
Private
Status page
Whether the API, the workers, market data and the database are up right now, and every incident in the last 90 days — measured every minute, not written by hand.
Live
Where to take it
There is no staffed support desk and no response-time guarantee: the platform is maintained in the open, and issues are answered by the maintainer as they arrive. What is guaranteed is in the code — limits that halt trading on their own, and a status page that is measured rather than written.
- Positions need to stop nowPause trading from the dashboard, then check the status page
- A vulnerabilityPrivate security report — never a public issue
- Something is brokenA GitHub issue, with the steps to reproduce it
- A question or an ideaA GitHub issue; ideas use the proposal form
If trading is impaired right now, check the status page first — an incident already being worked on is faster to read about than to report. For anything about how a decision was made, the documentation covers the vocabulary the answers use.