Manual

0. How the system works

BudaiCapital is a dashboard that wires your trading signals to your Bitget account to trade USDT-M perpetual futures automatically. You never click a button to open a position: a signal comes in from TradingView (or a Telegram channel the strategy reads) and the system executes it on Bitget using the risk plan you configured.

The signal loop

1. 01A strategy fires an alert (on TradingView, or a message in a Telegram channel the strategy listens to). The alert carries a side (BUY/SELL), a symbol (e.g. BTCUSDT) and, optionally, a full risk plan: stop loss, tiered take profits, trailing and break-even.
2. 02The dashboard receives the signal, finds every subscribed user, and queues one order per subscription.
3. 03The system picks each order up within seconds: it resolves your risk plan (from the message itself, the strategy, or your per-coin custom plan) and places the trade on Bitget along with the stop loss, the partial take profits and the native trailing.
4. 04The dashboard tracks the position in real time: partial take profits, trailing activation, break-even and the final close reason. Every signal also runs through the simulator (paper): a practice-only subscription never touches the exchange; a live one also executes for real.

Paper vs Live

Today every account you create from the dashboard is a real (live) Bitget account; demo account creation was retired because its behaviour diverged from the real thing. Paper trading runs in parallel: each strategy keeps a global simulated track record, and each subscription can enable its own personal paper. Paper stats (winrate, profit factor, Sharpe, equity) show up on Strategies and refresh after every simulated trade closes.

What you'll do in this manual

• Verify your email on Profile (required to create accounts) and link Telegram if you want Telegram login.
• Create a real Bitget account (API key + secret + passphrase) and validate it with Test.
• Browse the catalog, read each strategy's stats, and subscribe.
• Optional: edit your per-coin risk plan on the strategy and enable personal paper to track it in parallel.
• Wire TradingView to the strategy's webhook (if the strategy is TradingView-type) and validate with a test alert.
• Read the dashboard: open positions, the TP/SL/trailing/BE lifecycle, full history and notifications.

1. Add a real Bitget account

Your account connects the dashboard to a real Bitget account. Credentials are encrypted (AES-256) before they are stored and only decrypted at the moment an order is placed. The dashboard never shows them again: if you lose them, rotate the API key on Bitget and re-add them.

Go to → Accounts (/accounts)

Before you start

• Your email must be verified in Profile → Security. If it isn't, you won't be able to create accounts. If the email didn't arrive, ask for a resend.
• Generate a Bitget API key with read and futures permissions (USDT-M perpetuals). Do not enable withdrawals: that permission should never be on.
• If your Bitget profile requires IP restriction, ask the administrator for the server's IP to add it to the whitelist.
• Write down your API passphrase: Bitget needs three credentials (key + secret + passphrase), not two. If you forget the passphrase you'll have to create a new key.

Steps

1. Step 01

   Open the Accounts page

   From the sidebar go to Accounts. The page lists every account linked to your user. Empty on first visit.

2. Step 02

   Click + add bitget account

   A form opens. The exchange is locked to Bitget: it's the only one available for new accounts. Older accounts on other exchanges (BingX, Bybit, Bitunix) still work if they already existed, but you can't create new ones here. Bitunix in particular manages trailing in software rather than natively (see the lifecycle section).

3. Step 03

   Paste API key, secret and passphrase

   All three fields are required. The passphrase is the one people forget: if you leave it empty, the form won't accept the account. Credentials are encrypted on the server before being stored.

4. Step 04

   Save and validate with Test

   After saving, the account renders as a card. Click Test: the dashboard uses your credentials to ask Bitget for your USDT-M balance and shows Connection OK — balance: XX USDT. If Bitget returns an error, the exact message shows on the card.

2. Browse the catalog and subscribe

Strategies live in a public catalog at Strategies. Each card shows the indicator that fires it, its default timeframe, a free/premium tag and its paper trading stats: winrate, profit factor, Sharpe and cumulative PnL. Subscribing binds the strategy to one of your accounts so its signals execute.

Go to → Strategies (/strategies)

Steps

1. Step 01

   Open Strategies and filter

   Available filters: all / free / premium. Click any card to open the detail page. Read the stats before subscribing: a strategy with Sharpe < 1 or winrate < 50% isn't necessarily bad, but understand why.

2. Step 02

   Pick an account and subscribe

   On the strategy detail page, the Account menu only shows enabled accounts not yet subscribed to that strategy. Press Subscribe. The subscription appears under My Subscriptions and is active: the strategy's next signal executes on your account.

3. Step 03

   Decide the risk source

   Your subscription lets you choose between two risk modes: the strategy's or custom. The strategy's (default) uses the plan it publishes (SL, TPs, trailing, BE). Custom lets you override all of it per coin from Strategy detail → Risk configs: a different plan for BTC than for SOL, for example.

4. Step 04

   Enable personal paper (optional)

   The Paper personal toggle creates a simulated track record dedicated to your subscription. Every signal runs twice: once live on Bitget and once against your paper, so you get your own parallel history. Useful when you're tuning your risk plan.

3. Wire TradingView to the strategy webhook

If the strategy is TradingView-type, its signals come in over an HTTP webhook. The webhook URL carries a unique per-strategy token that the administrator shares with you. Telegram-type strategies don't need a webhook: the system already listens to a Telegram channel and reads each message against the strategy's rules.

Webhook URL format

Replace {token} with the strategy's token and {host} with the dashboard's public domain.

Configure the alert

1. Step 01

   Open the TradingView alert dialog

   On your chart, attach an alert to the indicator that fires the strategy (the one listed on its detail page). TradingView alerts can be per-bar-close or once-per-bar: confirm which one matches the strategy's logic.

2. Step 02

   Set the Webhook URL

   On the Notifications tab, enable Webhook URL and paste the full URL above with the strategy's token in place.

3. Step 03

   Set the message body

   The dashboard accepts a JSON body with at least side (BUY or SELL) and symbol (e.g. BTCUSDT). Optional but recommended: timeframe, price and a full risk object (sl_pct, tp_plan[{size,price_pct}], trailing, breakeven). Minimal example: {"side":"BUY","symbol":"{{ticker}}","timeframe":"1h"}. With risk: {"side":"BUY","symbol":"{{ticker}}","risk":{"sl_pct":1.5,"tp_plan":[{"size":0.3,"price_pct":1.0},{"size":0.3,"price_pct":2.0},{"size":0.4,"price_pct":3.5}],"trailing":{"activation_pct":2.0,"callback_pct":0.8},"breakeven":{"trigger_pct":1.0,"offset_pct":0.1}}}.

4. Step 04

   Test with one alert and read the response

   Fire the alert once. The dashboard confirms receipt if it processed it. Back on the dashboard, the position should show in Open positions within seconds (live) or in Strategies (paper).

4. What the dashboard shows you

The dashboard is read-only: it shows trades, signals, paper stats and equity, and queries Bitget directly for balances and open positions. It doesn't open or close orders: the execution system handles that separately.

Go to → Dashboard (/dashboard)

Main panels

1. Stats grid

   Total PnL, win rate, profit factor, Sharpe, Sortino, Calmar, max drawdown, expectancy, exit breakdown and total fees. Computed over closed (live) trades only. The selector up top filters by account. To see paper, go to Strategies.

2. Equity curve

   Cumulative PnL over time with drawdown underneath. Peaks are highlighted in the legend. The curve comes from real exchange fills, not theoretical calculations.

3. Open positions

   Live table of open positions on Bitget: symbol, side (LONG/SHORT), entry, leverage, margin, the indicator that opened it, timeframe and time open. Refreshes every few seconds.

4. Recent trades

   The last 10 closed trades with entry, exit, realized PnL, close reason and duration. For the full log with filters and pagination, open History.

Lifecycle of a position

A live trade isn't just an entry: the system places several exit orders at once and reacts to partial fills.

1. SL (stop loss)

   Hard floor. If price touches this level, the entire remaining position closes at a loss. It's placed as a separate order on Bitget when the position opens.

2. TP1 / TP2 / TP3 (partial take profits)

   Three tiered levels. When TP1 fills, a fraction of the position closes in profit and the rest stays open; same with TP2. TP3 usually closes whatever is left. If the sizes sum to less than 100%, the native trailing closes the remainder.

3. Trailing stop

   When profit clears the activation threshold, the system places a trailing stop on Bitget that follows the favorable price at the configured distance and triggers a close on a reversal. After each partial take profit, the trailing is re-placed with the remaining size. On legacy Bitunix accounts the trailing is managed in software (the dashboard moves the stop), because Bitunix offers no native trailing.

4. Break-even (BE)

   When unrealized profit reaches its threshold, the stop loss moves to entry plus a small margin. From there the trade can't lose, except a tiny fee if it taps break-even.

Not all of these states render in the current widgets. To see them in full, open the trade in History and review the associated events.

5. Read the trade history

The History page is the ledger of every position the system opened on your behalf. Use the filters (account, symbol, status) and page with Load More. Each row carries realized PnL computed from real exchange fills, fees and slippage included.

Go to → History (/history)

Columns

1. Symbol

   The futures contract, e.g. BTCUSDT, ETHUSDT, SOLUSDT.

2. Side

   LONG or SHORT: the direction the system took on entry.

3. Entry → Exit

   Effective prices. For partial take profits, the exit shown is the volume-weighted average across all fills (TP1 + TP2 + TP3 + final close).

4. PnL

   Realized profit or loss in USDT, with the percentage over margin in parentheses. Includes fees and slippage. A dash means the trade is still open.

5. Close reason

   Why the trade ended; see the table below.

6. Duration

   Time between entry and full close. Useful for comparing scalps and swings of the same strategy.

7. Indicator

   Which signal source opened it. Matches the strategy you subscribed to (neptune, cybercycle, cybercore, etc.).

Close reasons

6. Using AI Analysis

AI Analysis turns raw market data into a prompt for a language model (Claude, GPT, Gemini). You bring your own provider API key from Profile → Credentials. The dashboard never stores it in plain text: it's encrypted just like your Bitget API keys.

Go to → AI (/ai)

What each tab does

1. AI Analysis

   Builds a structured prompt from OHLCV, Elite indicators, SMC (Smart Money Concepts) and Ehlers signals over the timeframes you choose. Send to AI returns a markdown analysis ready to paste into your journal.

2. Mindset

   Shorter, narrative prompts focused on trade psychology and biases around the current setup. Useful after a hot or cold streak to check whether you're trading on conviction or fear.

3. Dominance digest

   Daily commentary on BTC.D, ETH.D, USDT.D and altcoin dominance. Use it as macro context before scaling positions.

4. USDT dominance

   Live chart of USDT dominance from TradingView. Use it to gauge risk-on (USDT.D falling) vs risk-off (USDT.D rising) regimes.

7. Current safety controls and limits

Knowing exactly what is and isn't automated is part of trading carefully. Today several controls are active at the account and session level; what's missing is marked below as planned.

Active safety controls

1. Per-account cut-off

   On Accounts, each card's Disable toggle switches the account off. The system detects it every cycle and stops executing signals on it; queued pending signals are skipped. It's the primary cut-off if you suspect something is off.

2. Pause a subscription

   From the strategy detail you can pause a subscription without unsubscribing. Paused means it doesn't execute but keeps its config (risk mode, personal paper, adjustments). Useful to cut one strategy without touching the others.

3. Email verification

   Creating an account requires a verified email. Until you verify it you can't link any exchange account: a barrier against rushed sign-ups with a throwaway email.

4. Active sessions and login history

   Profile → Security lists your active sessions (browser, IP, last seen) and lets you revoke any with one click. It also shows your login history (date, IP, method) to spot logins that weren't you. Revoking the other sessions signs you out of every other device instantly.

5. Telegram login

   You can link a Telegram username in Profile → Credentials to log in through the Telegram bot instead of a password. The widget signs each login so the server can confirm it really came from Telegram.

Planned (not implemented yet)

1. Global cut-off

   A single toggle that halts execution across all your accounts and subscriptions at once. Today you have to disable each account one by one.

2. Unified audit log

   Today there's a login history and every strategy change is recorded, but there's still no single panel with the full timeline of changes. It's on the roadmap.

3. Rate limiting and extra login protection

   A hardening pass over the login and sign-up forms. Today the dashboard relies on session cookies and CORS: enough for a closed beta, not for mass public sign-up.

Until those changes land, treat the dashboard as a closed-beta tool: use a dedicated Bitget account (not your main one), don't enable withdrawals on the API key, start on a strategy with personal paper before going live, and check Profile → Security every so often for sessions you don't recognize.