🕵️ SicherheitslückenWhat continuous operational resilience looks like under DORA(09.09.2026 um 17:53 Uhr)
🔧 AI Nachrichten OpenAI seeks tougher AI rules. CIOs may feel the ripple effects(10.09.2026 um 12:11 Uhr)
🔧 AI Nachrichten Mistral valued at €21bn after €3bn Series D funding round(08.09.2026 um 10:19 Uhr)
🪟 Windows TippsWindows XP's Cursor Indicator Is Getting a Windows 11 Refresh(25.08.2026 um 13:00 Uhr)
🕵️ SicherheitslückenWhat continuous operational resilience looks like under DORA(09.09.2026 um 17:53 Uhr)
🔧 AI Nachrichten OpenAI seeks tougher AI rules. CIOs may feel the ripple effects(10.09.2026 um 12:11 Uhr)
🔧 AI Nachrichten Mistral valued at €21bn after €3bn Series D funding round(08.09.2026 um 10:19 Uhr)
🪟 Windows TippsWindows XP's Cursor Indicator Is Getting a Windows 11 Refresh(25.08.2026 um 13:00 Uhr)

🔧 Programmierung 🕛 vor 3 Monaten 6 Min Lesezeit
0

We automated the easy half of trading and called it a trader

↗ Quelle (dev.to)
🗣️ Stimme:
📑 Inhaltsübersicht

Here's the part everyone keeps skipping. The AI-agent trading boom is not a scam, and it is not vaporware. There are agents in production right now signing transactions, paying for compute, and moving capital between protocols faster than you can refresh a chart. That part is real. It's funded. It is not going away.



My problem isn't with whether the agents work. It's with where all that capability is pointed.



Because nearly all of it is aimed at one half of the trade. The execution half. Get filled faster, find the better rate, rebalance on schedule, route a payment without a human. And the other half — the half that decides whether your account is still standing after a bad month — is being left almost completely undesigned.






The hype is earned. That's not the issue.



Look at the actual deployments and it's hard to call this a bubble in the usual sense.

















Number What it measures
$15.3B AI-agents sector market cap, Q1 2026 ()
~1,000 Developers contributing to Coinbase's x402 agent-payment protocol ( — three jobs that are tedious, latency-sensitive, and perfect for something that never sleeps and never gets bored. An agent will catch a funding-rate spread at 4 a.m. that you would have missed. It will rebalance to target weights without flinching. Good. Keep it.






But notice what every one of those jobs has in common



Yield optimization. Arbitrage. Rebalancing. Payment routing.



They're all execution. Every one of them assumes the hard decisions have already been made. The agent is told what to hold, how much to risk, and when the thesis is wrong — and then it does the mechanical part beautifully. It's a phenomenal pair of hands. It is not a brain deciding whether your hand should be on the stove at all.



That's the split I keep coming back to. Every trade has two halves.



[suggested chart: the two halves of a trade]



Solved by agents today — the hands:




  • Faster execution and routing

  • Yield optimization

  • Arbitrage execution

  • Portfolio rebalancing and payments



Still undesigned — the judgment that keeps you solvent:




  • How much to deploy (sizing)

  • What invalidates the trade

  • Behavior after a losing streak

  • Hard exposure caps and drawdown response



The agent economy of 2026 has gone almost entirely to the left side of that list. An agent that executes flawlessly on an unsound sizing rule just loses money faster.




An autonomous agent with no risk architecture is not an edge. It's just faster emotion at machine speed.







Automation amplifies your process — including the bad parts



This is the piece I want you to sit with before you hand a wallet to anything autonomous. Automation does not improve your process. It scales whatever process you already have.



A disciplined process, automated, becomes a disciplined process that runs without you getting tired. A weak process, automated, becomes a weak process at scale — executing its mistakes perfectly, around the clock, with no one awake to notice the account bleeding.



If your underlying logic is "go all-in on the signal and hope," an agent will go all-in faster, more often, and at 3 a.m. when you'd have been asleep and safe. The agent doesn't add judgment. It removes the friction that was, accidentally, protecting you. Speed is only an asset on top of a sound decision. On top of an unsound one, speed is the problem.



So the question to ask any agent product isn't "how fast does it execute" or "how clever is the model." It's: what does it do when it's losing?



Does it have a defined point where the position is wrong and it gets out? Does it cap how much of the book sits in one idea? Does it change behavior after a drawdown, or keep pressing because the model said so? If those answers are missing, you've bought a very fast hand attached to no brain.






What designing the second half actually looks like



None of this is an argument against automation. It's an argument for automating the right thing. The survival half isn't exotic — it's four boxes most execution agents simply assume someone else filled in:





  • Signal validation, not signal worship. Require agreement across methods before a setup counts. The point is to reject more, not to trade more. A fast agent firing on a single weak signal is exactly the failure mode above.


  • Capped, staged sizing. Spread entries across planned levels with a hard cap on total exposure, so no single idea can grow big enough to end the account. This is the "how much to deploy" box.


  • A reserve buffer. Set aside part of gains during good periods so the system can keep operating through a drawdown instead of being forced off plan. A buffer, not a guarantee — but it's the difference between riding out a rough stretch and getting knocked out.


  • A large-numbers framework. Treat results as a distribution over many trades, not a verdict on the last one. That's what keeps a system rules-based after a losing streak instead of revenge-trading.



Put those four together and you have something an arbitrage agent doesn't: a defined answer to what happens when it's wrong. Not a better prediction — a designed response to being wrong, automated so it actually gets followed at the moment discipline is hardest.






The boom and the gap are the same story



Here's what happens next, and it's not a contradiction of anything above. Agents keep getting better at execution. Yield, arbitrage, payments, rebalancing — all of it gets faster, cheaper, more autonomous. The capability curve is real and it bends up.



None of that closes the gap, because the gap isn't a capability problem. It's a design-priority problem. The risk half doesn't get solved by a smarter model. It gets solved by someone deciding, before the agent is switched on, what the rules of survival are — the sizing cap, the invalidation point, the drawdown behavior, the buffer — and then encoding those rules so the agent obeys them even when the market is screaming to do otherwise.



That's a choice. Right now most of the industry isn't making it. They're shipping the hands and calling it a trader.



So enjoy the boom. It's real, and parts of it are genuinely good. Just be clear-eyed about which half it solves. The execution half is getting world-class infrastructure. The survival half — the one that decides whether your account is still here next quarter — is still mostly up to you to design. Automate that part first.






Author's note: I work on these problems at KYO Markets, where the focus is the survival half rather than shaving milliseconds off a fill. If you want the longer, fully-sourced version of this argument, it's the full piece on KYO Markets.



Educational, not financial advice. Crypto is volatile and you can lose capital.

Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 0%
🟡 In Evaluierung 0%
🟢 Keine Auswirkung 0%
Spannende Innovation 0%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
1 Quelle
Sam Altman calls GPT-6 Astra rollout ‘messy’ as enterprise users wait for access
1 Quelle
Swiss government explores replacing Microsoft 365 with open-source software
1 Quelle
What continuous operational resilience looks like under DORA
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten We automated the easy half of trading and called it a trader

Thematisch verwandte Begriffe: automated, easy, half, trading · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
📂 News ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

↗ Original-Quelle
Zum Aktualisieren ziehen
ZERO-DAY Kritische Sicherheitsmeldung
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
🤖
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen