PulseFibo

Catch high-conviction crypto pullbacks before the crowd.

PulseFibo is a Telegram alert bot for crypto scalpers who want fast, rule-based signals on USDT pairs. It scans Binance and Bybit market data for volume surges, impulsive moves, and Fibonacci pullbacks in the ICT OTE zone, then sends structured alerts with entry, target, and stop loss levels. It helps traders reduce screen time and react consistently to setups that match their strategy.

Business Goals

  • Reach 500 monthly active users within 6 months of launch.
  • Achieve at least 35 percent free-to-paid conversion for premium alert tiers within 90 days of billing launch.
  • Maintain at least 60 percent 30-day retention among activated users who connect Telegram and enable scanning.
  • Generate alerts with a median end-to-end detection-to-message latency under 15 seconds for 95 percent of signals.
  • Keep support tickets related to alert formatting or missed notifications below 3 percent of all alerts per month.

User Goals

  • Detect qualifying crypto scalping setups without watching charts all day.
  • Receive clear Telegram alerts with entry, take profit, stop loss, and signal context.
  • Avoid repeated spam alerts on the same coin during active setups.
  • Filter out low-quality moves that do not meet volume and impulse thresholds.
  • Review signal details quickly on mobile and decide whether to trade manually or ignore.

Non-Goals

  • Automated trade execution in the initial release.
  • Backtesting, strategy optimization, or historical performance analytics in MVP.
  • Support for spot pairs outside USDT and non-supported leveraged tokens in MVP.
  • Full TradingView charting or advanced on-platform technical analysis tools.

Andi, 29, crypto scalper - Andi trades short timeframes during work breaks and cannot monitor charts continuously. He wants fast, consistent alerts that match his ICT-style entry rules.

Andi, 29, crypto scalper

  • As a scalper, I want alerts only when volume, impulse, and pullback conditions all align, so that I avoid low-quality entries.
  • As a trader using Telegram on mobile, I want the alert to show exact entry, TP, and SL levels, so that I can act immediately.
  • As a user, I want the same coin to be suppressed for a cooldown period after an alert, so that I do not get repeated spam.

Maya, 34, part-time swing and scalp trader - Maya uses Binance and Bybit and prefers structured alerts over manual scanning. She needs confidence that the bot is filtering out noisy market action.

Maya, 34, part-time swing and scalp trader

  • As a trader, I want the bot to scan many USDT pairs at once, so that I can find opportunities faster than manual review.
  • As a user, I want to know why a signal triggered, so that I can validate it against my own chart review.
  • As a trader, I want the bot to work reliably on a VPS, so that alerts keep coming while I am away from my desk.

Rafi, 41, signal group operator - Rafi runs a small paid Telegram group and wants a clear alert format that members can read instantly on mobile. He values reliability, consistency, and easy configuration.

Rafi, 41, signal group operator

  • As a group admin, I want alerts delivered in a consistent Markdown format, so that members can scan them quickly.
  • As an operator, I want to configure exchanges, cooldowns, and threshold values, so that I can adjust the bot to my audience.
  • As an admin, I want logs for failed API calls and Telegram delivery, so that I can diagnose issues without guessing.

Market Data Scanning · High priority

  • Continuously fetch and normalize OHLCV data for supported USDT pairs from Binance and Bybit through exchange APIs.
  • Use ccxt for unified exchange access and fallback handling.
  • Scan only active USDT spot or perpetual pairs configured by exchange.
  • Exclude leveraged tokens and symbols matching UP, DOWN, BULL, BEAR, and similar filters.
  • Refresh market data on a fixed loop and record the last successful fetch time per exchange and symbol.
  • Handle API rate limits, temporary timeouts, and empty candle responses without stopping the scan loop.

Signal Detection Engine · High priority

  • Evaluate volume surge, impulse move, and ICT Fibonacci pullback rules to identify valid scalping setups.
  • Compare the most recent completed candle volume to the average of the previous 10 candles and require at least 2.5x volume surge.
  • Require an impulse move of at least 1.5 percent in the same setup window before pullback validation.
  • Compute swing high and swing low from the impulse leg and derive Fib 0.618 and Fib 0.786 levels.
  • Trigger a signal only when current close is between Fib 0.786 and Fib 0.618 for the configured direction.
  • Reject signals if candle data is incomplete, stale, or the computed impulse leg is too small to validate.

Risk Level Calculation · High priority

  • Generate a consistent TP and SL suggestion for every valid setup based on market structure.
  • Set take profit at the impulse swing high for long setups.
  • Set stop loss 0.5 percent below the swing low for long setups, with mirrored logic for short setups if enabled later.
  • Display entry, TP, SL, and estimated reward-to-risk ratio in the alert payload.
  • Round levels to exchange-appropriate precision using symbol tick size or quote precision rules.
  • Prevent alert generation when TP or SL calculations are invalid or overlap due to extreme volatility.

Telegram Alert Delivery · High priority

  • Send real-time, human-readable alerts to a Telegram chat or channel with consistent formatting.
  • Use Telegram Bot API with secure bot token storage in environment variables.
  • Support Markdown-friendly formatted messages with emoji and line breaks optimized for mobile reading.
  • Include coin symbol, volume surge ratio, setup type, entry zone, TP, SL, and a caution to wait for lower timeframe confirmation.
  • Retry transient delivery failures with capped exponential backoff.
  • Log message status, chat ID, and delivery timestamp for auditability.

Alert Suppression and Administration · Medium priority

  • Prevent repeated alerts on the same coin and expose basic operational controls.
  • Apply a 30-minute cooldown per symbol after a successful alert.
  • Allow configurable cooldown duration through environment configuration.
  • Expose basic health status and last scan timestamp for monitoring.
  • Keep a simple local audit log of sent alerts and rejected setups.
  • Support manual reset of cooldown state for admin maintenance.

Onboarding and First Alert Setup

  • Create or reuse a Telegram bot and enter the bot token.
  • Connect the destination chat or channel ID.
  • Choose exchange sources, default Binance and Bybit, plus scan mode.
  • Set risk and alert parameters such as cooldown and symbol exclusions.
  • Run a test scan on a few symbols to validate delivery.
  • Time to first usable alert should be under 10 minutes for a prepared user.

1. Configure Connections

  • The user adds Telegram credentials and selects exchanges to scan.
  • Validate bot token format before saving.
  • Confirm chat or channel permissions before enabling alerts.
  • Show clear error states for invalid tokens or inaccessible chats.

2. Start Market Scan

  • The system begins scanning configured USDT pairs on a repeating schedule.
  • Fetch OHLCV data in batches to stay within rate limits.
  • Skip inactive or delisted symbols automatically.
  • Surface last scan time and scan progress in the UI or logs.

3. Evaluate Setup Rules

  • Each symbol is processed against volume, impulse, and Fibonacci conditions.
  • Compute average volume from the prior 10 closed candles.
  • Verify impulse and pullback thresholds before a signal is emitted.
  • Reject ambiguous setups and log the reason for debugging.

4. Send Structured Alert

  • When conditions pass, the bot dispatches a formatted Telegram message.
  • Render the alert with symbol, volume ratio, entry, TP, SL, and notes.
  • Include a concise caveat to wait for lower timeframe confirmation.
  • Retry delivery once or twice if Telegram returns a temporary failure.

5. Suppress Duplicates

  • After a successful alert, the symbol enters cooldown to reduce spam.
  • Do not rescan the symbol for alerting during the cooldown window.
  • Store cooldown state persistently so restarts do not reset suppression.
  • Allow admin override for debugging or maintenance.

Advanced and Power User Features

  • Custom threshold presets per exchange or symbol group.
  • Optional direction filters for long-only or short-only alerting.
  • Detailed alert logs with filter pass/fail reasons and latency metrics.
  • Manual symbol blacklist and whitelist management.
  • Graceful restart recovery that restores cooldown and scan state from storage.

Mobile-First Operational UI

  • Simple dashboard focused on status, last scan, active alerts, and errors.
  • High-contrast cards for signal confidence, timing, and risk levels.
  • Readable typography and compact layouts that work well on phones.
  • Clear loading, retry, and offline states for API-dependent screens.
  • Accessible labels and color-independent status indicators for critical alert states.

Andi used to watch five-minute charts all evening, trying to catch pullbacks after strong moves. He often entered late or skipped valid setups because he could not monitor every pair at once.

With PulseFibo, he connects Telegram, chooses Binance and Bybit, and lets the bot scan USDT pairs continuously. When a coin shows a 2.5x volume surge, a strong impulse, and a pullback into the ICT Fibonacci zone, he gets a clean alert with entry, TP, and SL in seconds.

Now Andi can review a signal on his phone, decide quickly, and avoid repeated noise on the same symbol. He spends less time staring at charts, acts more consistently, and gets a workflow that scales as market activity changes.

User-Centric Metrics

  • Median time from signal detection to Telegram delivery under 15 seconds.
  • At least 80 percent of alerts are judged readable and actionable by user survey.
  • Fewer than 5 percent of alerts are reported as malformed or missing key fields.
  • At least 60 percent of active users configure and keep scanning enabled after 30 days.
  • Cooldown feature reduces duplicate alerts on the same symbol by at least 90 percent within the suppression window.

Business Metrics

  • Reach 500 monthly active users within 6 months.
  • Convert at least 35 percent of activated users to a paid plan within 90 days of monetization.
  • Maintain monthly churn below 8 percent after the first billing cycle.
  • Drive at least 20 percent of new signups through referral or community sharing.
  • Achieve a support burden below 0.5 tickets per active user per month.

Technical Metrics

  • Monthly uptime at or above 99.9 percent.
  • P95 scan loop completion under 20 seconds for the configured symbol universe.
  • Telegram message delivery success above 99 percent excluding user-side chat restrictions.
  • Zero critical secrets exposed in logs or client-side code.

Tracking Plan

  • event_scan_started with exchange list, symbol count, and scan version.
  • event_ohlcv_fetch_succeeded with exchange, symbol, timeframe, and latency.
  • event_signal_rejected with reason code such as low volume, weak impulse, or invalid fib zone.
  • event_signal_triggered with symbol, direction, volume ratio, entry, TP, SL, and latency.
  • event_telegram_delivery_succeeded with chat ID, message length, and send time.
  • event_telegram_delivery_failed with error class and retry count.
  • event_cooldown_applied with symbol and cooldown expiry time.

Technical Needs

  • Python 3.9 or newer service runtime.
  • ccxt for normalized exchange market data access.
  • pandas for candle processing and rolling average calculations.
  • requests for Telegram Bot API HTTP calls.
  • Persistent storage for cooldown state and sent alert logs, using SQLite for MVP and Postgres for scale.
  • Background worker or scheduler such as APScheduler, cron, or Celery depending on deployment model.
  • Environment-based secret management for bot token, exchange settings, and alert configuration.

Integration Points

  • Binance market data API through ccxt.
  • Bybit market data API through ccxt.
  • Telegram Bot API for outbound alerts.
  • VPS or cloud hosting provider such as Ubuntu on DigitalOcean, Render, or Railway.
  • Optional observability integration such as Sentry for exception capture.

Data Storage & Privacy

  • Store only the minimum user configuration required to send alerts and manage cooldowns.
  • Encrypt or secret-manage Telegram tokens and any future API keys; never expose them in logs.
  • Keep audit logs for alert generation and delivery status with retention limits, such as 30 to 90 days.
  • Provide a way to delete all stored configuration and alert history for a user or deployment.
  • If user contact or billing data is added later, align handling with GDPR and CCPA principles for consent and deletion.

Scalability & Performance

  • Use batched symbol fetching and staggered scheduling to reduce API throttling.
  • Cache exchange metadata and precision rules to avoid recalculating them on every cycle.
  • Design the scan loop to continue even if one exchange or symbol fails.
  • Separate market scanning from Telegram delivery so slow messaging does not block detection.

Potential Challenges

  • Exchange API rate limits could slow scans; mitigate with batching, request pacing, and exchange-specific backoff.
  • False positives may occur in highly volatile conditions; mitigate with stricter candle validation and optional confirmation filters.
  • Telegram delivery failures could hide alerts; mitigate with retries, persistent logs, and delivery status monitoring.
  • Precision mismatches can produce invalid TP or SL levels; mitigate by rounding with exchange-specific tick size rules.
  • Server restarts could reset cooldown state; mitigate with persistent storage for alert history and cooldown expiries.

Team & resourcing - Small team - 2 engineers, 1 product designer, part-time PM, and shared DevOps support

Phase 1: MVP Signal Bot · Weeks 1-3

  • ccxt-based market scanner for Binance and Bybit
  • Volume surge, impulse move, and Fibonacci pullback detection
  • Telegram alert delivery with structured message format
  • Local cooldown suppression and basic error logging

Phase 2: Reliability and Controls · Weeks 4-5

  • Persistent storage for cooldown and alert history
  • Retry logic, health checks, and scan latency metrics
  • Admin configuration for thresholds, exclusions, and cooldown duration
  • Improved logging and failure visibility

Phase 3: User Operations Layer · Weeks 6-7

  • Minimal dashboard or command interface for status and configuration
  • Signal history view with alert reasons and timestamps
  • Manual test alert and connection validation flows
  • Basic analytics instrumentation for product usage

Phase 4: Scale and Premium Readiness · Weeks 8-10

  • Performance tuning for larger symbol universes
  • Sentry or equivalent exception monitoring
  • Prepared architecture for paid plans and multi-channel delivery
  • Foundation for future features like FVG, multi-timeframe confirmation, and auto-trading webhooks

Paste this into Cursor, Bolt, Lovable, or v0 to start building.

Build a production-ready crypto signal bot called PulseFibo.

Product summary:
A Telegram alert bot that scans Binance and Bybit USDT pairs for crypto scalping setups using three rules: 2.5x volume surge over the prior 10 candles, at least 1.5 percent impulse move, and pullback into the ICT OTE Fibonacci zone between 0.618 and 0.786. When a setup passes, send a structured Telegram alert with entry, take profit, stop loss, volume ratio, and a short note to wait for lower-timeframe confirmation. Include a 30-minute per-symbol cooldown to prevent spam.

Default tech stack:
Frontend: simple mobile-first admin dashboard with Next.js and Tailwind.
Backend: Python 3.11 with FastAPI for config and health endpoints, and a background scanner worker using ccxt, pandas, and APScheduler.
Storage: SQLite for MVP, designed to migrate cleanly to Postgres.
Observability: structured JSON logs and Sentry integration.
Deployment: Dockerized app for VPS deployment.

Core screens/flows:
1. Setup screen to enter Telegram bot token, chat ID, exchange selection, cooldown minutes, and symbol exclusions.
2. Dashboard showing scan status, last scan time, active symbols, last alerts, and errors.
3. Signal history screen with filter pass/fail reasons, timestamps, and alert payload preview.
4. Settings screen for thresholds, precision, and retry behavior.
5. Test alert flow to verify Telegram delivery.

Backend requirements:
- Fetch OHLCV for all active USDT pairs on Binance and Bybit.
- Exclude leveraged tokens and symbols containing UP, DOWN, BULL, BEAR.
- Compute rolling average volume from the last 10 completed candles.
- Detect impulse move and Fibonacci zone using the most recent valid swing high and swing low.
- Validate current close is between Fib 0.786 and Fib 0.618 for a long setup.
- Calculate TP at swing high and SL 0.5 percent below swing low.
- Round prices to exchange precision.
- Persist cooldown state and alert history.
- Retry Telegram delivery with capped exponential backoff.
- Never crash on API or network errors; log and continue scanning.

Data model:
UserConfig(id, telegram_bot_token, telegram_chat_id, exchanges, cooldown_minutes, volume_multiplier, impulse_percent, enabled_symbols, excluded_symbols, created_at, updated_at)
SignalEvent(id, exchange, symbol, timeframe, direction, volume_ratio, impulse_percent, fib_618, fib_786, entry_price, take_profit, stop_loss, status, reason, detected_at, delivered_at)
CooldownState(symbol, cooldown_until, last_alert_at)
DeliveryLog(id, signal_event_id, provider, status, error_message, attempt_count, created_at)

Generate the full app with clean separation between scanner logic, strategy rules, Telegram dispatcher, persistence layer, and admin UI. Include seed config, validation, error handling, and a polished responsive UI optimized for mobile operators.

Business Idea

Berikut adalah dokumen **Product Requirement Document (PRD)** lengkap untuk pembuatan **ICT & Volume-Based Crypto Scalping Telegram Bot**. Dokumen ini dirancang sebagai panduan komprehensif bagi developer, trader, maupun tim eksekusi agar pengembangan sistem berjalan terstruktur dan sesuai target fungsi. --- # 📄 Product Requirement Document (PRD) ## 📌 1. Document Overview * **Nama Produk:** Crypto ICT & Volume Scalping Telegram Alert Bot * **Versi Document:** 1.0 * **Tanggal:** 14 Oktober 2026 * **Status:** Draft / Ready for Development * **Target Pengguna:** Trader Crypto Scalper (Spesialisasi ICT / Smart Money Concept) --- ## 🎯 2. Product Summary & Objectives Bot ini bertugas memindai (*scan*) pasar *Cryptocurrency* secara real-time pada bursa (contoh: Binance / Bybit) untuk menemukan setup scalping berprobabilitas tinggi. Bot berfokus pada **lonjakan volume institusional (Volume Surge)**, **pola pergerakan harga ICT (Optimal Trade Entry / OTE)**, serta **Fibonacci Retracement (0.618 - 0.786)**. Begitu kriteria terpenuhi, bot akan langsung mengirimkan *signal alert* yang terstruktur ke channel/chat Telegram. ### **Tujuan Utama:** 1. Otomatisasi pemantauan ratusan pasangan koin (*USDT Pairs*) secara bersamaan. 2. Mengeliminasi *FOMO* dan *emotional bias* trader melalui parameter teknis yang objektif. 3. Memberikan notifikasi instan dengan data konkret (*Entry, TP, SL, Volume Surge Ratio, Level Fibo*). --- ## 👥 3. User Personas & Use Cases * **Persona:** Scalper trader yang tidak memiliki waktu untuk memantau chart 24/7, namun ingin mendapatkan notifikasi saat ada *smart money entry* di area krusial. * **Use Case:** 1. Bot mendeteksi lonjakan volume besar pada koin **ABC/USDT** di timeframe 5m. 2. Harga membuat pergerakan impulsif naik (*Impulse Move*), lalu mengalami *pullback* ke area Golden Pocket Fibonacci (0.618 - 0.786). 3. Bot memvalidasi parameter dan mengirimkan format pesan lengkap ke grup Telegram pengguna. 4. Pengguna mengeksekusi perdagangan secara manual/otomatis sesuai rekomendasi. --- ## ⚙️ 4. Functional Requirements (Fitur & Logika) ### **4.1. Market Data Ingestion & Scanning** * **Exchange Integration:** Menggunakan API Public (melalui pustaka `ccxt`) dari Binance/Bybit. * **Pair Filtering:** Memindai seluruh pasangan berpasangan dengan USDT (mengecualikan koin *Leveraged Tokens* seperti UP/DOWN, BULL/BEAR). * **Timeframe Scanning:** Timeframe utama 5 Menit (`5m`) untuk analisis struktur dan volume. ### **4.2. Strategy Core Engine (Logic & Thresholds)** 1. **Volume Surge Filter:** * Volume candle terkini ($\text{Candle}_{t-1}$) wajib minimal **$2.5\times$** lipat dari rata-rata volume 10 candle sebelumnya. 2. **Impulse Move Filter:** * Kenaikan harga candle impulsif minimal **$1.5\%$** dalam rentang candle yang sama. 3. **ICT Optimal Trade Entry (OTE) + Fibonacci Retracement:** * Menghitung *Swing High* dan *Swing Low* dari rentang pergerakan impulsif terakhir. * Menghitung nilai Fibonacci: $$\text{Fib 0.618} = \text{High} - (\text{High} - \text{Low}) \times 0.618$$ $$\text{Fib 0.786} = \text{High} - (\text{High} - \text{Low}) \times 0.786$$ * **Sinyal Valid:** Jika harga saat ini (*Current Close*) terdeteksi sedang *pullback* dan berada di area antara $\text{Fib 0.786}$ hingga $\text{Fib 0.618}$. ### **4.3. Risk & Management Engine** * **Dynamic Take Profit (TP):** Ditetapkan pada level *Swing High* pergerakan impulsif awal. * **Dynamic Stop Loss (SL):** Ditetapkan $0.5\%$ di bawah level *Swing Low* pergerakan impulsif. * **Cooldown Alert Manager:** Mencegah spam pesan. Koin yang sudah terkirim notifikasinya tidak akan di-scan ulang selama **30 menit**. ### **4.4. Telegram Alert Dispatcher** * Mengirim notifikasi menggunakan Telegram Bot API via HTTP POST request. * Menggunakan format pesan Markdown agar rapi, berstruktur, dan mudah dibaca secara cepat di smartphone. --- ## 🎨 5. Message Interface & Output Spec Pesan yang dikirimkan ke Telegram harus mengikuti struktur visual berikut: ```text 🎯 ICT + FIBO SCALP SETUP TERDETEKSI! 🎯 📌 Koin: #SOLUSDT 📈 Lonjakan Volume: 3.2x dari rata-rata 📊 Kondisi: Pullback ke Area ICT OTE (Fib 0.618 - 0.786) 💵 Area Entry: 142.50 🎯 Target TP: 146.20 (+2.6%) 🛑 Stop Loss: 140.80 (-1.2%) 💡 Catatan ICT: Tunggu konfirmasi Choch / MSS di timeframe 1m sebelum entry. ``` --- ## 🏗️ 6. Non-Functional Requirements (Sistem & Infrastruktur) | Kategori | Spesifikasi / Syarat | | --- | --- | | **Bahasa Pemrograman** | Python 3.9+ | | **Pustaka Utama** | `ccxt`, `pandas`, `requests`, `time` | | **Kecepatan Scan** | Rata-rata 1 siklus pemindaian selesai dalam $\le 20$ detik | | **Reliability** | *Exception handling* penuh pada koneksi API agar bot tidak crash saat error jaringan | | **Infrastruktur Deployment** | VPS Linux (Ubuntu 22.04 LTS) atau Cloud PaaS (PythonAnywhere/Heroku) | | **Uptime Target** | $99.9\%$ (24 jam nonstop) | --- ## 🗺️ 7. Roadmap & Future Improvements (Phase 2) 1. **Multi-Timeframe Confluence:** Menambahkan konfirmasi trend dari timeframe 1 Jam (`1h`). 2. **Fair Value Gap (FVG) Detector:** Otomatisasi deteksi FVG (*Imbalance*) tepat di zona Fibonacci. 3. **Auto-Trading Execution (Webhooks):** Integrasi langsung ke 3Commas / Cornix / TradingView Webhooks untuk eksekusi order *buy/sell* otomatis tanpa intervensi manual. 4. **Dashboard Analytics:** Pembuatan Web Dashboard untuk memantau Win-Rate sinyal yang dikeluarkan oleh bot. --- ## 🚀 8. Kriteria Kelayakan Launching (Acceptance Criteria) * [x] Bot berhasil terhubung ke API Binance dan mengambil data OHLCV tanpa error. * [x] Logika perhitungan Fibonacci 0.618–0.786 teruji presisi sesuai chart. * [x] Bot mampu memfilter koin yang tidak memenuhi kriteria lonjakan volume ($< 2.5\times$). * [x] Notifikasi Telegram masuk secara *real-time* dengan penulisan format yang rapi dan konsisten. * [x] Mekanisme *Cooldown* 30 menit berfungsi menahan *spam alert* untuk koin yang sama.

Make My PRD

Design by The Resonance | Powered by GPC – The AI Transformation Company

    PRD: Berikut adalah dokumen **Product Requirement Document...