Known limitations

Every candle on a venue chart is the bar the venue itself drew, with the same closes, wicks and boundaries. The EdgeVault Index is a composite EdgeVault builds itself. Timeframes a venue does not serve natively are disabled in the picker rather than built from a guess.

If a live price or candle feed drops, the chart and order-book readings are marked as dropped, with the time since the last reading, rather than left looking current. Position and account figures are not on this check yet, which is listed below rather than left for you to find.

Live execution is not switched on yet. When it is on, orders placed from the terminal on Phoenix are real, signed in your own wallet, and non-custodial. Nothing fires before your wallet approves it. Phoenix perps are still in private beta at Phoenix, so placing one needs a wallet they have whitelisted; without that the venue rejects the order, not EdgeVault.

The full order form is there (market/limit, TP/SL, reduce-only, cross margin) but the submit button is disabled.

Read-only market data is live now.

The order form is there; submission disabled.

Book, DOM, chart and trades are Bulk mainnet. The order form does not submit. It refuses with one sentence, and nothing is sent.

The order form is there and does not send orders yet.

The order surface and the builder fee approval are built, and stay switched off until live execution opens.

The order form is there; submission disabled.

The order form is there; submission disabled.

A stop or take-profit you set on Phoenix is written on-chain into a Phoenix account. It works with EdgeVault down, your browser closed and your laptop off, because Phoenix evaluates it.

It cannot survive Phoenix halting or delisting the market, the Solana network halting, or the trigger firing into a book with no bid at that price.

EdgeVault's servers hold no wallet key. A trade-only key on this device signs orders, only if you switch that on. A linked venue account's trade-only key is used only for orders you place. That means no auto-exit from EdgeVault's servers, no auto-hedge, and no "EdgeVault closed it for you because your rule triggered". The venue's own conditional order is what protects you while you're away; EdgeVault's part is making that easy to set and showing you it's really there.

EdgeVault does not hold pre-signed transactions for you.

Your side, size, entry, and the liquidation price the venue last calculated stay on screen with a counter showing how old the reading is. Mark price, unrealised P&L and distance to liquidation disappear.

You see which venue is silent and for how long, which of your venues are still answering, and whether you have a stop resting at the silent one.

What EdgeVault cannot do is close a position at a venue that is not accepting orders.

Congested means your exit may need a higher fee and several attempts. Halted means nothing lands for anyone until validators restart the network, which has historically taken hours.

A venue can delist a market and force-settle positions at short notice. No terminal can prevent that.

What EdgeVault can do is notice the market has gone while you still hold it, and tell you.

Your venue-held stops keep working. Price alerts that run on EdgeVault's servers stop, and the alerts panel says so as soon as it can reach EdgeVault again. Your position is at the venue, not here, so you can always act at the venue directly.

The agent desk and live execution are built for a desk. The terminal has its own phone view, with the chart, positions and a read-only book, and it is exit-only unless you switch new orders on in settings. Everywhere else on a small screen you are pointed to the mobile dashboard.

Your sensitive content is encrypted in your browser first, while data a feature must read on the server is not. Section 6 of the Privacy Policy is the one list of both.

Privacy Policy, section 6 →

Turn server alerts on and your price levels are checked on a server, so they reach Telegram with every tab closed. If that checker stops or a venue feed drops, the alerts panel says so in plain words and names what it costs you. With server alerts off, alerts only fire while a tab is open. It will not show a healthy badge over a broken checker.

Alerts on Bulk are not checked on the server at all yet, so those stay tab-only and are labelled that way.

How alerts on the server are stored →

The dropped-feed marker above is wired into execution panels today. The rest of the terminal is being brought onto the same freshness check surface by surface.

EdgeVault is in early access. Names, prices and small paths may still move.