You can lose everything allocated
Digital assets are volatile. Copying a wallet, following a model or executing quickly does not make a trade safe or profitable. There is no configuration — fee level, provider tier, strategy type — that removes this risk.
Execution is not guaranteed
Same-block or first-block outcomes are engineering objectives, not promises. Congestion, validator behaviour, RPC latency, relays, priority fees, slippage, failed simulation, reorgs and competing traffic all affect results.
Latency and fill quality vary per operator deployment; benchmark from your own environment before relying on any throughput assumption.
Strategy risk
A source wallet may be wrong, manipulated, compromised or acting through connected wallets you cannot observe. Historical behaviour and confidence scores do not predict future performance.
- Copy targets can reverse direction without warning.
- Confidence scores describe model agreement, not probability of profit.
- Manipulated source activity is a real and documented market pattern.
Operational risk
Software bugs, stale data, provider outages, leaked credentials, incorrect configuration and smart-contract vulnerabilities may cause losses. Begin in dry-run mode and use a dedicated limited-balance hot wallet.
Token separation
No token can guarantee bot access, execution quality, profit or protection from losses. Check the official token status before trusting any contract.
Risk limits you control
- Daily loss cap — hard stop after a threshold, enforced client-side.
- Volume cap — bounds exposure per day regardless of signal count.
- Explicit priority-fee budgets — never open-ended.
- Per-strategy enablement — execution is granular, not all-or-nothing.
These controls restrict what the engine may do; they do not make trading safe. Only committed-capital sizing does that.