Connect APIs
Demo/Testnet for safe account testing. Live for public market data only.
Local API console
Operating manual
Use this page as the main checklist before you scan alerts or prepare demo trade automation.
Visual workflow
Demo/Testnet for safe account testing. Live for public market data only.
Fetch symbols, load candles, and confirm Binance data is visible.
Add the dashboard indicator package and review its settings.
Choose indicator alert names and define BUY/SELL alert intent.
Save time window, selected rules, volume filter, and scanner symbols.
Backfill missing candle history before scanning any selected symbols.
Test background scanning manually before enabling scheduled runs.
Filter today, current session, symbols, timeframes, and source.
Only after alerts look correct, define demo-only limits, SL/TP policy, and duplicate controls. No live trading.
Icon-style workflow visuals are embedded SVGs based on free/open SVG icon patterns, so the dashboard works offline locally and on the VPS.
Required first
Daily scanner
Alerts
Trading safety
Connection setup
Simulated funds
Ready.
Public market data
Ready.
Current day connection health
Daily counts are calculated from local audit records for today in IST. Errors are shown here so repeated connection issues are easy to trace.
Help
API key and API secret are your Binance Futures Testnet credentials. Use this account for automation testing and demo trades only.
Test Demo Signed Key reads the Demo/Testnet Futures account once. Diagnose Demo Signed Key checks public Demo Futures plus signed Demo Futures account read.
Connect Demo Futures Testnet API verifies the signed demo account connection and shows demo account status. If saved credentials exist, you can leave the key fields blank.
Live Futures Market Data URL reads public Binance Futures data for charts, price, and 24h volume. This does not need live Futures trading permission.
Test Live Data checks the public live Futures endpoint. Connect Live Futures Market Data API connects to Binance live public market data only. It does not place trades.
Test Demo Public API and Test Live Data check whether Binance public data is reachable. Save stores credentials locally in this project. Use Saved uses saved credentials. Clear Saved removes them. Disconnect clears the current connection status.
API Connection Attempts And Sessions shows today's attempt count, success/failure count, active session time, session start time, and recent errors from local audit logs.
Live futures market data
Ranked by 24h quote volume
Top symbols are selected by highest Binance USD-M Futures 24h quote volume. Sorting changes the table view only; it does not change which symbols qualify for Top 10, 20, 50, or 100.
Click Refresh List to load ranked live futures symbols.
Stored candles
Uploaded indicator
Chart guide
Click Fetch Symbols, search the symbol, and select it from the dropdown.
Price source must match the Binance chart setting. Use Last Price for normal trade candles, Mark Price for mark candles, or Index Price for index candles.
Historical candles to download controls how many REST candles are saved. Binance allows up to 1000 per request.
Candles to show on chart controls how many stored candles are drawn. Use fewer candles for a cleaner view.
Auto live socket starts Binance live updates after Load Chart. REST loads history first, then WebSocket keeps the current candle moving. A REST fallback runs only as backup.
Use the separate Chart Live Data Verification page when you want to compare Binance REST candles against live socket candles.
Chart live data verification
Use this page when Binance website candles and dashboard candles look different. Keep Binance website on the same symbol, timeframe, and Last Price mode.
Dashboard indicator library
Upload only dashboard-native indicator packages that were already created and reviewed in the converter lab. This page does not convert Pine Script.
Choose the indicator folder or select `indicator.json`, module file, and README together.
Packages are saved under this dashboard storage folder and ignored by Git.
View manifest, README, and dashboard code before applying indicators to chart data.
Uploaded indicators are not allowed to trade until later approval gates are added.
Select an uploaded indicator and inspect its files before applying it on the chart.
Uploaded indicators
Automation setup
Create named alert definitions. These rules will later drive background scanning and demo trade decisions.
Optional live-cross mode
Use Not applicable when this indicator does not need current live candle crossing. These fields are ignored unless live-cross timing is selected.
Indicator alert playbook
Use this guide when Hammer Maranatha153nz alerts need both candle-close confirmation and live candle high/low crossing checks.
Visual workflow
Upload Hammer Maranatha153nz, inspect the manifest, and confirm available alert names and settings.
Create separate rules for hammer pattern, hammer BUY entry, live cross above high, and live cross below low when needed.
Use candle-close mode for confirmed hammer candles. Use live-cross mode when price must trigger before the candle closes.
Triggered alerts go to Trade Automation Rules first. Demo orders are sent only when demo switch, safety, SL, TP, and duplicate checks pass.
Mode A
Use this when the hammer pattern must be confirmed only after the candle closes.
Mode B
Use this when current live price must cross the previous candle high/low or an identified candle level before the candle closes.
Mode C
Use this when you want fast notification, but still want to know whether the candle finally confirmed.
Important distinction
Stable and safer. Alert is created after candle close, so the pattern is already confirmed.
Faster and noisier. Alert can trigger before close when price crosses a selected high or low.
Every live-cross alert needs a stored reference candle or level, such as previous high, previous low, support, or resistance.
One reference candle and direction should create one alert only, even if live price crosses the level many times.
Scanner test
Run saved Alert Rules against locally stored candles before enabling daily background automation.
Manual scan guide
Manual Scan does not download candles by itself. Download historical data in Chart Data Storage first.
Only saved and enabled Alert Rules are scanned. Rules decide which indicator events become triggered alerts.
If the same alert already exists for the same candle, it is counted as a duplicate instead of being saved again.
This local scan creates signal history only. Demo trade execution will be added after scanner validation.
Daily automation setup
Save the daily scan window, symbol-volume filter, timeframes, and Alert Rules before building the live scheduler.
Optional speed controls
When optimization is off, the scanner uses the original full process: full stored history, candle readiness check, one safe worker, then alert scan and trade evaluation. It is slower, but easier to understand and gentler for first testing.
Use these only when you want faster scanner cycles after the normal process is already working.
No Alert Rules selected yet.
Save only when you change times, symbols, timeframes, rules, or checkboxes. You do not need to save it every day.
When checked, Start Daily Scanner can run this plan during the saved time window. When unchecked, the scanner skips safely.
When checked, each new session can rebuild the symbol universe from fresh 24h volume data.
Runs one immediate test cycle and stops. By default it scans and evaluates only. It can place Demo/Testnet orders only when the Run Once demo order checkbox and max order count allow it.
Starts the real automatic loop during the saved window. It scans normal candle-close rules, starts live-cross monitoring when needed, evaluates alerts, and lets Trade Automation Rules plus Safety decide whether Demo/Testnet orders can be placed.
Workers are parallel scanner jobs. 1 worker is slowest but safest. More workers can finish faster, but can add API and computer load.
Stops the loop only. It does not delete the saved plan, symbol universe, candles, or triggered alerts.
Background execution
One start button runs the saved daily plan. Normal candle-close rules and live-cross rules are handled automatically.
Choose which real steps Run Once should perform. Keep all steps selected for normal testing.
Started automatically by Start Daily Scanner only when selected Alert Rules use live-cross settings.
Daily plan guide
The selected timezone, start time, and end time define when each daily scanner session should run.
When reset is enabled, the next day can build a fresh symbol list from the latest 24h volume data.
Minimum 24h quote volume decides which symbols qualify. Symbol limit is All by default, or a Top N cap when selected.
Start Daily Scanner follows Trade Automation Rules and Safety. Run Once has its own demo-order test option so you can test order placement manually before relying on the automatic loop.
Run Once Now uses the selected test steps beside its button. Start Daily Scanner uses the saved Daily Scanner Plan and optional optimization settings at the top of this page.
Daily symbol builder
Build today's scanner symbol list from Binance USD-M Futures 24h quote volume.
No selected symbols yet.
No rejected symbols yet.
Universe guide
The builder keeps only active USD-M Futures perpetual contracts from Binance exchange info.
Symbols are ranked by 24h quote volume from Binance ticker data, then filtered by your threshold.
All matching symbols are selected by default. Choose Top 10, 20, 50, 100, or more only when you want a cap.
After this list is built, candle readiness will check whether each selected symbol has enough history.
History gate
Check whether selected symbols and timeframes have enough stored candles before background scanning starts.
No readiness rows yet.
Readiness guide
Readiness uses the symbols from the saved Symbol Universe and timeframes from Daily Scanner Plan.
The required candle count comes from selected indicators, with a local minimum of 100 candles.
Backfill downloads missing historical candles using Binance REST and stores them in the local chart candle store.
Background scanning should only start for symbol/timeframe rows marked ready.
Background signal inbox
Search alerts that were triggered by indicators. The status shown on each card comes from optional manual review or later trade automation decisions.
Alert guide
Every scanner match is saved here with symbol, timeframe, indicator, event, side, candle time, and optional entry/SL/TP.
The duplicate key is stored internally so the same symbol, timeframe, indicator, event, and candle cannot create repeated local alerts.
Use Alert period to see today's alerts, previous-day alerts, or only alerts triggered after the saved daily scan start time.
This page stores signals only. Demo and live orders remain disabled until the later Trade Automation Rules step.
Demo trade gate
Choose which triggered alerts may open demo/testnet trades, review ready or blocked decisions, and send Demo/Testnet orders only when safety gates allow them.
Dry-run execution gate
Evaluate triggered alerts against saved Trade Automation Rules before any Binance testnet order endpoint is connected.
Filtered decision list
Shows the saved decisions matching the selected status, symbol, and limit filters.
Trade safety guide
Rules are stored for Binance Demo/Testnet only. Live trading stays locked.
Use same-symbol and flat-position controls to prevent repeated or conflicting demo trades.
Max trades per day, open trades, trades per symbol, position size, SL/TP policy, default SL %, and TP/RR are saved before order execution exists.
Demo/Testnet orders require the local execution switch and saved demo credentials. Live orders remain locked.
Triggered Alerts can be evaluated as dry-run demo trade decisions. Ready means the rule allowed it; blocked means no order should be sent.
Global safety gate
Set the dashboard-wide demo/testnet automation limits before any order reaches Binance Demo/Testnet. Live trading stays locked.
Safety guide
Demo orders require both the Demo/Testnet order switch and Safety settings to allow the action.
Pause blocks new demo orders. Maintenance also blocks cancel/close controls while you are changing settings.
These limits sit above individual Trade Automation Rules and apply to every demo order attempt.
Every Safety settings save is recorded in Audit Logs so VPS migration can keep the same control history.
Demo/testnet only
Monitor Binance Demo/Testnet wallet, positions, open SL/TP orders, and local execution decisions. Live trading remains locked.
Local vs Binance check
Open exposure
Protective and pending orders
Local execution log
Monitor guide
This page reads and controls Binance Demo/Testnet orders only. Live trading is still locked.
Cancel open demo SL/TP or pending orders for one symbol when you need to clean up a test.
Close an open demo position with a reduce-only market order after confirming the action. The dashboard also tries to clean normal and algo SL/TP orders for that symbol.
Recent decisions show what the dashboard attempted and whether Binance accepted or rejected it.
In Futures, an accepted market order opens or changes a position. So a test may show a position even when the later SL/TP protection step failed.
Use this only to clean failed messages from this monitor view. It does not close positions, cancel Binance orders, or delete audit history.
Global report library
Explore every report type planned for this dashboard. Use this page to understand what each report shows, which data it needs, and whether it can be built now or after VPS/PostgreSQL migration.
Live local report
One place to confirm today's API connection, scanner plan, symbol universe, candle readiness, alert activity, and demo/testnet safety state before automation runs.
Live local report
Follow dashboard indicator alerts from trigger to trade decision, blocked state, ready-for-demo order, demo order attempt, opened position, protection, and attention items.
Live local report
Confirm whether selected Alert Rules require intrabar live-candle cross monitoring, whether the live-cross scanner is running, and which rule settings are still missing.
Live local report
Review demo/testnet order decisions from ready state through order attempt, opened position, SL/TP protection, close, failed/unknown state, and attention items.
Live local reports
These reports use local dashboard records that already exist, so they can be used before VPS/PostgreSQL migration.
Report catalog
Build sequence
Dashboard-native reports
Review indicator alerts, trade decisions, lifecycle status, and demo/testnet outcomes from local dashboard records.
Symbol performance
Indicator performance
Timeframe performance
Trade rule performance
Needs review
Latest alerts
Latest decisions
Analysis guide
This page does not scan, create alerts, or send orders. It only reads local dashboard records.
Check Need attention first. These are failed, unknown, or unprotected demo lifecycle records.
Use symbol, indicator, timeframe, and trade rule tables to see which rules create useful or blocked outcomes.
This local report will later become PostgreSQL report queries with exports and scheduled summaries.
Preview before delete
Clean local JSON test data only after reviewing the preview. Active demo order decisions are protected from decision cleanup.
Apply cleanup
Cleanup guide
Preview shows current records, removable records, remaining records, and sample rows before deletion.
Candles are cleaned by age and by keeping the latest candles per dataset. Symbol filter limits candle cleanup to matching symbols.
Pending, opened, and unknown demo order decisions are kept so the monitor can still reconcile them.
On VPS this will become PostgreSQL dry-run counts, export-before-delete, and admin-only cleanup permissions.
Operational history
Review important dashboard actions before we move the same flow to VPS PostgreSQL.
Audit guide
Save, connect, use saved, diagnose, and disconnect actions are recorded without exposing API secrets.
Alert rule, trade rule, triggered alert review, delete, and clear actions are tracked.
Ready/blocked decisions, demo order sends, unknown timeouts, failures, cancel orders, and close position actions are visible here.
This local JSON log will later become a PostgreSQL audit_logs table with user, IP address, and role details.
Alert maintenance
This page is optional. It is only for manual notes, changing review status, ignoring test alerts, or deleting local test alerts.
The status is saved on that individual triggered alert and appears again in Triggered Alerts. It does not change the Alert Rule, and it does not automatically affect future alerts for the same symbol.
No. Normal automation should use Alert Rules and Trade Automation Rules. Manual review is only for testing, notes, cleanup, or intentionally marking alerts as ignored.
Open Triggered Alerts and use the Status filter. Counts for New, Reviewed, and Ignored are shown above the alert list.
VPS readiness
Manual scan visual test
Load an alert from Manual Scan to see the matching candle.