Spotting a spread is easy. Knowing whether it’s worth trading is the work.
I’m building ArbSpread to put prices, depth, funding and spread history in one place.
CEXs + perp DEXs. Free market data. No account needed.
Research, not auto-trading.
https://t.co/vWqPz5lMdH
The checkbox has been overruled.
Binance says its Nov 19 BITOUSDT adjustment will close strategy-bot positions even with “Close all positions on stop” switched off.
@LucyClaudeBuild For a restart between send and response, Hyperliquid lets you query an order by cloid. Saving it before the send would give the locked card a way to reconcile, without assuming the order failed.
@Suikongz The premium formula in section 3 is venue-specific. Hyperliquid uses impact bid/ask prices for a set notional, so a best-bid/best-ask midpoint misses the depth input.
@moo9000@grvt_io Binance is a counterexample: funding applies to positions open at the funding time. It isn’t prorated when you close between settlements.
@sisSoftware Coinbase’s “received” already has an order ID, but it isn’t a queue entry. “open” marks a resting order; “done” can also arrive for one that never rested.
@DeFi_Recker@ethena Are the monthly points and Nov 9 on the same lookback? Aavescan labels its monthly table APY 30d, while its daily rate comes from 24h exchange-rate growth.
@DecentralisedA A dead bot can’t send a final cancel. Kraken Spot’s cancel-all-after timer can: once armed, it cancels all client orders at expiry unless renewed. There’s no per-strategy filter in that call.
@orbitperp_team Does the client get an order acknowledgment before or after the standby confirms it? That would clarify what “zero data loss” covers during failover.
@the_codermaniac Yep—the bids and asks behind the bars. If they’re your engine’s orders, “Local engine depth” would make that clear. The Binance trade price can be live while your engine’s spread is a different number.
That OPEN sign was doing overtime.
MEXC’s Nov 8 maintenance notice promised futures trading would stay available, with possible order errors and delayed book/WebSocket data. The update is now complete.