How 20kevit/tele-mexc works
tg-signal-ingest ingests one selected Telegram channel, durably records its messages and recovery history, then parses eligible signals into guarded Spot order intents. The runtime separates ingestion, signal/trade lifecycle, exchange access, persistence, and owner operations. MEXC writes use the official CLI adapter, while REST supports read-only exchange data; the control bot is an operational interface, not a separate trading decision path. Relationships below follow the README and shown source references; several listed subsystems have no implementation excerpt, so their internal links are omitted.
Main entry points: engine.py Intent engine · tg_signal_ingest/service.py Live listener · trade_manager.py Trade lifecycle · control/service.py Owner control bot
Components 23
Telegram ingestion
- Live listener
tg_signal_ingest/service.py - Telegram client
tg_signal_ingest/telethon.py - Backfill and recovery
tg_signal_ingest/backfill.py - Message normalization
tg_signal_ingest/normalize.py - Processing queue
tg_signal_ingest/processing.py
Signal and trading
- Signal parser
tg_signal_ingest/trading/parser.py - Intent engine
tg_signal_ingest/trading/engine.py - Risk controls
tg_signal_ingest/trading/risk.py - Trade lifecycle
tg_signal_ingest/trading/trade_manager.py - Market monitor
tg_signal_ingest/trading/monitor.py
Durable state
- Trading state
tg_signal_ingest/trading/store.py - Trade records
tg_signal_ingest/trading/trade_store.py - Message repository
tg_signal_ingest/repository.py - SQLite database
tg_signal_ingest/db.py
MEXC integration
- Spot REST client
tg_signal_ingest/mexc/client.py - Spot write adapter
tg_signal_ingest/mexc/cli.py
Operations and control
- Runtime configuration
tg_signal_ingest/config.py - Owner control bot
tg_signal_ingest/control/service.py - Control bot API
tg_signal_ingest/control/bot_api.py - Notification worker
tg_signal_ingest/notification_dispatcher.py
Other components
- Telegram channel
- MEXC Spot
- Owners and operator
Connections 25
- Telegram channel → Telegram client: sends events
tg_signal_ingest/telethon.py - Telegram client → Live listener: provides updates
tg_signal_ingest/service.py - Live listener → Backfill and recovery: runs recovery
tg_signal_ingest/service.py - Live listener → Message repository: stores messages
tg_signal_ingest/service.py - Backfill and recovery → Message repository: persists history
tg_signal_ingest/backfill.py - Live listener → Processing queue: queues messages
tg_signal_ingest/service.py - Processing queue → Message normalization: normalizes content
- Intent engine → Signal parser: parses signals
tg_signal_ingest/trading/engine.py - Intent engine → Risk controls: checks eligibility
README.md - Intent engine → Trading state: records intents
tg_signal_ingest/trading/engine.py - Intent engine → Trade lifecycle: advances trades
README.md - Trade lifecycle → Spot write adapter: submits orders
README.md - Spot write adapter → MEXC Spot: writes Spot orders
README.md - Trade lifecycle → Spot REST client: reconciles read-only
README.md - Spot REST client → MEXC Spot: queries Spot data
tg_signal_ingest/mexc/client.py - Market monitor → Spot REST client: checks markets
README.md - Message repository → SQLite database: persists messages
tg_signal_ingest/repository.py - Trading state → SQLite database: persists intents
tg_signal_ingest/trading/store.py - Trade records → Trading state: uses trading state
tg_signal_ingest/trading/trade_store.py - Owners and operator → Owner control bot: operates service
README.md - Owner control bot → Control bot API: sends bot requests
tg_signal_ingest/control/service.py - Owner control bot → Runtime configuration: uses settings
tg_signal_ingest/control/service.py - Intent engine → Notification worker: appends events
README.md - Notification worker → Owners and operator: delivers alerts
README.md - Live listener → Runtime configuration: loads settings
tg_signal_ingest/service.py