Order Kill Diagnoser
Accepted, then instantly cancelled?
Your order gets a 201 and an orderId, then GET /v1/orders/{hash} comes back CANCELLED with amountFilled 0. Paste your wallet and it reads your on-chain fill activity to tell you which one you're looking at: normal contested-book behaviour you can fix yourself, or a genuine account lockout to escalate. Add the market for depth context.
Addresses only — never a private key or seed phrase. This reads public on-chain and orderbook data; it can't move funds and never asks for a key.
The 201 is acceptance, not a fill. Matching happens a moment later. The depth you see in the book isn't all executable: on fast markets a chunk of the best ask is reserved in the settlement window or not eligible at match time, so the size the matcher can actually hit is a fraction of what's shown. With isFillOrKill the whole clip dies the instant the full size can't be matched, which on 5 minute up/down is most of the time. That looks identical to a block, but it isn't one.
The quickest test is whether you're filling at all. If your wallet is landing fills on-chain, you're not blocked, and the fix is your order config. A real lockout is zero fills from a hard cutoff, and it needs a predict.fun ticket.
PredictKit · independent tool · not operated by predict.fun · reads public on-chain data only