Frequently asked questions

An evaluation. You get a simulated account with a starting balance and a published rule set — a profit target, drawdown limits and a minimum number of trading days. Reach the target without breaking a limit and you pass, which qualifies you to trade a funded account for a share of the profit.

No. Every account is simulated and no order reaches an exchange. OrbitFx holds no client funds. What is real is the price: fills execute against a live index built from a median of major venues, so the market you are trading against is the actual market.

Nothing. Beta accounts are free while the rule parameters are being calibrated. Paid challenges open once calibration and the legal work are complete — and the price will be published before anyone is asked to pay it.

Crypto perpetual futures. The beta runs BTC/USDT and ETH/USDT, the pairs whose order-book parameters we have actually measured. More open as they are measured rather than estimated — the current list is always on the rules page.

The account stops immediately and becomes read-only: positions are frozen and no further orders are accepted. You are emailed, and the account page shows which rule ended it, at which tick, and at what price. The outcome is written to an append-only log that nobody — including us — can alter afterwards.

Not for your account. The rule set is pinned to it at creation and the account is evaluated under that version forever. If we publish better rules tomorrow, they apply to accounts created tomorrow. Your account page links to the exact terms it is judged by.

Equity, which includes unrealised profit and loss, fees, and funding charges. Funding is charged at the rate the venue actually settled, never a predicted one — a rate that never arrives is dropped with an audit event rather than being estimated.

Because the platform stopped being confident in the price. If venues disagree beyond tolerance, or feeds go stale, trading pauses for everyone until the index is sound again. A pause costs us volume; a breach computed from a doubtful price would cost you an account.

Deliberate execution latency, drawn from a published band, is the defence against latency arbitrage — trading against a price the platform has not caught up to yet. Without it, a simulated firm is drained by a handful of fast participants and everyone else pays for it. Ours is applied to every account identically, and the code that computes it cannot see whose order it is.

No. It derives from a per-order seed computed server-side under a secret you never see. A known delay is no delay at all, which is why the seed is never returned to the client and never accepted from it.

Open the evidence pack on your account page. It re-derives the fill from storage — the order with its seed, the recorded index history and the versioned execution config — and reproduces the price independently of whatever happened at the time. If the re-derivation disagrees with the fill, that is our error and we treat it as one.

No. There is no dealing desk and no counterparty — the accounts are simulated. Our revenue is challenge fees, which is exactly why the pass rate has to be a real number rather than a marketing one, and why the rules and the parameters behind them are published.

Yes. You can issue API keys from your dashboard and trade programmatically. A key acts as you, on your own accounts only, and goes through the same rules and the same execution delay as anything placed in the interface — there is no faster path.

No. Running one signal across multiple accounts — or holding opposite sides of the same instrument in two accounts so one necessarily passes — converts the evaluation into a lottery ticket rather than a measure of skill. We monitor for correlated fills across accounts and review what we find.

Both are fine. Crypto trades continuously and we do not restrict strategies that are simply profitable. What is restricted is conduct that games the evaluation structure itself rather than the market — the terms set that out.