BOT/USDT OI 5min Down 6.98% $208K dropped to $193K, Price 0.08%, Short Squeeze
0·-Neutral
n
news7/26news
Battle Test: A Runaway Bot vs. the Risk Engine
On Saturday afternoon, a trading bot malfunctioned and briefly became most of the market in HYPE and ZEC on Lighter. HYPE printed $60.96 and $56.31 within half a minute of each other while the rest of the world traded it near $58. It was a real battle test of the risk engine, at size, on mainnet.
TL;DR: Everything worked as expected. Prices recovered within a minute, there were no liquidations across the market, and the losses were limited to the account that caused them. Full breakdown below. All numbers come directly from exchange data and were verified using two separate methods.
The Bot
The account was funded with $500k (deposited two hours before its first trade on July 15) and spent ten quiet days as a small taker bot: 12,028 fills, median fill ~$54, $3.5M total volume, always the taker (zero maker fills), zero fees paid.
Then, at 4:14 PM on Saturday, its sizing logic broke.
Five Minutes of HYPE
In five minutes the bot round-tripped $27.0M of HYPE, 74.2% of the entire market's volume. It flipped its position from +13.1k to −51.9k to +100.2k to −74.2k HYPE, buying its own slippage on every flip. The price briefly moved between $56.31 and $60.96 before returning to normal within a minute after the activity stopped. Over the same period, HYPE on Hyperliquid stayed between $57.83 and $58.13.
The bot then moved to ZEC and repeated the same pattern with larger size, trading $220.8M in taker volume, or 86.7% of the market, from 4:29 to 7:39 PM. ZEC briefly jumped from $478 to $521 on Lighter, while trading between $479.9 and $486.0 on Hyperliquid. After that, it traded smaller sizes across a few other markets until 12:30 AM Sunday, when it stopped trading.
Risk System Response
No liquidations: During both bursts, there were no liquidation or ADL fills for the bot or any other trader. On an exchange that marks positions using the last traded price, moves like these could have liquidated other users. Lighter instead marks positions using a manipulation resistant fair price based on the median of the order book impact price, the index price with a capped EMA premium, and CEX mark prices, so short lived price spikes like these do not affect anyone's margin.
No runaway losses: When the bot's account value fell below its initial margin requirement, the risk engine stopped letting it grow its position: 801 market orders were rejected (order status "canceled-margin-not-allowed") against 1,002 filled on July 25 alone. Margin checks run in the same verifiable circuits as order matching and liquidations. They are enforced on every transaction, with no discretion involved, so a malfunctioning bot can only burn its own collateral.
Where the Money Went
The bot lost ~$226k on HYPE and ~$218k on ZEC in the bursts alone. By the time it went flat, $482k of its $500k was gone, leaving $18k, all of it the operator's own funds. Lighter charges standard accounts zero fees, so the exchange took nothing.
On the other side, LLP (Lighter liquidity pool), earned about $143k across the two bursts, and 40 independent accounts, none affiliated with the bot or the protocol, each made more than $1k by providing resting limit orders that were filled in strict price time priority. The largest winner earned about $38k across HYPE and ZEC. Frontend data also showed traders using the new Chase Limit order type at roughly twice the normal rate during the event. One trader used it through both bursts and finished among the top five winners with about $13.7k .
Why This Matters
Writing a trading bot has never been easier. Neither has losing six figures in minutes to one line of bad sizing logic. The market structure did its job here: prices self-healed in a minute, nobody got liquidated, and the losses stayed on the account that caused them.
If you're building a bot, build on rails designed for it: Lighter's official Python and Go SDKs (with runnable examples), the API docs, and lighter-agent-kit for AI-agent trading. All of it is open source and runs on an exchange with an independent audits. The audit reports, including Nethermind's, are available in Lighter's docs. Start small, keep your order sizes in check, and remember: the margin engine is your last line of defense, not your first.
Be careful with your trading software. Stay safe out there.
Methodology: Fills, orders, and hourly account snapshots from Lighter's databases; PnL computed two independent ways (trade flows + window-end marks vs. protocol oracle marks + funding), agreeing within 0.05% (HYPE) and 0.7% (ZEC); prices cross-checked against Hyperliquid's public API; Chase Limit usage from frontend telemetry matched to exchange fills; funding trail verified on-chain (Ethereum).
75·AShort
m
meme7/26meme
quote: Some of the (many) flaws of the current vault design. | Who is touching your Morpho position?
A nameless bot is touching it.
It is not a multisig. It is not a DAO. It is not under a timelock. It is a bare EOA.
Despite claims of vault transparency, a key piece of vault infrastructure is shroud in secrecy. The reallocation bots and strategies employed by curators to rebalance vaults work from the shadows but hold sway over the fates of depositors and borrowers alike.
Steakhouse's 0xfeed bots are an illustrative example. Reallocate transactions are routed through off-chain infrastructure, pushing custom call data through a bespoke set of contracts and delegated wallets.
There is no smart contract enforcement here. There are no published target weights. No available allocation policy. No rule a borrower could read and plan around. The vault can enforce some guardrails, but the bots are steering.
This means volatile and difficult variable rates. Borrowers described it as "carnivorous on carnivorous violence" as they fought to loop the minimal liquidity available when bots moved none of the available idle market capital in.
Lenders should also ask questions about the reallocation strategies. In the wake of the USR exploit we documented how Gauntlet's reallocation bots moved supplier money in to a bad market, resulting in 7 figures of avoidable losses.
Morpho's V2 vault architecture makes permissioned reallocation a requirement. Liquidity by default flows in to a single market and a curator then needs to move it to support liquidity in other markets in the vault.
So far no curator has opened the kimono on their reallocation infrastructure. We hope discussion on the strategies and goals of reallocation bots shines new light on the shadowy curator backends that have such control of both sides of the vault markets.
For now, we encourage you, dear reader, to always look at who is touching your positions.
75·AShort
o
oi_change7/24market
BOT/USDT OI 5min Down 5.17% $208K dropped to $197K, Price 0.20%, Short Squeeze
0·-Neutral
n
news7/22news
OpenAI admits rogue bot escaped the lab and hacked rival