The trend is your friend. Your exchange’s order book isn’t.
Datapipesoft today released Pending Entries for CryptoOracle, a conditional-entry feature that removes a limitation every exchange order book shares: a pending order can only ever be staged against the direction you want to trade. Entries are available on Bybit, MEXC and Hyperliquid, and are armed directly from the split view.
The order you could never place
The market trades at 100. You want to go long at 110 — a breakout, confirmed by the move itself. Place that as a buy limit and it fills instantly at 100, because it sits above the market. The order book only lets a resting buy wait below the price and a resting sell wait above it.
That constraint is not a quirk of one venue — it is what a limit order is. Which means every pending order a trader can leave on an exchange is a bet against the current move: buy the dip, sell the rally. The trade momentum traders actually want to pre-arm — buy strength, sell weakness — has no resting form. They have to sit and watch for it.
Pending Entries inverts that. The condition is held inside CryptoOracle rather than in the book, so the level can sit on either side of the market. Arm a long above the price and it waits for the breakout. Arm a short below it and it waits for the breakdown. The counter-trend levels a limit order already handles work exactly the same way — one mechanism, both directions, no order-book geometry to work around.
| You want to | Exchange limit order | CryptoOracle pending entry |
|---|---|---|
| Buy below the market | Yes — rests as a bid | Yes |
| Sell above the market | Yes — rests as an ask | Yes |
| Buy above the market (breakout) | No — fills immediately | Yes — waits for the cross |
| Sell below the market (breakdown) | No — fills immediately | Yes — waits for the cross |
Exchanges do offer stop and conditional orders that can trigger with the trend — but they fire on the exchange side, filling into a position CryptoOracle never placed. That arrives as an unmanaged position the bot has to adopt after the fact, without the settings the trader configured for the symbol. A pending entry triggers inside CryptoOracle and opens through the bot’s own order path, exactly like an auto-open, so splits, stop-loss and take-profit apply from the very first pass.
How an entry lives
Armed. The trader picks a side, a trigger price and a size. The direction of the crossing is frozen at that moment: “Buy at 110” means rise through 110 from 100, and fall to 110 from 120. Only the reference price separates the two, and the server resolves it from the same price feed that will later fire the entry — never from the browser.
Waiting. The entry sits with a lifetime of its own, shown as time remaining and marked red under the final hour. While it is armed, auto-open is held off for that symbol: a level the trader staked is never pre-empted by a market open.
Triggered. Every scan pass checks armed entries against a bulk price snapshot. The first pass to reach a crossed entry claims it outright, so overlapping passes cannot open the same position twice.
Opened — once. The order goes out at the size the trader chose, and a notification reports the fill against the level that triggered it. Entries are one-shot in every outcome: placed, rejected or failed. Nothing re-arms itself against a price that has already moved on.
What it refuses to do
- Fill somewhere you did not choose. If the market gaps past the level by more than the entry’s slippage cap — 0.5% by default — the entry is rejected and reported rather than filled at market.
- Guess your size. Size is required when arming and travels with the entry. It never falls back to the symbol’s auto-open amount, which would open a position the trader never sized.
- Act on a blind feed. On a missing or empty price snapshot, nothing fires and nothing is cancelled. Entries stay armed until real prices return.
- Take the scanner down with it. A feed or exchange failure inside the sweep is logged and contained, so the rest of the trading loop keeps running.
- Drift from what is shown. The interface lists entries from the same source the scanner sweeps, so what is displayed and what can actually fire are the same set.
In the interface
Each side of the split view gains a + pending action. The dialog pairs a trigger-price field with a slider running from −100% to +100% around that side’s mark price, so a level can be set by feel or typed exactly. The slider spans both sides of the mark, which is the point: a breakout level and a pullback level are the same gesture. Lifetime is set in hours on a scale weighted toward the short end, where most entries actually sit.
A pending long reads as part of the long book, not as a detached list. The dialog previews the side it expects; the confirmation reports the side the server derived, so the two are visibly reconciled rather than assumed.
Availability
Pending Entries is available now to CryptoOracle subscribers on Bybit, MEXC and Hyperliquid accounts, in both the web platform and the trading API. No configuration is required — the action appears in the split view for every symbol already under management.
“Traders are told the trend is their friend, and then handed an order type that can only be pointed the other way. You can pre-arm buying a dip; you cannot pre-arm buying a breakout. We stopped treating that as a fact of life and moved the condition to our side — where a level is just a level, above or below.”
[SPOKESPERSON NAME, TITLE], Datapipesoft