Training an RL Agent (PPO/SAC/DQN) for a Trading Strategy

We design and develop full-cycle blockchain solutions: from smart contract architecture to launching DeFi protocols, NFT marketplaces and crypto exchanges. Security audits, tokenomics, integration with existing infrastructure.
Showing 1 of 1All 1305 services
Training an RL Agent (PPO/SAC/DQN) for a Trading Strategy
Complex
from 2 weeks to 3 months
Frequently Asked Questions

Blockchain Development Services

Blockchain Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1361
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1189
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

Training an RL Agent (PPO/SAC/DQN) for a Trading Strategy

Imagine: you've spent months training a DQN agent on historical data, only to have it lose capital on the live market due to unaccounted slippage. In one of our projects, a client came with a similar problem: they trained PPO on minute candles, achieving a Sharpe ratio of 1.8 in testing, but in live trading the drawdown reached 40%. The client was losing around $15,000 monthly because of these shortcomings. We discovered that the environment did not account for fees and liquidity. After calibrating the reward and adding walk-forward validation, the Sharpe ratio climbed back to 1.5 and the drawdown dropped to 12%. This saved $4,000 per month.

Designing an RL agent for crypto trading is not just about picking an algorithm. You face market non-stationarity, hidden fees, slippage, and the risk of overfitting. We take on the full cycle—from building the data pipeline to live trading. We use proven algorithms PPO, SAC, and DQN, adapting them to your strategy. Our experience: over five years in blockchain development, 15+ projects for DeFi and CEX, including integration with Binance API. Contact us for a detailed analysis of your strategy.

Three Working Algorithms: DQN, PPO, SAC

Each algorithm has its niche. Let's look at their strengths and typical use cases.

DQN (Deep Q-Network)

Suitable for discrete actions (buy/hold/sell) and simple strategies. DQN approximates the Q-function: Q(state, action) — the expected discounted reward for taking action in state.

import torch
import torch.nn as nn
from collections import deque
import random

class DQNNetwork(nn.Module):
    def __init__(self, state_dim, n_actions, hidden_dim=256):
        super().__init__()
        # Dueling architecture: separate Value and Advantage streams
        self.shared = nn.Sequential(
            nn.Linear(state_dim, hidden_dim),
            nn.ReLU(),
            nn.Linear(hidden_dim, hidden_dim),
            nn.ReLU()
        )
        self.value_stream = nn.Linear(hidden_dim, 1)
        self.advantage_stream = nn.Linear(hidden_dim, n_actions)
    
    def forward(self, x):
        shared = self.shared(x)
        value = self.value_stream(shared)
        advantage = self.advantage_stream(shared)
        # Dueling: Q = V + (A - mean(A))
        q_values = value + (advantage - advantage.mean(dim=1, keepdim=True))
        return q_values

class PrioritizedReplayBuffer:
    """Prioritized Experience Replay — sample important transitions more often"""
    def __init__(self, capacity=50000, alpha=0.6):
        self.buffer = deque(maxlen=capacity)
        self.priorities = deque(maxlen=capacity)
        self.alpha = alpha
    
    def push(self, state, action, reward, next_state, done, td_error=1.0):
        priority = (abs(td_error) + 1e-5) ** self.alpha
        self.buffer.append((state, action, reward, next_state, done))
        self.priorities.append(priority)
    
    def sample(self, batch_size, beta=0.4):
        probs = np.array(self.priorities) / sum(self.priorities)
        indices = np.random.choice(len(self.buffer), batch_size, p=probs)
        
        # Importance sampling weights
        weights = (len(self.buffer) * probs[indices]) ** (-beta)
        weights /= weights.max()
        
        batch = [self.buffer[i] for i in indices]
        return batch, indices, weights

Double DQN eliminates Q-value overestimation: the online network selects the action, and the target network evaluates it.

# Double DQN target calculation
with torch.no_grad():
    next_actions = online_net(next_states).argmax(dim=1)  # online net selects
    next_q = target_net(next_states).gather(1, next_actions.unsqueeze(1))  # target evaluates
    targets = rewards + gamma * next_q * (1 - dones)

PPO (Proximal Policy Optimization)

Suitable for both discrete and continuous actions, on-policy, stable training. PPO limits the policy update size via clipping.

class PPOActor(nn.Module):
    def __init__(self, state_dim, action_dim, hidden_dim=256):
        super().__init__()
        self.network = nn.Sequential(
            nn.Linear(state_dim, hidden_dim),
            nn.Tanh(),
            nn.Linear(hidden_dim, hidden_dim),
            nn.Tanh()
        )
        self.policy_head = nn.Linear(hidden_dim, action_dim)
        self.value_head = nn.Linear(hidden_dim, 1)
    
    def forward(self, x):
        features = self.network(x)
        logits = self.policy_head(features)
        value = self.value_head(features)
        return logits, value

def ppo_update(model, optimizer, states, actions, old_log_probs, 
               advantages, returns, clip_eps=0.2, n_epochs=4):
    for _ in range(n_epochs):
        logits, values = model(states)
        dist = torch.distributions.Categorical(logits=logits)
        new_log_probs = dist.log_prob(actions)
        entropy = dist.entropy()
        
        # PPO clipped objective
        ratio = (new_log_probs - old_log_probs).exp()
        surr1 = ratio * advantages
        surr2 = torch.clamp(ratio, 1 - clip_eps, 1 + clip_eps) * advantages
        
        actor_loss = -torch.min(surr1, surr2).mean()
        critic_loss = (returns - values.squeeze()).pow(2).mean()
        entropy_loss = -entropy.mean()
        
        total_loss = actor_loss + 0.5 * critic_loss + 0.01 * entropy_loss
        
        optimizer.zero_grad()
        total_loss.backward()
        torch.nn.utils.clip_grad_norm_(model.parameters(), 0.5)
        optimizer.step()

SAC (Soft Actor-Critic)

Suitable for continuous action space (positioning 0%–100% of capital), off-policy, maximum sample efficiency. SAC maximizes: J(π) = E[Σ γ^t (r_t + α H(π(·|s_t)))]. The entropy term H encourages exploration.

class SACActorContinuous(nn.Module):
    def __init__(self, state_dim, action_dim, hidden_dim=256):
        super().__init__()
        self.network = nn.Sequential(
            nn.Linear(state_dim, hidden_dim), nn.ReLU(),
            nn.Linear(hidden_dim, hidden_dim), nn.ReLU()
        )
        self.mean_head = nn.Linear(hidden_dim, action_dim)
        self.log_std_head = nn.Linear(hidden_dim, action_dim)
    
    def forward(self, x):
        features = self.network(x)
        mean = self.mean_head(features)
        log_std = self.log_std_head(features).clamp(-20, 2)
        std = log_std.exp()
        
        dist = torch.distributions.Normal(mean, std)
        action = dist.rsample()  # reparameterization trick
        # Squash to [-1, 1]
        action_tanh = torch.tanh(action)
        log_prob = dist.log_prob(action) - torch.log(1 - action_tanh.pow(2) + 1e-6)
        
        return action_tanh, log_prob.sum(-1, keepdim=True)

Which Algorithm to Choose for Your Strategy?

The choice depends on the action space and sample efficiency requirements. If your strategy uses only discrete signals (buy/sell/hold), DQN with dueling and PER will give stable results. For continuous capital management (e.g., portfolio percentage), SAC is unrivaled: it's 2–3 times more sample-efficient than PPO. PPO is a universal choice when you need reliability and ease of tuning.

We often combine algorithms in a multi-agent architecture: a macro-agent based on DQN determines the overall direction, and a micro-agent based on SAC executes trades. This reduces variance and improves the Sharpe ratio by 15–30%.

Why Is a Correct Reward Function Important?

Reward shaping is a key step that determines the agent's behavior. Typical mistakes: the agent learns to accumulate unrealized profit (without accounting for slippage) or starts trading very rarely to avoid fees. We use a multi-component reward: PnL, drawdown penalty, fees, and spread. For example, reward = ΔP&L - λ1 * fee - λ2 * max_drawdown. The λ coefficients are chosen to simulate realistic conditions.

In one DeFi project, an incorrect reward led the agent to open hundreds of micro-trades, generating a loss from fees. After redesigning the reward (penalty for the number of trades), the agent became profitable.

Algorithm Comparison for Crypto Trading

Algorithm Action Space Sample Efficiency Stability Best Use Case
DQN Discrete Medium Medium Simple buy/sell strategies
PPO Both Low (on-policy) High General-purpose, reliable
SAC Continuous High High Position sizing as action

How to Set Up RL Agent Training: Step-by-Step Plan

  1. Define the action space and state space. For discrete actions (buy/sell/hold), DQN is suitable; for continuous positioning, SAC. The state includes prices, volumes, indicators.
  2. Design the reward function. Account for PnL, fees, slippage, drawdown penalty.
  3. Choose the algorithm and neural network architecture. We use dueling DQN, PPO with clipping, SAC with automatic entropy tuning.
  4. Train with validation. We apply walk-forward validation with 36 rolling windows and early stopping.
  5. Test on out-of-sample data. Evaluate Sharpe ratio, max drawdown, reward stability.

Typical Challenges and How We Solve Them

Market non-stationarity — an agent trained on a calm market may fail in high volatility. As noted in reinforcement learning specification, distribution shift is a serious challenge. We use curriculum learning: gradually increase environment volatility, and in production — continuous fine-tuning with a drift detector.

Reward hacking — artificially inflated rewards. Protection via reward clipping and using a realistic simulator with market data (Level 2, historical candles).

Overfitting — agent memorization. We use walk-forward validation with 36 rolling windows and testing on fully excluded periods (out-of-sample).

Example of Hyperparameter Tuning For PPO, we tune learning rate (3e-4), clip epsilon (0.2), entropy coefficient (0.01) via Bayesian optimization on 50 trials. The best configurations are saved in MLflow. Typical search time is 2 days on GPU.

What's Included in the Work

  • Strategy analysis and data pipeline preparation.
  • Custom environment design (gymnasium) accounting for fees, slippage, and drawdowns.
  • Algorithm and neural network architecture selection.
  • Training with hyperparameter tuning (grid/random search, Bayesian optimization).
  • Walk-forward validation and robustness to market regime changes.
  • Integration with broker API (Binance, Bybit, KuCoin).
  • Documentation, training your team, 3-month support.

Contact us so we can analyze your strategy. We guarantee result quality and support at all stages.

Estimated Timelines and Stages

Stage Duration Result
Analysis and data pipeline 1–2 weeks Prepared data, environment specification
Environment and algorithm design 1–2 weeks Custom environment, baseline model
Training and hyperparameter tuning 2–4 weeks Optimal policy, metrics in MLflow
Walk-forward validation and testing 1–2 weeks Report on Sharpe, drawdown, out-of-sample
Integration and deployment 1–2 weeks Live trading agent, documentation

Order a consultation — we will select the algorithm and architecture for your task. We will evaluate the project for free within 2 business days.

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.
Component Technology Latency / Throughput
Order gateway Go + WebSocket <1ms p99
Matching engine Rust (in-memory) 500k+ orders/sec
Balance store Redis (write-through) <0.5ms
Settlement DB PostgreSQL 14+ ~50k TPS with partitioning
Event streaming Apache Kafka 1M+ events/sec
Blockchain node Geth / Solana validator depends on chain

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

Exchange type Timeframe
DEX (AMM, xy=k) 3 to 5 months
DEX with concentrated liquidity (v3-like) 6 to 10 months
CEX (matching engine + custody + trading UI) 8 to 14 months
Integration with existing protocol 4 to 8 weeks

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.