Demo
Market__Mode=DemoBackend-seeded demonstration records, not real market data. Demo signals must never produce Telegram messages or mix with non-demo signals.
Something needs attention
Connect to FlagShip
An access key is required by this server.
Yahoo requires the server’s workspace API key, including locally. Only local Demo with a blank server key can connect without one. Feed configuration and Telegram credentials stay in server-side settings or .NET user-secrets; the browser cannot enable Telegram.
A CLEARER VIEW OF THE MARKET
Market overview.
Watch the setup. Wait for the breakout. Keep the decision yours.
Connecting to your backend…
Waiting for the server to identify the feed. No market data is assumed.
COMPLETED NSE CANDLES · NOT TRADES
Awaiting feedLatest real data —
Waiting for the backend feed mode. No prices are assumed.
Waiting for enabled instruments…
| Instrument | Daily closeCandle ended · IST | 1h closeCompleted bar · IST | RSI · Daily | RSI · Weekly | RSI · Monthly | Candles receivedD / W / M / 1h histories | Data statusFetched ≠ candle end |
|---|---|---|---|---|---|---|---|
| Waiting for the backend. No placeholder prices. | |||||||
Scroll horizontally for all columns. Expand “Periods & timestamps” for each history.Highlighted RSI: backend qualifies and strictly < 10 · Not a fill or an order
How to read the latest completed data
Yahoo public NSE data may be delayed, unofficial, incomplete, or unavailable. These are the latest completed candles returned by a successful scan, not streaming ticks or a live quote. An after-hours fetch does not mean a new trade occurred.
Fetched is when the server recorded the successful symbol scan. Candle end is the completion boundary of that candle. Weekly and monthly histories come from Yahoo’s native periods and are admitted only after calendar rollover: Monday 00:00 IST and the first day of the next month at 00:00 IST respectively. Those boundaries are not exchange trade times. The first history bar may be dropped if its period is partial.
Counts show usable completed candles received per timeframe, not ticks, fills, or unique trading days. RSI may be unavailable with insufficient history. “No RSI setup” describes only the latest returned D/W/M periods; its count excludes missing RSI and scan errors. Setup counts can include retained snapshots, so check warnings and timestamps. Older signals can still exist. Eligibility does not confirm a breakout or create an executed trade.
Snapshots exist only in the current server process, appear after a successful Yahoo scan, and reset when the server restarts. A failed scan retains the previous snapshot with a warning. Demo and Ingestion currently supply no real-data snapshots. No signal price or previous browser session is used to fill a gap.
SIGNAL PIPELINE
Buy-onlyFrom setup to decision
01Find the setup
Daily / weekly / monthly
Wilder RSI(2) strictly < 10
02Wait for confirmation
Completed bar strictly above
the signal candle high
03You make the call
Record a manual fill.
Nothing places an order.
Daily → 1h monitoring · Weekly & monthly → dailyAwaiting signals
WATCHLIST MIX
By timeframe
Waiting for backend data…
YOUR RADAR
Signal watchlists —
| Instrument | Timeframe | RSI(2) | Signal high / low | Entry / last price | Targets · 1R / 2R / 3R | Status | Actions |
|---|---|---|---|---|---|---|---|
Loading your radarRequesting signals from the backend. No placeholder prices. | |||||||
INR prices · Signal low is the stop reference · R = entry − signal lowIndex / cap labels are user-maintained or illustrative
DEFINE YOUR UNIVERSE
Instruments —
| Instrument | Sector / cap | Index labels | Type / tick size | Latest data · IST | Scan enabled |
|---|---|---|---|---|---|
| Waiting for backend data… | |||||
THE LATEST
Recent activity
Waiting for backend events…
Waiting for notification status…
AUDIT TRAIL
Signal activity
Waiting for backend events…
Events returned by the dashboard, newest first. Open a signal for its detailed event and notification history.
A key for this tab only
The server validates X-Api-Key on every API request. Yahoo requires an API key even on localhost; use HTTPS in production. Run the VS Code task FlagShip: copy production API key for the hosted dashboard, or FlagShip: copy local API key for localhost, then paste below and save. The keys are separate. Clear your clipboard afterward; never paste keys into chat.
The local server can select Market:Mode=Yahoo through .NET user-secrets while the default configuration remains Demo. The reported feed mode is authoritative. The browser cannot change the feed or enable Telegram; Telegram credentials and other user-secrets remain server-side.
No saved key in this tab.
Know what is connected
- Feed
- Awaiting backend
Health checks are public and do not send your access key. They do not verify price freshness or Telegram delivery.
Choose the source. Keep secrets on the server.
This is configuration guidance, not an in-browser feed editor. Restart or redeploy the backend after changing its environment settings.
Telegram delivery, holidays & operating rules
Telegram__Enabled=true- Enable server-side notifications only for eligible non-demo signals.
Telegram__BotToken- Server secret only. Never put it in frontend files, browser storage, URLs, or logs.
Telegram__ChatId=-4087969089- Destination chat configured on the backend. The browser never sends Telegram messages.
Security__ApiKey- Server secret; required with HTTPS in production. An empty configured key may allow local development/demo access.
Market__Holidays__0,Market__Holidays__1, …- Configure the exchange holiday calendar using YYYY-MM-DD dates in the server’s Market:Holidays array. Session rules use Asia/Kolkata; weekends alone are not a complete calendar.
Use only completed candles. Daily RSI setups monitor hourly bars; weekly and monthly setups monitor daily bars. Strict RSI < 10 and strict high breakout apply. Stop and target tracking does not execute exits.
Recording is not execution. Active means a manually confirmed actual entry (a simulated fill in Demo). Closed means a stop, 3R, or manual record closure. No scan, confirmation, close, or toggle on this page places a broker order.