Vesper
Execution

RISEx trading terminal: sessions, orders and access

Move from funding research to the RISEx order interface with a clear distinction between wallet access, session authorization and the state of your orders. Connecting is not proof that a trade is ready or safe.

Mainnetverify the selected network
24hregistration requested by current code
Separatelocal clearing and venue revocation
01

From research to the terminal

Use the DEX Radar to research routes and the backtester guide to understand historical estimates. The RISEx terminal is a separate order interface, not a guarantee that both legs of an arbitrage will execute together.

Check current account eligibility, any access or invite requirement, the network and the selected market. Confirm contract size, price increments, margin and available balance before an order. Do not enter a seed phrase or main-wallet private key into a website.

02

What the browser session does

The terminal code creates a session signer in the browser and stores its key in sessionStorage. Registration uses an EIP-712 authorization from the account wallet and a separate signature from the session signer. The reviewed code requests an expiry 24 hours after registration; this is not proof that every registration succeeds or that an existing key has that lifetime.

The terminal signs supported actions in the browser and sends signed requests through backend validation/proxy routes. This describes this terminal path, not every SypherScore product. Review the actual authorization and any further permit or budget request; a session key is still sensitive, and trading permissions can cause losses even without a withdrawal operation.

03

Reloading or closing the browser

Restoration depends on available browser-session data, the same account and network, and a current active-key check. A closed tab, cleared storage, expiry or revoked key can require a new authorization. Do not assume that reopening always restores trading.

Clearing browser data is not revocation at the venue. Closing the browser is not an order cancellation or position close. Accepted orders can fill, expire or be cancelled, and positions remain exposed to funding and liquidation under venue rules while you are offline. Reconcile the live order, fill and position records when reconnecting.

04

Three separate checks when ending a session

First review open orders and cancel those you no longer intend to keep; verify the result rather than relying only on a submitted request. If you want no exposure, separately reduce or close positions and verify both positions and remaining orders. A cancellation does not undo an earlier fill.

To remove signing authority, use the venue-supported revocation flow and verify the key status. Official documentation describes an account-signed revocation; this guide does not claim that the SypherScore terminal provides a one-click revoke button. Key expiry or revocation is not evidence that existing positions or orders are gone.

05

Execution costs and two-leg risk

Depth and prices can change between research and order submission. Allow for partial fills, leg timing, fees, spread, slippage and funding on each venue. A quoted rate or estimate is not the realized cost, and a single-venue terminal is not proof of synchronized cross-venue execution.

A reduce-only setting limits an order’s intent under venue rules; it does not guarantee acceptance, a fill or an immediate flat account. Confirm results from current records. This guide offers no guaranteed return, fixed loss cap or recommended leverage.

06

Sources and review scope

Reviewed 26 September 2026 against the public terminal source and official documentation. This is a guide, not a security audit or verification of any account. Documentation examples may use testnet; check the selected network and current venue requirements.

Questions

Questions

Does the terminal need my main-wallet private key?

No such key or seed phrase should be entered. The reviewed browser path uses wallet signatures and a separate session signer; this is not a platform-wide custody or security certification.

Does every session last exactly 24 hours?

The reviewed terminal code requests a 24-hour registration. Acceptance, the actual key status and its recorded expiry must still be checked; an existing key may have different conditions.

Does closing the browser stop trading exposure?

No. Browser closure does not cancel accepted orders or close positions. Venue state can change while you are offline, so reconcile orders, fills and positions when reconnecting.

Is clearing the saved signer the same as revoking it?

No. Local clearing removes browser state. Venue revocation is a separate authorized action, followed by a status check; neither alone proves the account is flat or orderless.

Can the terminal be used without the scanner?

The terminal and research tools serve separate purposes. A scanner suggestion is not required for the guide’s workflow and does not authorize a trade or guarantee a two-leg fill.

Related SypherScore pages