Kaiyn Trading Bot

Kaiyn Capital · Execution Infrastructure

Kaiyn Trading Bot

A confirmation-first Telegram workflow for Bitget USDT-FUTURES, designed around explicit risk limits, deterministic order identity, and operations that can be reviewed.

View repository Read portfolio case study
Confirmation first Preview before execution
Deterministic identity Traceable order lifecycle
Auditable operations Health, alerts, and backups

Execution workflow

A signal becomes an order only after explicit confirmation.

Telegram actions create persistent pending orders. The system calculates size, validates exchange constraints, then validates again before sending a confirmed order to Bitget.

Telegram trading signal workflow showing market and GTC limit order confirmation
Signal intake, confirmation preview, exchange-rule validation, and execution summary.

Engineering pillars

Execution integrity, risk controls, and operational readiness.

The design treats safe state transitions and recoverable operations as part of the product, not as infrastructure added after launch.

01 / Execution

Execution integrity

Persistent state and exchange reconciliation are used to reduce ambiguous or duplicated submissions.

  • Confirmation previews
  • Market and GTC limit flows
  • Deterministic client order IDs
  • Row locking and reconciliation
02 / Risk

Risk controls

Order sizing and exchange constraints are checked before a request reaches the submission boundary.

  • Fixed 1R sizing
  • Position and daily trade caps
  • Decimal financial calculations
  • Encrypted API credentials
03 / Operations

Operational readiness

Health checks, audits, retention, and restore procedures keep operating state visible and recoverable.

  • Admin health and error alerts
  • Structured audit events
  • Retention and local backups
  • Encrypted R2 offsite backup
Operational screenshots showing health checks, audit records, and Docker Compose CI
Admin health output, audit visibility, and Docker-first verification.

Operational evidence

Operations are part of the product surface.

The same Telegram interface used for execution also exposes concise operational context to administrators.

01

Health visibility

Inspect database, backup, cleanup, and Bitget API status from Telegram.

02

Reviewable events

Order, channel, admin, and system actions are recorded for later review.

03

Recovery path

Retention, local dumps, encrypted offsite backup, and restore runbooks are included.

Technical foundation

A deployment path that mirrors verification.

Application

Python 3.11 · python-telegram-bot · Bitget REST API · Fernet encryption

State and runtime

PostgreSQL 16 · SQLAlchemy asyncio · Alembic · Docker Compose

Verification and delivery

Ruff · mypy · pytest · GitHub Actions · GHCR · VPS deployment

Documentation

Inspect the workflow and operating assumptions.

The repository documents command usage, execution state, deployment, and recovery procedures.

Command referenceTelegram commands, signal syntax, and smoke tests. Trading flowPending orders, validation, reconciliation, and schema. Deployment runbookDigitalOcean VPS deployment, rollback, and troubleshooting. Backup and restorePostgreSQL restore verification and recovery procedures.