Guides

Sign up, log in, what each page in the dashboard shows you, and a 30-second tour of /app.

The Botely autotrade feature works by approving a dedicated **agent wallet** (a separate keypair Botely generates) on your Hyperliquid account. Your main wallet stays in your custody.

How the Botely agent wallet is bounded, where its private key lives, what an attacker who compromised it could and could not do, and how revocation works.

Three independent ways to disable the agent: in-app per-strategy toggle, in-app master switch, or wallet-side revocation on Hyperliquid (the hardest stop).

The bot toggle in /app/settings has one aggregate master switch and two per-strategy switches (v6.4 + v7). The master is derived from the children — turning it off turns both children off.

The bot trades on YOUR main Hyperliquid account, signed by a agent wallet registered against YOUR wallet. Botely never holds your funds — they stay in your account the whole time.

MetaMask is the EVM wallet Botely's onboarding wizard expects. Install the extension once, then use it to sign actions on Hyperliquid — including approving your Botely agent wallet.

Either import an existing 12/24-word recovery phrase, or generate a fresh wallet inside MetaMask. Both produce a 0x... EVM address Botely can target on Hyperliquid.

Hyperliquid trades perpetuals against USDC. To fund your account you bridge USDC from Arbitrum (or another supported chain) into Hyperliquid's clearinghouse.

Botely migrated from dYdX v4 to Hyperliquid in May 2026. If you have USDC still parked on dYdX (a leftover trading balance from the legacy bot era), here's how to move it.

Connect a Ledger or Trezor through MetaMask to keep your main account key in a signing device. Signatures Botely's wizard requests are mediated by MetaMask — the device confirms the action physically.

MetaMask is the default in Botely's onboarding wizard, but any wallet that signs Hyperliquid's EIP-712 `approveAgent` action works. Common alternatives below.

v6.4 is the conservative baseline: long-only momentum on ETH/SOL/BNB with regime-aware entries, rolling 30-minute features, and per-coin TP/SL/max-hold.

v7 is the aggressive variant: adds short signals on SOL+BNB, Optuna-optimized parameters, and tighter exits. Higher trade count and higher backtest score, but more drawdown risk.

Three exit gates fire whichever comes first: take-profit, stop-loss, or a hard time limit. Conceptual primer — no formulas.

The /app chart plots the running sum of every closed trade's net P&L in USD. Real numbers from your account — not a simulated $1000 backtest.

The backtest page shows per-coin per-year P&L grids, drawdown timelines, and the out-of-sample split. Quick reference for what each panel means.

Walk-forward backtests are the best evidence we have, but live markets shift in ways no historical sample fully captures. Read this before drawing conclusions from any chart on the /backtest page.

Real-time signals with HMAC-signed webhook delivery, plus optional non-custodial autotrade on your Hyperliquid agent wallet up to a $5,000 capital cap.

Same delivery and optional non-custodial autotrade as Standard, with a higher $20,000 capital cap for larger portfolios. Includes CSV history download and priority support.

Botely's core product is verified algorithmic signals (advisory). On paid tiers you can additionally enable optional non-custodial autotrade — the bot signs orders on your Hyperliquid agent wallet for the three whitelisted markets (ETH/SOL/BNB). It's not trading-as-a-service; you stay in custody and you keep the kill-switch.

Connect your Telegram account to receive signals as chat messages. Setup is a /start command on a bot, link via a one-time token in /app/settings.

Receive signals as plain-text emails. Setup is automatic — your account email is used unless you override.

Botely POSTs each signal to your endpoint with an HMAC-SHA256 signature header. Audit-grade integration for programmatic consumers.

Versioned JSON schema, header layout, and verification snippets in Node, Python, and PHP.

Common failure modes and how Botely retries.

Download your full closed-trade history as a CSV from /app/trades → Export, or programmatically via the API.

Plain-language summary of what Botely sees, never sees, and how the on-chain permissioned-key model bounds the blast radius if anything is compromised.

What's actually signed, what's stored, what the failure modes are. For users who want to verify Botely's claims before approving the agent.

If you suspect your owner mnemonic / recovery phrase has leaked, time is critical. Follow these steps to limit damage and rotate.

How to store your recovery phrase so it survives device failure but doesn't end up on someone else's computer. Practical do's and don't's.

Top-down list of what to verify when the bot has been silent for an unusual stretch.

Rotation, not recovery. The trading-key private key was shown to you ONCE during the wizard. If you didn't save it, you can't recover it — but you can cheaply replace it.

Common problems with the EVM-wallet → Botely-wizard handoff: MetaMask popup blocked, wrong network, multiple wallet extensions fighting over the connection.

Botely Phase 0 is founder-only and runs one bot on one wallet. Phase 1 adds multi-tenant (one user, one wallet each). Multi-wallet per user is Phase 2.

Botely's SaaS and the trading bot are separate processes. SaaS down ≠ bot down. Open positions stay safe — TP/SL are on-chain.

Practical user-facing summary of how Botely sits relative to MiCA + MAR. NOT legal advice — see /compliance for the rigorous version.

Botely doesn't file your taxes — you do. General pointers on how perpetual futures profits are typically treated, and where to be careful.

Phase 0 does NOT require KYC. Phase 2 will when Botely opens to public users with payment processing. What we'd ask for, and why.