Get the app

What's new in 2.3.0

2.2.0 was about what the chart says. 2.3.0 is about what your account can do: two new venues, a wallet, a Balances tab that reports what your holdings are worth rather than how many you have, short selling restored with the collateral that makes it honest, and every control on the order ticket audited against what your broker can actually do. For the full engineering changelog, see the v2.3.0 release notes on GitHub (opens in new tab).

You can short again, and the account does the arithmetic that makes it honest

Short selling was withdrawn in 2.2.0 — it was offered and it did not work. It is back in paper trading at 1×, modelled properly. Selling something you do not own means somebody lent it to you and you owe it back at whatever it ends up costing, so the sale proceeds are locked and an equal amount of margin is locked beside them.

• You are told what a short costs to open, what it is worth now, and how far price can go against you before the position is liquidated — because a short that cannot say where it dies is not a short, it is a trap.
• Leverage is still withheld. Paper trading is 1× and the leverage selector does not render, because borrowing beyond your collateral is not modelled yet. Nothing on screen promises something the account cannot do.
• Available in the free browser account (opens in a new tab) and on the desktop, wherever paper trading runs.

Two new venues

• Gemini — US-regulated, with spot market data, the order book, and trading, and its sandbox reachable through paper mode. This one was verified live against a real key, which found two things no offline test could see: the nonce has to be in seconds, and sandbox keys are master-scoped and need the account named in every payload. Both fixed the same hour.
• Kraken Futures, which is its own venue rather than a setting on Kraken — different host, different signing, and its own API keys minted somewhere else entirely. Folding it into Kraken would have meant one credential slot holding two credentials, and you would have met that as an authentication failure with no explanation.

That makes sixteen trading venues and seventeen analytics data sources. Both new venues need your own API key, so they live in the desktop app.

The Balances tab can say what your account is worth

It used to show quantities — asset, free, locked — and no values at all. Now: what each holding is worth, the total, what share of the account each one is, and the day’s change. Those are the numbers that answer “how am I doing”, and they were the ones missing. An asset that cannot be priced says “unpriced” and the total says it is partial — a missing price is never quietly counted as zero.

Deposit addresses, read out properly

Ask for a deposit address and it arrives in a read-only field with a copy button, which means your screen reader’s review cursor and your braille display walk it character by character without anything special from us. The address is checksum-verified before you ever see it, and case survives the trip — which matters, because for some networks the capitals are the checksum. Kraken is the first venue behind it. It needs your own API key, so it is a desktop feature.

Every control on the order ticket answers to what your broker can actually do

The capability surface was audited against reality rather than against its own documentation, and it was wrong in both directions — claiming things providers could not do, and hiding things they could. Now: if a control is there, the venue supports it; where it isn’t, it is absent or disabled with a reason, never present and inert. A test now fails the build if a new venue is added without declaring what it can do.

Two fixes worth naming

• Adding an API key kept insisting you needed an API key. Add a key, activate it, and the symbol list went on saying “API key required” for the very provider you had just supplied — until you restarted the app. Found by using the terminal rather than by a test, which is its own lesson.
• An empty list stops meaning five different things. “Nothing here”, “we could not reach the venue” and “your key cannot read this” now read as what they are.

Not in this release, deliberately: moving funds off a venue

The withdrawal path is built and pinned by tests, and no one has yet run a real withdrawal with it. That is the one place in this terminal where being wrong loses money directly rather than through a trade, so it ships switched off: the button does not render, and the code refuses before any request could leave your machine. It stays off until it has been driven end to end against a live venue. You will read about it here when it is on, not before.

Everything from the 2.2, 2.1 and 2.0 lines

Nothing was removed, and the previous release’s headline work is unchanged:

• The chart names its own shapes (2.2.0). Twelve formations announced as you move through them — with the neckline, the measured target, which edge you walked in from, and, at the bar it resolves, what price actually did: “confirmed here: closed below the neckline at 42,100”, or “ends here without confirming”. Nested and overlapping shapes say so rather than being silently reduced to one.
• Place a trade from the chart in three keystrokes (2.2.0). Ctrl+Alt+Shift+1/2/3 arms a risk percentage, Ctrl+Alt+Shift+X sets the stop from the bar you are on, then Shift+Enter for a limit or Ctrl+Enter to go now — with the position size worked out and spoken, and a reminder on every bar that you are armed.
• Your open trades stay live in tabs you are not looking at (2.2.0). Stops fire and limit orders fill wherever the trade is, whether or not its tab is open, and whether or not background monitoring is on.
• The paper account cannot reach an impossible state (2.2.0). Six defects found and pinned by tests — unlinked brackets, selling what you did not hold, a resting buy filling into negative cash, assets missing from Balances. A refused order says why, not just “rejected”.
• Editable stop-loss and take-profit columns (2.2.0), each value checked before it is sent, because several venues will accept a stop on the wrong side and trigger it instantly.
• Watchlists and the screener, the respect report (Alt+R), Market Structure, Value Deviation, bar replay, split view, the twelve themes and the theme editor all arrived in 2.1 and are unchanged.
• 2.0’s foundation is still underneath: every exchange on a direct API, order results that can never go silent, background monitoring that cannot die quietly, alerts that fire with the browser closed, and native bracket orders on Tradier and Schwab.

The test suite stands at 3,239 tests, all green — and a guard now fails the build if a new trading venue is added without declaring, in code, exactly what it can and cannot do.

Known limitations, stated plainly: withdrawals are built but switched off until one has been run end to end against a live venue (see above). Kraken Futures’ request signing is verified against Kraken’s own documented example rather than against Kraken itself — its test venue was decommissioned in July and there is nothing left to sign up for. Kraken deposit addresses are read, not created, so the first address for an asset has to be generated once on kraken.com. Coinbase live candles still don’t report volume, though historical bars do, and Schwab’s real-time account stream awaits Schwab developer-app approval. None of these affects charting or order placement.

Questions or issues? See the User Manual and Quick Start Guide.