Saw this on CryptoSlate: there’s an easy-to-miss detail with Kraken futures—if you cancel during the Maker Protection holding window, the API may already return “cancelled” successfully, but the order can still execute as an IOC when the window ends.
On October 8, they expanded this setup to 61 perpetual contracts. Non-post-only limit orders are held for a few dozen milliseconds before entering the matching engine; cancellations during that window are converted to IOC orders, which take whatever liquidity they can, with any remainder not resting on the order book. Spot trading is unaffected, and the 10 most liquid linear perpetuals are excluded.
If your automation treats “cancelled successfully” as meaning the position is closed, your books can easily get out of sync. The official warning also says: don’t place the same order again after a successful cancellation.
#Kraken #Futures
On October 8, they expanded this setup to 61 perpetual contracts. Non-post-only limit orders are held for a few dozen milliseconds before entering the matching engine; cancellations during that window are converted to IOC orders, which take whatever liquidity they can, with any remainder not resting on the order book. Spot trading is unaffected, and the 10 most liquid linear perpetuals are excluded.
If your automation treats “cancelled successfully” as meaning the position is closed, your books can easily get out of sync. The official warning also says: don’t place the same order again after a successful cancellation.
#Kraken #Futures