Analysis
Market data and portfolio context help a user evaluate conditions. Reading data does not instruct a venue to trade.
Stryx Learn / automation controls
What is crypto trading automation?
Crypto trading automation is a rules-and-execution workflow. It combines configured conditions with a supported runtime and an authorized path for submitting actions; it is not simply a chart signal and it does not remove the need for oversight.
Analysis, signals, configuration and orders are different
Signal
A signal reports that a rule or indicator has matched. It can be stale, incomplete or unsuitable for the user’s current exposure.
Configuration
Strategy parameters describe intended behavior: for example size, direction, spacing, thresholds or a protective distance exposed by the service.
Order execution
An order requires a functioning runtime, sufficient balance, a supported venue and the necessary wallet signature or delegated execution authority.
A practical automation lifecycle
1. Configure
Choose the controls exposed by the selected workflow and verify they match the intended market, size and risk limits.
2. Authorize
Connect the relevant wallet, then complete any separate approval, signature, venue authentication or supported delegation the workflow requires.
3. Start
Resolve readiness blockers before activation. A start request can still be rejected if the wallet, balance, venue or runtime is unavailable.
4. Monitor and intervene
Watch runtime status, order responses, positions and errors. Intervene when actual state no longer matches the strategy assumptions.
5. Stop and verify
Use the service-specific stop, pause or unsubscribe control where supported, then confirm remaining orders, positions and authority separately.
Wallet approval and delegated execution
User wallet approval
A connected wallet provides identity and session context. A transaction approval or signature is a separate user action and may apply to one specific instruction.
Delegated execution where supported
An executor or delegated signer can provide a separate execution role for a configured workflow. Its exact scope, lifecycle, funding and recovery controls depend on the service.
Runtime status and blockers
A dashboard can show running, stopped, blocked or error state, but displayed state can become stale when an API, venue or runtime is unavailable. Review wallet binding, venue readiness, balances, permissions, configured parameters and current positions before relying on a status label.
Checklist before activation
Authority
- Correct connected wallet
- Required approval or delegation
- Known stop or intervention path
Execution context
- Supported venue and market
- Sufficient collateral or executor balance
- Current API and runtime availability
Risk context
- Position size and leverage
- Liquidity and slippage
- Existing orders and concentration