Execution
RISEx trading terminal for the SypherScore workflow
The Trade tab connects discovery and validation to a guarded RISEx mainnet interface while keeping sensitive signing flow browser-local.
How the terminal is designed
SypherScore's RISEx terminal is built as a trading surface for users who already found a route in the scanner and want to review RISEx market data in the same product environment.
The backend is intentionally limited to proxy and validation work. It does not request, store, or log a main wallet private key, and it does not sign orders for the user.
- Session signer state belongs in the browser session.
- Main wallet private keys should never be entered into SypherScore.
- Order intent remains user-controlled.
Where it fits in funding arbitrage
A RISEx route can appear in AI Top Pairs, be checked through historical context, and then reviewed in the terminal. The terminal is one part of the workflow, not a replacement for risk controls.
- Use scanner first.
- Validate the route.
- Open the terminal only when the route still makes sense.
Does SypherScore need my main wallet private key?
No. Never provide a main wallet private key. The backend is only a proxy/validation layer and does not sign orders.
Why does RISEx access use invite codes?
RISEx access can be invite-gated. SypherScore can surface invite-code access in the terminal workflow when codes are available.