November 3, 2023

Withdrawal Still Stuck? How to Still Make the On-Chain Competition Round

An exchange withdrawal stuck at pending while an on-chain Bitcoin competition round is still open has one of three causes, and only one of them is recoverable before the round closes. The exchange has not yet broadcast the transaction (exchange-side delay), the transaction is in the Bitcoin mempool but stuck at a low fee rate (network-side delay), or the round has already closed — in which case the question becomes what to do for the next round. If the exchange has broadcast the transaction and it is in the mempool, acceleration options exist. If the exchange has not yet broadcast it, the options reduce to waiting or using a different BTC source if one is available.

Bitok Arena Says

An exchange pending status and a mempool pending status are different problems. Exchange pending means the BTC has not left the exchange's custody — it has not reached the Bitcoin network. Mempool pending means it is on the network, waiting to be mined into a block. Knowing which state you are in determines what, if anything, can be done to accelerate confirmation before the round closes.

Identifying which type of pending applies is the first step. Check the exchange withdrawal history: if a transaction ID (TXID) is listed, the exchange has broadcast the transaction and it is in the mempool. If no TXID appears, the exchange has not yet released the transaction. Exchange-side delays occur when the exchange batches withdrawals, during security holds on new destination addresses, or during high-volume periods when the withdrawal queue is congested. For exchange-side delays, the options are waiting for the exchange to process or initiating from a personal wallet that already holds BTC if one exists — bypassing the exchange queue entirely.

Mempool Acceleration Options

Replace-By-Fee (RBF) is available only for transactions broadcast with the RBF flag enabled. RBF allows the sender to replace an unconfirmed transaction with a new version paying a higher fee rate, incentivizing miners to include it in the next block rather than waiting for the queue to clear naturally. If the original transaction was broadcast with RBF enabled — which is an opt-in feature in wallets like Electrum and Bitcoin Core — and it is still unconfirmed, a replacement transaction with a higher fee rate can be submitted. The replacement supersedes the original in the mempool. Wallets that did not broadcast with the RBF flag cannot use this method. Exchange withdrawal transactions often do not support RBF, as exchanges batch and broadcast without it enabled.

Bitok Arena Research

Bitok Arena mapped the available acceleration methods for stuck Bitcoin mempool transactions, ordered by availability and practicality.

Replace-By-Fee (RBF) — requires the original transaction was broadcast with the RBF flag; creates a replacement transaction at a higher fee rate; only possible before any confirmation; available in Electrum and Bitcoin Core.

Child Pays for Parent (CPFP) — usable from the receiving side if the stuck transaction is sending to a personal wallet first; a new high-fee child transaction incentivizes miners to include the parent.

Transaction accelerators — mining pools including ViaBTC offer paid acceleration that prioritizes specific TXIDs for next-block inclusion.

If the transaction was sent directly to an on-chain competition destination the sender does not control, CPFP is not available. RBF or an accelerator are the remaining options.

Child Pays for Parent (CPFP) to speed up a competition entry is available in a specific routing scenario: if the stuck transaction is sending BTC to a personal wallet first, and the intention is to forward to the competition address, CPFP can be applied at the personal wallet step. Create a new transaction from the stuck incoming unconfirmed UTXO with a high fee rate — this creates the "child" transaction that pays for the "parent" to be confirmed. The total fee of the child must be high enough that the combined fee rate of parent plus child exceeds the miner's inclusion threshold. Electrum, Bitcoin Core, and some other wallets can create CPFP transactions from unconfirmed received UTXOs. This does not work if the BTC was sent directly to the competition destination rather than routing through a personal wallet first.

Fee Rate and Round Timing

How to check the transaction hash to confirm progress starts with finding the TXID in the exchange withdrawal history, then pasting it into Mempool.space. The display shows confirmation count, fee rate, and estimated confirmation time based on current mempool conditions. A transaction at 10 sat/vbyte in a mempool where 20 sat/vbyte is the clearing rate may wait hours. A transaction at 50 sat/vbyte in the same mempool confirms in the next block. If the transaction was submitted at a fee rate too low for current conditions and neither RBF nor CPFP is available, waiting is the only remaining option. The TXID is the only source of information about which of these situations applies.

Bitok Arena Research

Bitok Arena compiled fee rate guidance for on-chain Bitcoin competition entries under time constraints.

Check the current mempool first — Mempool.space shows the fee rate required for next-block confirmation in the Priority column of the mempool chart; set the withdrawal or sending fee to this rate or above when the round timing matters.

Low fee rate consequences — a transaction at 5 sat/vbyte when the clearing rate is 25 sat/vbyte may wait 6 to 12 hours; this misses any round that closes within that window, regardless of how early it was initiated.

Priority fee rate — setting the fee 20–30% above the current clearing rate provides buffer against sudden mempool congestion spikes during the wait; the additional cost on a standard 141-vbyte transaction at 10 sat/vbyte difference is 1,410 satoshis — negligible relative to any meaningful competition entry amount.

When a BTC withdrawal shows no TXID and is stuck in the exchange queue, the fastest recovery option — if one exists — is initiating a send from a different personal wallet that already holds BTC. This bypasses the exchange queue entirely and allows a competition round entry from the personal wallet while the exchange processes the original withdrawal separately. The original withdrawal is not lost — it will eventually arrive at the personal wallet. The round entry is made independently from available BTC, treating the two processes as separate operations.

Prevention: Entry Setup Before the Round

The address format issue — an exchange refusing to send to a Native SegWit bc1q address — appears in some older or region-specific exchange withdrawal interfaces that only accept Legacy (1xxx) or P2SH (3xxx) format. The workaround is to withdraw to a personal wallet that the exchange accepts, then send from that personal wallet to the bc1q competition destination. The competition address will receive BTC sent from any valid Bitcoin address format — the restriction is in some exchanges' send interfaces, not in the Bitcoin protocol or in any on-chain application that reads the sender's address.

Bitok Arena Says

The round that closes without an entry because the withdrawal was stuck teaches the lesson cleanly. On-chain Bitcoin competition entries from a personal self-custody wallet remove the exchange processing variable entirely. The transaction broadcasts from a wallet the competitor controls, at the fee rate they set, at the moment they choose. Entry control starts with BTC in a personal wallet before the round — not with a withdrawal submitted while the round is running.

The prevention for stuck withdrawal situations is holding BTC in a self-custody wallet before the round opens, not initiating withdrawals while the round is active. Withdraw from the exchange in advance — treat exchange withdrawals as preparation, not as part of the round entry process. Keep a competition balance in a personal wallet with a fresh bc1q address. When the round is live and the board shows a competitive gap, send directly from the personal wallet at the fee rate appropriate for the time remaining. The exchange queue does not exist in this path. The transaction is broadcast immediately. The fee rate is set by the sender, not by the exchange's batch processing schedule.

Bitok Arena Bottom Line

Bitok Arena's analysis of stuck withdrawal troubleshooting identifies three states: exchange-side delay (no TXID, BTC not yet broadcast), network-side delay (TXID present, insufficient fee rate), and no recovery possible (round already closed). Acceleration options — RBF, CPFP, transaction accelerators — are available only in the network-side delay case and only under specific conditions. The structural prevention is holding BTC in a self-custody wallet before the round, with the send fee rate set according to current mempool conditions, rather than routing through an exchange during active round time.