01
Start with Pulse
Describe an idea before configuring execution.
- Describe your idea, answer questions and review the assumptions.
- Build and read the simulated backtest, then edit in the Strategy Lab.
Bots · simulated and LIVE workflows · Browser walkthrough
The Bot Builder supports simulated and, where your account and a tested exchange connection allow it, LIVE workflows. simulated uses simulated activity; LIVE uses the selected exchange connection and can place real orders. Always check the mode shown in the Builder and review every setting before saving or activating.
Risk notice: simulated results are simulated and do not guarantee live results. LIVE trading can lose money. Never enable withdrawals on an exchange API key, and never share API credentials. Backtests use historical data and do not predict future performance.
In this section
Member pages may ask you to sign in. Page contents and access can vary with your account.
01
Describe an idea before configuring execution.
02
Use the dashboard to review your Bot workspace, then open Builder to choose a system. A draft is not active until you review and activate it.
03
Manage Bots is where you review saved Bot configurations and their available controls. Bot Library groups the available strategy and research tools.
04
The Builder offers Scanner signal source, DCA, Grid and Market making. Each system displays its own configuration fields; follow the fields shown rather than assuming all systems work alike.
05
The on-chain Arbitrage workspace offers Solana and BSC route quotes to members with the required bot membership. Connect the matching chain wallet to refresh quotes. The quote scanner does not submit trades.
06
simulated workflows use an Edge Theory simulated account. LIVE Bot workflows require an exchange API connection; the connection form confirms that withdrawals are disabled.
07
Activity reports recorded checks, orders, positions and issues. Verify whether each record is simulated or LIVE before interpreting it.
08
Statistics summarise recorded Bot activity. Check the mode and period in the report before drawing conclusions; historical performance is not a forecast.
09
The health page reports registry and runtime status for configured Bots. A failed page load is not a healthy status.
10
Strategy Lab has separate design and historical test controls; DCA, Grid and Bot family workspaces are available as separate destinations. Check each page’s mode and assumptions before using a control.