Urgent.News

What's breaking now, across thousands of outlets.

Tech

How My Stop-Loss Mistake on the Crypto Exchange Cost Me

How did it all start? I felt very smart when I decided to write my own trading agent in the crypto markets. I took a language model and had it interpret market data to make buy, sell or wait decisions. Everything was going very well at first. My Python code was working, pulling stock market data and sending orders based on the decisions made by the model. In the first version, I lost money…

Translated from Spanish Read in Spanish

A cryptocurrency trader wrote a custom trading bot that initially performed well but ultimately failed due to a flaw in its stop-loss mechanism. The bot's code controlled the stop-loss, which became ineffective when the computer running the bot restarted during a market downturn, resulting in significant losses. The trader learned that relying solely on software for critical trading decisions is risky and switched to using the exchange's own order book to set stop-loss orders.

This change ensured that the stop-loss remains active even if the trader's computer or software fails. The trader also added features like trailing stop-loss and improved the system's efficiency and safety.

Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

CSS gap decorations: lines between grid items

This note has an interactive demo. Try it in the original Drawing a line between grid cells has always been a hack: borders on half the items, :nth-child() rules to remove the extra ones, or a…

CVE-2026-118773: CVE-2026-118773: Asynchronous Control Flow Bypass and Uncontrolled Resource Consumption in node-glob

CVE-2026-118773: Asynchronous Control Flow Bypass and Uncontrolled Resource Consumption in node-glob Vulnerability ID: CVE-2026-118773 CVSS Score: 6.3 Published: 2026-10-30 CVE-2026-118773…

  • CVE-2026-118773 affects node-glob versions 9.0.0 to 14.0.1
  • Missing return statements in AbortSignal check logic cause CPU, event loop, and disk I/O exhaustion
  • Upgrading to glob version 14.0.2 resolves the issue

More from Saturday 31 October →