How vladgnedko0x0/pulse-trader works
Pulse Nexus is a Telegram-operated trade management and automation platform. A trader enters a trade through the bot’s trade wizard and order flow; the application maintains trade and user state, applies trade and strategy rules, and uses exchange workers for order execution and position monitoring. Persisted trade and position data also supports history and statistics. The README documents Binance and Bybit, analytics, journaling, and security; excerpts show Binance-backed execution and database operations, but do not expose the full startup wiring or all feature implementations.
Main entry points: TGBotWorker.cs Bot worker · CacheOrdersWorker.TradeWizard.cs Trade wizard and order flow · BinanceWorker.cs Binance worker · DatabaseService.cs Database service
Components 23
Telegram interface
- Application startup
Pulse-Trader/Program.cs - Bot worker
Pulse-Trader/classes/TelegramAPI/TGBotWorker.cs - Trade wizard and order flow
Pulse-Trader/classes/TelegramAPI/Trading/CacheOrdersWorker.TradeWizard.cs - Order interaction
Pulse-Trader/classes/TelegramAPI/Trading/CacheOrdersWorker.OrderFlow.cs - User configuration
Pulse-Trader/classes/TelegramAPI/Configuration/CacheOrdersWorker.ConfigRoot.cs - Admin panel
Pulse-Trader/classes/TelegramAPI/Admin/CacheOrdersWorker.AdminPanel.cs
Trade management
- Trade model
Pulse-Trader/classes/Trading/TradeInfo.cs - Trade calculations
Pulse-Trader/classes/Trading/TradeMath.cs - Strategies and prerequisites
Pulse-Trader/classes/Trading/TradeStrategy.cs - Trade statistics
Pulse-Trader/classes/TelegramAPI/Statistics/CacheOrdersWorker.Statistics.cs
Exchange execution
- Exchange client interface
Pulse-Trader/classes/Exchanges APIs/IExchangeClient.cs - Binance worker
Pulse-Trader/classes/Exchanges APIs/BINANCE/BinanceWorker.cs - Bybit worker
Pulse-Trader/classes/Exchanges APIs/BYBIT/ByBitWorker.cs
Persistence and services
- Exchange and session state
Pulse-Trader/classes/Exchanges APIs/ExchangeWorkerState.cs - Database service
Pulse-Trader/classes/Database/DatabaseService.cs - User state
Pulse-Trader/classes/TelegramAPI/UserState.cs - Crypto utilities
Pulse-Trader/classes/CryptoUtilsF/CryptoUtils.cs - Localization
Pulse-Trader/classes/Localization/LocalizationService.cs
Other components
- Trader
- Telegram
- Binance API
- Bybit API
- MySQL
Connections 28
- Trader → Telegram: sends updates
- Telegram → Bot worker: delivers updates
- Application startup → Bot worker: initializes
- Application startup → Crypto utilities: initializes
- Application startup → Localization: initializes
- Bot worker → Trade wizard and order flow: dispatches trade actions
- Bot worker → Order interaction: dispatches order actions
- Bot worker → User configuration: dispatches settings
- Bot worker → Admin panel: dispatches admin actions
- Trade wizard and order flow → Trade model: creates trades
- Trade wizard and order flow → Trade calculations: uses calculations
- Trade wizard and order flow → Strategies and prerequisites: uses trade rules
- Order interaction → Trade model: updates trades
- Order interaction → Exchange client interface: gets exchange client
- Exchange client interface → Binance worker: implemented by
- Binance worker → Binance API: requests exchange operations
- Binance worker → Database service: saves positions
- Database service → MySQL: reads and writes
- Trade statistics → Database service: reads trade data
- Admin panel → Database service: queries users
- Admin panel → Exchange and session state: restores worker state
- Bot worker → User state: maintains sessions
- Trade statistics → Telegram: sends reports
- Binance worker → Telegram: sends notifications
- Localization → Trade wizard and order flow: supplies text
- Localization → Trade statistics: supplies text
- Exchange client interface → Bybit worker: optional implementation
- Bybit worker → Bybit API: documented integration