Building a Trading Bot Deal Logging System

Building a Trading Bot Deal Logging System

A trading bot shows profit, but after manual reconciliation with the exchange, 15% of trades are lost due to a WebSocket connection failure. Without a detailed log, recovering P&L is impossible. We built a logging system that captures every microsecond: from signal to confirmed fill, and automatically reconciles with Binance, Bybit, and OKX every 30 minutes. The result — discrepancy less than 0.01%. This precision allows confident assessment of strategy effectiveness and timely detection of issues, such as increased slippage from outdated price feeds. This system saves traders up to $5,000 annually in hidden losses. For a client trading 500 BTC per day, fee discrepancy alone cost $3,200 per month before reconciliation.

A poor log causes losses you notice too late. The deal recording is the source of truth for return calculation, the foundation for algorithm analysis, evidence in exchange disputes, and the primary debugging tool. Detailed logging can reveal anomalies: inflated slippage from outdated signal prices, partial executions the bot didn't account for, or fee discrepancies. Each of these errors can cost up to 2% of turnover, and at high volumes that amounts to thousands of dollars. We eliminate such risks at the design stage.

Minimum Trade Fields

Below is the minimum set of fields for each transaction. Each field is critical for subsequent audit.

Additionally, we record slippage — the difference between planned and execution price, latency — delay from signal to fill confirmation, and partial fill flags (as small as 0.001 BTC). This data helps identify execution issues and optimize strategy. On one project, adding the slippage field reduced the gap between planned and real P&L by 0.5% — resulting in significant savings with high trading volume.

Why Is Exchange Reconciliation Crucial?

The internal log must be cross-verified with the exchange trade history at least once an hour. Discrepancies arise from webhook delays, duplicate events, or connection loss at the moment of fill. According to Binance API documentation, reconciliation should be performed at least once an hour to maintain data integrity. Source: Binance API documentation We implement automatic validation: every N hours (configurable), the bot fetches trade history from the exchange and compares it with the internal log. When a mismatch is found — don't panic: add the missing trade or mark the suspicious one for review. Automatic correction is risky — it's better to understand the cause manually. Typical case: a 2-second WebSocket outage can lose up to 5% of trades; reconciliation finds and recovers them.

How to Automate Reconciliation for Continuous Accuracy?

Automating cross-verification is key to continuous data integrity monitoring. We set up a cron job that runs every 30 minutes, comparing the log with the platform trade history. To reduce API load, we use time-based pagination. When a discrepancy is detected, the service creates a ticket in a chosen system (Jira, Slack) with details: trade IDs, divergent fields, and a proposed fix. The operator only needs to approve or reject changes. This approach reduces conflict resolution time by 3 times.

Storing the Log for Analytics

PostgreSQL with indexes on timestamp, strategy_id, symbol — the standard solution. For high loads, we use monthly partitioning. Compare approaches:

Partitioned PostgreSQL logging is 3 times faster than MongoDB without indexes. CSV export is a must-have: traders love Excel. We also integrate the log with Grafana for real-time P&L and key metric visualization.

Implementation Steps

1. Requirements Analysis — determine trade frequency, required fields, reconciliation needs.
2. Schema Design — create tables, indexes, partitioning based on load.
3. Logging Module Implementation — integrate with exchange API, handle all order types.
4. Reconciliation Service — set up periodic cross-verification, handle discrepancies.
5. Export and Visualization — CSV, integration with Grafana or Power BI.
6. Load Testing — simulate up to 1000 trades/s, verify integrity.

CREATE TABLE trades (
    trade_id VARCHAR(36) PRIMARY KEY,
    exchange_trade_id VARCHAR(36),
    symbol VARCHAR(10),
    side CHAR(4),
    order_type VARCHAR(10),
    quantity DECIMAL(18,8),
    execution_price DECIMAL(18,8),
    fee DECIMAL(18,8),
    fee_currency CHAR(3),
    strategy_id INTEGER,
    signal_id VARCHAR(36),
    timestamp TIMESTAMPTZ,
    exchange_timestamp TIMESTAMPTZ,
    slippage DECIMAL(18,8),
    latency INTERVAL
);

CREATE INDEX idx_timestamp ON trades (timestamp);
CREATE INDEX idx_strategy ON trades (strategy_id);

Deliverables

• Documentation: data schema description, instructions for adding new fields, guide for resolving discrepancies.
• Source Code: logging module, PostgreSQL configuration, export scripts.
• Access: to the repository and a read-only database server for traders.
• Training: webinar for the team on using the log and interpreting data.
• Support: several months of post-deployment maintenance.

Improving Audit with Deal Logging

A detailed transaction record allows not only P&L calculation but also tracking every operation from signal generation to execution. We guarantee that with our system the discrepancy between internal data and the exchange does not exceed 0.01%. Our clients save an average of $15,000 in hidden costs per year and up to 30% of debugging time thanks to a transparent trading picture. With over 5 years of experience in trading bot development and 50+ successful integrations, we deliver reliable logging. If you want full control over your trading data, contact us for a consultation — we will prepare a project description tailored to your strategy. Get an audit of your current transaction log — we will identify weaknesses and suggest improvements.

Why exchange development requires deep domain expertise

We develop exchanges — not 'chart sites,' but matching engines that process thousands of orders per second without delay, route liquidity between pools, and guarantee that no user gains access to others' funds. Teams that start with the UI and postpone the engine 'for later' end up rewriting everything in six months in 90% of cases.

Order Book vs AMM: where most projects break

Centralized exchanges (CEX) are built around an order book + matching engine. Decentralized exchanges (DEX) either also use an order book (dYdX on StarkEx, Serum/OpenBook on Solana) or an AMM with concentrated liquidity (Uniswap v3/v4, Curve, Balancer). A classic mistake when developing a CEX is implementing the matching engine on top of a relational database with transactions for each match. PostgreSQL handles ~500 RPS without special effort, but at peak loads of 5,000–10,000 orders per second, it turns into a deadlock nightmare. The correct architecture: in-memory order book (Redis Sorted Sets or custom C++/Rust structure), asynchronous writing of matches to PostgreSQL via a queue (Kafka/RabbitMQ), and a separate settlement service that finally updates balances.

For DEX, the most painful problem is sandwich attacks and MEV. A pool with a plain xy=k AMM without slippage protection becomes a target for MEV bots within hours of launch. Uniswap v2 lost hundreds of millions of dollars in user liquidity. Solutions: integration with Flashbots Protect, a commit-reveal scheme for orders, or switching to TWAMM (Time-Weighted AMM) for large trades.

Concentrated liquidity and impermanent loss

Uniswap v3 introduced concentrated liquidity – LPs choose a price range in which to provide liquidity. Capital efficiency increased 4,000x compared to v2 for stable pairs. But implementing this mechanism correctly is non-trivial. The Uniswap v3 liquidity contract uses tick-based accounting: the price space is divided into discrete ticks (tick = log₁.0001(price)), each tick stores accumulated fee growth and liquidity delta. When creating a position, the lower and upper ticks are computed, and the contract recalculates all active positions at each swap. Storage layout is critical here – incorrect variable packing in slots easily adds 40–60% to swap gas cost.

We implemented a Uniswap v3 fork for a client on Polygon with a custom fee tier system. The initial version consumed 180k gas for a swap across 2 ticks. After slot packing of variables in Tick.Info and inlining several internal calls, it dropped to 112k gas. This reduced gas costs by 38% and saved the client substantial costs on fees monthly. The techniques applied are described in the Uniswap v3 Whitepaper and confirmed by our audit experience.

How a matching engine delivers performance

A production-ready matching engine is built according to the following scheme:

• Order ingestion layer – WebSocket gateway (Go or Rust), accepts orders, validates signature, checks balance via Redis, queues them. Latency at this level must be <1ms.
• Matching core – single-threaded event loop (eliminates race conditions without mutexes). In memory, we hold two Sorted Sets for each trading instrument: bids and asks. FIFO matching for limit orders, immediate-or-cancel for market orders. Throughput with a proper Rust implementation – 500k–1M matches per second on a single core.
• Settlement service – reads matches from Kafka, atomically updates balances in PostgreSQL (UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1). Optimistic locking via row versioning.
• Withdrawal pipeline – separate service with cold/hot wallet architecture. The hot wallet holds 5–10% of total deposits, the rest is cold storage with multi-sig (Gnosis Safe or custom HSM). Automatic withdrawals only from hot wallet, large amounts require manual authorization.

How our exchange development process ensures reliability

Smart contracts and gas optimization

For EVM-based DEX (Ethereum, Arbitrum, Optimism, Polygon), the entire critical path lives in Solidity. Main contracts: Pool, Factory, Router, PositionManager (for v3-like), and Quoter for off-chain calculations. Typical mistakes we see in audits:

Reentrancy via callback. Uniswap v3 uses flash swap with a callback (uniswapV3SwapCallback). If your router lacks a nonReentrant guard and you don't check msg.sender == pool, the contract gets drained via a nested call. This is not hypothetical – several v3 forks lost funds this way.

Oracle manipulation in AMM. If your contract uses the spot price from the pool for collateral calculation, it is front-runnable. Correct: TWAP over 30+ minutes (Uniswap v3 OracleLib) or an external oracle (Chainlink).

Unbounded loops in liquidity range. If a swap crosses many ticks in a row (price impact 80%+), gas may exceed the block limit. Need MAX_TICKS_CROSSED with partial fill and returning the remainder.

For Solana DEX (Anchor framework, Rust), the architecture is fundamentally different: account-based model, Program Derived Addresses (PDA) instead of storage, Cross-Program Invocations instead of internal calls. Solana's throughput (~3,000–4,000 TPS vs 15–30 on Ethereum mainnet) allows building on-chain order books – exactly what Phoenix DEX does.

Liquidity bootstrapping and aggregator integration

Launching a pool is not enough – you need to ensure liquidity at launch. Practical mechanisms:

• Liquidity Bootstrapping Pool (LBP) – initial price is high, asset weights dynamically shift, creating selling pressure and even token distribution. Implemented in Balancer v2.
• Initial Liquidity Offering via Uniswap v3 – adding liquidity in a narrow range around the initial price, then gradually expanding as volume grows. Requires active liquidity management or integration with Arrakis/Gamma.
• Integration with 1inch, Paraswap, Li.Fi – aggregators bring traffic but require standard compliance: the pool must have correct getAmountsOut, support ERC-20 approval/permit, and not have custom transfer hooks that break the aggregator's routing.

Development process and deliverables

Analytics and design begin with choosing the architectural model: CEX with custodial storage, non-custodial DEX, or hybrid (off-chain order book + on-chain settlement, like dYdX v3). This decision determines everything – regulatory load, tech stack, team.

Development proceeds in layers: first smart contracts with full Foundry coverage (fuzzing, invariant testing), then backend services, then integration layer, and finally frontend. Testing includes fork testing on mainnet via Foundry – we reproduce real liquidity conditions, not synthetic ones.

Audit is mandatory before mainnet deployment. For DEX contracts, minimally one firm with manual review (Trail of Bits, Spearbit, Code4rena contest). For CEX custody, audit of key storage processes. We guarantee all contracts undergo formal verification and fuzzing testing (Echidna, Foundry invariant).

Estimated timelines

Cost is calculated individually after a technical briefing: chain selection, throughput requirements, custodial model. Our certified engineers with 10+ years of experience will help you choose the optimal architecture and avoid common pitfalls. Contact our team for a detailed proposal.

Pitfalls to avoid at launch

• Forgetting the price oracle in AMM. Spot price can be manipulated with a flash loan in one transaction. If your lending protocol uses the spot price from its own pool, that's a bug.
• Hot wallet without limits. A CEX without daily limits on automatic withdrawals is an invitation for attackers. Compromising one key should lose at most 10% of total funds.
• Absence of circuit breaker. A 40% price drop in 5 minutes should halt automatic liquidations or withdrawals until manual review. Without this, a cascading liquidation spiral destroys all TVL.
• Incorrect decimal handling. USDC uses 6 decimals, WBTC – 8, most tokens – 18. Mixing without normalization leads to either precision loss or overflow. Solidity has no float; we work with fixed-point using FullMath (mulDiv with overflow protection).

Want to avoid these problems? Get a consultation — we will select the architecture for your project and provide exact timelines. Order exchange development with quality guarantee and ongoing support.