8. Risk, Safety & Disclaimers
Perpbot is a powerful tool. With that power comes risk. This section is intentionally blunt.
8.1 General Trading Risk
No financial advice Perpbot, its strategies, and any examples provided are not financial advice. Users must make their own decisions regarding risk tolerance, leverage, and capital allocation.
Loss of capital Trading perpetual futures with leverage is inherently risky. Any strategy—including those offered by Perpbot—can incur severe drawdowns or full loss of deposited capital.
Past performance ≠ future results Backtests, forward tests and live performance shown in dashboards or marketing material are illustrative only and do not guarantee future returns.
8.2 Execution & Automation Risk
Automation amplifies mistakes While automation removes emotional bias, it also means that a poorly configured strategy or mistaken parameter (e.g. incorrect leverage, quantity or symbol) can be executed many times and at high speed.
Infrastructure failures Outages or issues can occur at any layer of the stack:
TradingView alerts
Perpbot backend and Telegram bot
Aster / Hyperliquid APIs
Network connectivity or hardware failures
Perpbot will strive for robustness and safe defaults, but no uptime or execution guarantees can be made.
Exchange-side risk Exchanges may change APIs, enforce new restrictions, suffer outages, liquidations or solvency issues. Perpbot has no control over exchange operations.
8.3 Leverage & Liquidation Risk
Perps platforms allow high leverage. This magnifies both gains and losses.
Liquidation can occur quickly in volatile markets, especially for illiquid pairs or oversized positions.
Even with risk rules in place (break-even logic, SL/TP, time-based exits), slippage and gaps can cause exits to occur worse than expected.
Users should:
Use conservative leverage.
Start with smaller allocations while learning the tool.
Backtest strategies before going live.
8.4 Custody & API Safety
Perpbot is an automation layer, not a custodian:
Funds stay on the exchange (Aster, Hyperliquid, etc.), under the user’s account.
Perpbot uses API keys provided by the user to place and cancel orders.
Best practices:
Use dedicated API keys just for Perpbot.
Limit permissions to the minimum necessary (e.g. futures trading only; no withdrawals).
Whitelist the Perpbot server IP on the exchange when possible (Perpbot will prompt users to do this during setup).
Revoke API keys immediately if suspicious activity is suspected.
8.5 Smart Contract & On-Chain Risk
If and when Perpbot integrates on-chain smart contracts:
Smart contracts can contain bugs or vulnerabilities.
Bridges, oracles and DeFi protocols can be exploited or behave unexpectedly.
Users should be aware that on-chain integrations add an additional dimension of risk beyond centralized exchanges.
8.6 Legal & Regulatory Disclaimer
Perpbot does not operate as an investment manager, broker or advisor.
Users are responsible for complying with local regulations regarding derivatives trading, leverage and taxation.
The PERP token, strategy account and any revenue-sharing mechanisms do not constitute securities or guaranteed returns; they are mechanisms for aligning incentives within the ecosystem.
Last updated