---
title: "Sergei B (@pelagiquant) | Hashnode"
description: "Sergei B (@pelagiquant) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@pelagiquant"
---

@pelagiquant

# Sergei B

@pelagiquant · Tbilsi · Joined October 2026

## Comments

[Thanks, Arnold. The issue is shared funds, not overlapping coins. The machine leaves those other positions alone, but with cross-margin they can still draw on the same collateral. The confirmation acknowledges that risk; it doesn't remove it. Are those positions manual trades or another bot?](https://hashnode.com/posts/what-we-check-before-a-trading-machine-starts/6ad9eb7444543f9fde25fda5/comment/6af42ee5ef641118f799066f#reply-6af95684593e8cdc15885f7d)

Reply · Article · 6d ago · [What we check before a trading machine starts](https://hashnode.com/posts/what-we-check-before-a-trading-machine-starts/6ad9eb7444543f9fde25fda5)

[Thanks — the change in trade count deserves a closer look. I wouldn't infer a fee-aware entry filter from that count alone: this comparison doesn't establish where the two trade sequences first diverge. The asymmetry is worth investigating, but I wouldn't assign it to a particular mechanism without tracing those differences. Here we changed a flat fee rate, not a per-fill maker/taker model. That would be a useful next experiment, but whether it narrows the live/backtest gap still needs measuring. Would you start by recalculating costs on a fixed set of fills, or by rerunning the strategy with the new cost model? The first isolates the accounting effect; the second also captures changes in trading behaviour.](https://hashnode.com/posts/the-backtest-used-a-0-06-fee-what-was-my-account-actually-paying/6ae044e80130645d01b33b13/comment/6ae30c202d9192239b37b70d#reply-6ae32d3c446d4ff89ed07862)

Reply · Article · Oct 29 · [The backtest used a 0.06% fee. What was my account actually paying?](https://hashnode.com/posts/the-backtest-used-a-0-06-fee-what-was-my-account-actually-paying/6ae044e80130645d01b33b13)
