Signal
A signal is market or strategy information. It can inform a decision, but it is not itself permission to trade and does not mean an order was submitted.
automation and decision support
AI crypto trading dashboard with visible controls
The Stryx AI crypto trading dashboard helps configure and monitor supported bot services, execution controls and protective workflows while keeping authority and risk visible.
From signal to execution
Configured strategy
Parameters define how the selected automation workflow should respond. Review size, direction, thresholds, limits and protection settings exposed by that service.
Execution
Execution requires the relevant wallet, venue, balance and authority path. A connected wallet, configured rule and accepted order are separate states.
Readiness before activation
Wallet and permissions
Confirm the selected wallet, required venue authentication, builder approval or executor-wallet state shown for the workflow. Connecting a wallet alone does not authorize trading.
Balances and venue
Check available collateral, gas or funded executor balance where required, plus whether the selected venue and live route are responding.
Blockers and parameters
Resolve explicit blockers and read the configured strategy before pressing start. Paper and live modes, supported assets and control sets can differ by service.
Runtime status and intervention
Observe the reported state
Use runtime status, session mode, wallet binding, order state and service errors to distinguish running, stopped, blocked or stale conditions. A dashboard can lag an external venue.
Stop or resume where supported
Use the start, stop, pause, resume or unsubscribe controls exposed by the selected service. Confirm the resulting runtime state and inspect remaining orders and positions rather than assuming a button completed every external action.
Intervene when context changes
Intervene when permissions, balances, venue connectivity, prices, position size or strategy assumptions no longer match the intended run. Manual execution may be more suitable for a one-off order.
Unavailable services and imperfect execution
If a wallet, venue, API, data source or delegated runtime is unavailable, new actions can be blocked, delayed or rejected while displayed state becomes stale. Liquidity, spread, slippage, partial fills, volatility and timing can change the result. A fixed stop or trailing instruction is a trigger-and-execution workflow, not a guaranteed fill or price.
Frequently asked questions
What does a crypto trading automation dashboard control?
It presents the configuration, readiness, runtime state and intervention controls exposed by a supported automation service.
Does connecting a wallet authorize trading?
No. Connection identifies the active wallet context; an approval, signature or supported delegation is a separate action.
What is delegated execution?
Where supported, a separate executor role can submit permitted actions for a configured workflow after the required authority is established.
Can a bot guarantee a stop-loss exit?
No. Liquidity, slippage, volatility, rejected orders, timing and venue availability can affect or prevent a fill after a trigger.
What should a user check before starting automation?
Check wallet and venue readiness, balances, permissions, strategy parameters, blockers, current exposure and the service-specific stop or recovery path.
How can automation be stopped?
Use the stop, pause or unsubscribe control exposed by that service where supported, then confirm runtime state and any remaining orders or positions.