Telegram signal intake
Admins publish tradeable signals and forward them to managed channels, groups, and forum topics.
Kaiyn Trading Bot
Telegram-based Bitget USDT-FUTURES signal execution with encrypted API credentials, fixed 1R sizing, order confirmation, audit records, backups, and Docker-first deployment.
Built for confirmed signal execution.
The bot keeps trading flow state in PostgreSQL, validates Bitget contract rules before execution, and records operational events for admins.
Pending order confirmation
Users confirm market or GTC limit orders before execution, with row locking to guard duplicate clicks.
Encrypted credentials
Bitget API key, secret key, and passphrase are stored with Fernet encryption.
Fixed 1R sizing
Order previews calculate trade size from each user's configured fixed 1R risk amount.
Audit and alerts
Admin commands expose system health, recent audit events, backup state, and error summaries.
Docker-first runtime
PostgreSQL, bot, maintenance, and backup services run through Docker Compose.
Market and limit execution flow.
Signals become Telegram actions, actions become pending orders, and confirmed orders are validated again before submission to Bitget.
Operational readiness is part of the product surface.
Health checks
Admins can inspect bot, DB, backup, cleanup, and Bitget API status from Telegram.
Structured audit trail
Order, channel, admin, and system actions are recorded for review.
Retention and backup
Maintenance cleanup and daily PostgreSQL backup are included in the Compose runtime.
Python, PostgreSQL, Docker Compose.
The project is built around a Python 3.11 runtime, async SQLAlchemy, Alembic migrations, and CI checks that mirror the deployment path.
Python 3.11
python-telegram-bot
Bitget REST API
PostgreSQL 16
SQLAlchemy asyncio
Alembic
Fernet encryption
Docker Compose
Ruff
pytest
GitHub Actions
GHCR
Read the runbooks and command references.
Project documentation covers command usage, trading flow behavior, deployment, backup restore checks, and production readiness.