Command center for monitoring and operations
Trading Control Room
Monitor signal intake, paper simulation, Binance Demo/Testnet execution, risk gates, stale protection, audit activity, and project progress from one command screen.
Start, Stop, Or Notify
Alert Intake
Execution Pipeline
No live Binance call
TP/SL protection tracked
Guard Status
Diagnostics
Build Status
Audit Pulse
Operate
Secure account
My Dashboard Access
TradingView command stream
TradingView Alerts
Inspect signal-only webhook traffic, approved strategy routing, payload details, safety blocks, and automation outcomes from one command console.
Analytics range
Signal Dashboard Window
Webhook ledger
Detailed Alert Records
| ID | Alert ID | Strategy | Team / Owner | Symbol | Timeframe | Signal | Market | Entry | SL / TP | Priority | Tag | Status | Simple Payload | Reason | Received | Payload |
|---|
Telegram
Telegram Message Ledger
Monitor inbound signal messages, outbound dashboard notifications, channel filters, and safety status from one operations view.
Date scope
Ledger Range
Combined
All Telegram Messages
| ID | Direction | Channel | Chat ID | Sender | Owner | Title | Message | Category | Status | Reference | Reason / Errors | Time |
|---|
Inbound
Signal Messages Received From Telegram
| ID | Update ID | Owner | Chat ID | Sender | Message | Status | Errors | Received |
|---|
Outbound
Dashboard Notifications Sent To Telegram
| ID | Channel | Chat ID | Category | Title | Message | Status | Telegram Message | Reason | Sent / Skipped |
|---|
Safety
Safety Blocks
| Source | User | Reference | Strategy | Market | Symbol | Side | Status | Reason | Time |
|---|
Paper trading
Simulated Orders
| ID | Virtual | Alert ID | Strategy | Owner | Symbol | Side | Amount | TP/SL | Status | Safety | Created | Action | Terminate |
|---|
Binance testnet
Manual Testnet Orders
| ID | Paper ID | Virtual | Owner | Market | Symbol | Side | Amount | Binance | Protection | Status | Created | Terminate |
|---|
Order lifecycle
Order Tracker
Paper Trading Tracker
| ID | Virtual | User | Market | Symbol | Side | Amount | Status | Safety | Created |
|---|
Binance Spot Order Tracker
| ID | Virtual | User | Symbol | Side | Amount | Binance | Protection | Status | Created |
|---|
Binance Futures Order Tracker
| ID | Virtual | User | Symbol | Side | Amount | Binance | Protection | Status | Created |
|---|
Analysis and reports
Automation Intelligence Room
Long-form operational reports for trades, alerts, messages, safety blocks, and Binance Demo/Testnet lifecycle. Live Binance remains locked out.
What The Current Filter Is Saying
Equity And Drawdown
Results By Outcome
Top Contributors
Strategy P/L Leaders
Symbol P/L Leaders
Source Conversion
Strategy Performance
| Strategy | Closed | Win Rate | Net P/L | Avg P/L | Open | Alerts | Rejected |
|---|
Symbol Performance
| Symbol | Closed | Win Rate | Net P/L | Avg P/L | Open | Alerts | Testnet |
|---|
Source Conversion
| Source | Alerts/Messages | Paper Orders | Testnet Orders | Submitted | Rejected | Closed P/L |
|---|
Open Futures Demo Positions
| ID | Virtual | User | Source | Strategy | Symbol | Side | Amount | Entry | Open P/L | Lifecycle | Opened | Age |
|---|
Closed Futures Demo Report
| ID | Virtual | User | Source | Strategy | Symbol | Side | Amount | Entry | Exit | P/L | Close Reason | Duration | Closed |
|---|
TradingView Alert Report
| ID | Alert ID | Owner | Strategy | Symbol | Side | Market | Status | Simple Payload | Received |
|---|
Message Report
| ID | Direction | Channel | Chat ID | Category | Status | Message | Time |
|---|
Paper And Testnet Ledger
| Layer | ID | Virtual | User | Market | Symbol | Side | Amount | Binance | Protection | Status | Created |
|---|
Manual trading
Manual Paper Order
Risk controls
Active Paper Risk Settings
Users
Platform Users
| ID | Role | Country | Telegram Chat | Max Paper | Symbols | Status | Paper | Testnet | Live | Manual | Copy | Save All | Telegram Actions | Permission Actions | Risk Actions | Status Actions |
|---|
Strategy control
Approved Strategies
| ID | User | Source | Strategy | Label | Symbols | Markets | Execution | Status | Updated | Action |
|---|
Binance testnet
Testnet API Key Storage
| ID | User | Country | User Testnet | Market | Key | Status | Connection | Checked | Updated | Action |
|---|
Read-only viewer
Spot Testnet Orders
Open
Open Orders
| Order ID | Owner | Symbol | Side | Type | Price | Executed | Quote | Status | Updated |
|---|
History
Order History
| Order ID | Client ID | Owner | Symbol | Side | Type | Price | Executed | Quote | Status | Updated |
|---|
Fills
Trade History
| Trade ID | Order ID | Owner | Side | Price | Qty | Quote | Commission | Time |
|---|
Read-only viewer
Futures Testnet Orders
Risk
Positions
| Symbol | Owner | Side | Amount | Entry | Mark | Unrealized PNL | Liquidation | Leverage | Margin |
|---|
Open
Futures Open Orders
| Order ID | Owner | Symbol | Side | Position | Type | Price | Executed | Quote | Status | Updated |
|---|
Protection
Futures Conditional TP/SL Orders
| Source | Owner | Symbol | Side | Type | Trigger | Quantity | Status | Reason | Updated |
|---|
Conditional
All Open Conditional Orders
| Algo ID | Owner | Symbol | Side | Type | Trigger | Quantity | Reduce Only | Status | Updated |
|---|
History
Futures Order History
| Order ID | Client ID | Owner | Symbol | Side | Position | Type | Price | Executed | Quote | Status | Updated |
|---|
Fills
Futures Trade History
| Trade ID | Order ID | Owner | Side | Position | Price | Qty | Quote | PNL | Commission | Time |
|---|
Application controls
Settings
Telegram messages sent from dashboard
Outbound Notification Controls
These controls decide which dashboard events are sent to Telegram. Telegram messages sent by users into the dashboard are still controlled separately by Platform User chat ID and approved strategies.
Telegram channels
Inbound / Outbound Channel Configuration
Use the inbound channel for Telegram messages that create dashboard alerts/orders. Use the outbound channel for dashboard notifications sent to Telegram.
Recommended channel design
Separate Inbound And Outbound Channels
Use one Telegram chat or channel for users sending trade signals into the dashboard, and a different Telegram channel for admin notifications from the dashboard. This makes operations easier to understand and avoids message noise.
Coming next
Multi-Channel Telegram Ledger
The next Telegram work item will separate inbound signal channels, outbound notification channels, and combined channel history views.
User guide
User Guide
Futures demo
Futures Demo/Testnet Preparation
This section is for verification before and during Futures automation testing. No Futures order is placed from the guide.
TradingView webhook setup
TradingView Alert Message
Use this reference when creating TradingView alerts. The application decides the execution mode from dashboard settings and the approved strategy profile.
Webhook URLhttps://api.maranatha153nz.com/webhooks/tradingview?secret=YOUR_TRADINGVIEW_WEBHOOK_SECRETJSON message
{
"source": "tradingview",
"alertId": "tv-futures-{{ticker}}-{{time}}",
"strategyCode": "r025_spot_testnet_manual_check",
"symbol": "{{ticker}}",
"timeframe": "{{interval}}",
"signal": "BUY",
"entry": "optional numeric price",
"stopLoss": "optional numeric price",
"takeProfit": "optional numeric price"
}
Telegram inbound template
Inbound Signal Format
Use this format for Telegram messages that are intended to become paper, Spot Testnet, or Futures Demo/Testnet orders.
MARANATHA153NZ_SIGNAL alertId: tg-20260801-001 strategyCode: telegram_paper_alert symbol: BTCUSDT timeframe: 15m signal: BUY entry: optional numeric price stopLoss: optional numeric price takeProfit: optional numeric price
Step 1
Open Futures Demo/Testnet
Login to Binance Futures Testnet and open the BTCUSDT futures screen. Keep this separate from normal Binance live trading.
Step 2
Find The Order Screens
Confirm where the page shows Open Orders, Order History, Trade History, Positions, Leverage, Margin Mode, and Balance.
Step 3
Create Futures Testnet Key
Create or confirm a separate Futures Testnet API key, save it under Futures Testnet, then use Check Connection.
Step 4
Capture Verification
Before we automate, record where Futures orders, conditional TP/SL orders, positions, and trades appear after a small demo order.
| Verification Item | Why It Matters | Status |
|---|---|---|
| Futures Testnet login works | We need a safe demo account before Futures testing. | Verified |
| Open Orders page found | We must see active Futures orders before adding cancel/close controls. | Verified |
| Order History and Trade History found | We need to prove each automated Futures test can be audited. | Verified |
| Positions, leverage, and margin mode found | Futures risk is different from Spot and must be visible before automation. | Verified |
| Futures Testnet key connection passes | The app should confirm account access before Futures demo orders. | Verified |
Audit
Admin Audit Logs
| ID | Actor | Action | Entity | Before | After | Time |
|---|
Database maintenance
Database Cleanup
Storage Usage Filter
Delete Records Filter
System
System Health
Product research
Research Roadmap
Guiding rules
Product Principles
Advanced features
Dashboard Architecture
| Area | Priority | Stage | Dashboard Need | Why | Planned Controls |
|---|
Sources
Research Basis
| Source | Finding | Link |
|---|
Roadmap
Project Status
| ID | Stage | Work Item | Status | Priority | Completed / Target | Duration | Next Action |
|---|