Daily on-chain Bitcoin sends require BTC in a self-custody wallet before each transaction. For participants who accumulate BTC on an exchange through regular purchases — DCA schedules, salary-linked buys, or trading profits — building a system that moves that BTC into a self-custody wallet consistently is more efficient than managing each withdrawal manually. Most major exchanges support recurring or scheduled withdrawals, but the critical caveat is how the exchange handles the sending address: exchanges often send withdrawals from a shared pool address rather than an address assigned to the individual account. When that happens, the address that appears on the blockchain belongs to the exchange. For on-chain competition entries, this means the leaderboard position belongs to the exchange's address — not the participant's — and any prize payment would go to the exchange, not directly to the participant's wallet.
A recurring withdrawal to your own wallet is a recurring transfer to on-chain readiness. The withdrawal from the exchange is step one. The on-chain send from your self-custody address is step two. Conflating the two steps — or trying to skip from exchange directly to on-chain destination — is where the shared-address problem creates leaderboard and prize delivery issues. Two steps, two separate decisions, in sequence.
The two-step workflow — exchange to self-custody, then self-custody to on-chain destination — is the structure that ensures every transaction goes out from an address the participant controls. Bitok Arena Research documented the recurring withdrawal setup and the common misconfigurations that undermine the purpose of the setup.
Setting Up the Recurring Exchange Withdrawal
Major centralized exchanges — Binance, Coinbase, Kraken, and similar platforms — support recurring withdrawals to whitelisted addresses. The whitelisting process adds a self-custody wallet's receive address to an approved list of withdrawal destinations. Once whitelisted, a recurring withdrawal can be scheduled at a defined frequency and amount. The setup process varies by exchange but takes under 10 minutes including the whitelisting confirmation step, which typically requires email or 2FA verification.
Bitok Arena identified the four components of a recurring withdrawal setup for daily on-chain Bitcoin sends and what each one is responsible for.
The self-custody address — a Bitcoin wallet (Electrum, BlueWallet, hardware wallet, or similar) generates the Native SegWit bc1q receive address that anchors the setup; every other component points to this address; the address must be bc1q format for lowest transaction fees on subsequent on-chain sends.
Exchange-side whitelisting — the self-custody address is added to the exchange's approved withdrawal list; this step lives in the exchange's security settings; it requires 2FA or email verification and is independent of any action in the self-custody wallet.
Recurring configuration — amount (planned daily on-chain send plus a fee buffer), frequency (daily), and destination (the whitelisted address) define the automated transfer; the amount should include the Bitcoin network fee for the subsequent on-chain send plus the intended transaction amount.
The timing consideration for daily on-chain sends matters when the send needs to confirm by a specific time. A recurring withdrawal scheduled to execute once daily should be timed so the BTC arrives in the self-custody wallet with sufficient lead time for the Bitcoin network to confirm the subsequent on-chain send. Three Bitcoin network confirmations take approximately 30–60 minutes under normal conditions with a standard fee. A withdrawal scheduled to arrive 2 hours before the intended send time provides a comfortable confirmation window under normal network conditions.
Why the Two-Step Sequence Is Not Optional
Some participants attempt to simplify the setup by scheduling recurring withdrawals directly to an on-chain competition destination address — skipping the self-custody intermediate step. This approach fails for Bitcoin competition specifically because the leaderboard tracks the sending address, not the receiving address. When an exchange sends from its shared pool address, the transaction appears on the blockchain with the exchange's address as the sender. The destination receives the BTC, but the position on the leaderboard belongs to the exchange's address — an address the participant does not control and from which the participant cannot make additional sends to strengthen a leaderboard position.
Bitok Arena documented the specific failures that occur when the exchange-to-competition-direct approach is used instead of the two-step sequence.
Leaderboard address control — the on-chain competition leaderboard tracks the sending address; the exchange's shared pool address appears as the sender rather than the participant's address; the participant cannot view or manage this leaderboard position because they do not control the sending address.
Position augmentation failure — adding to an on-chain competition position during a round requires sending additional BTC from the same address that made the initial entry; a participant cannot instruct the exchange to send a second withdrawal from the same shared pool address that processed the first.
Prize delivery path — on-chain competition prizes are sent to the address that competed; if that address is the exchange's, the prize arrives at the exchange rather than at a self-custody address the participant controls directly.
The manual step in the second position of the sequence is not an inefficiency — it is where the competitive decision happens. On-chain competition entry amounts depend on current leaderboard conditions, which change daily. A fixed automated amount sent directly from the exchange to the competition cannot respond to competitive dynamics. The self-custody wallet receives a consistent supply of BTC through the automated withdrawal; the manual send from the self-custody wallet uses that supply to execute an entry amount calibrated to that day's conditions.
Automation and Manual Decision Together
The recurring withdrawal setup solves the supply problem permanently: BTC arrives in the self-custody wallet on a predictable schedule without requiring manual intervention for each withdrawal. The manual on-chain send from the self-custody wallet solves the competitive decision problem each day: the entry amount, timing, and any mid-round additions depend on leaderboard information that is only available during the live round. Neither step can fully automate what the other requires.
Automation handles the exchange-to-wallet step. The wallet-to-on-chain-destination step stays manual because conditions change daily and the entry decision is the competitive part that no fixed schedule can replace. Set the recurring withdrawal once. After that, the only daily decision is the entry amount — not the mechanics of getting BTC from the exchange to a wallet you control.
Set up the recurring withdrawal to a self-custody bc1q address once. Verify the first execution on a block explorer to confirm the self-custody address is the recipient. From that point forward, the BTC supply side is handled automatically. The daily on-chain send decision — amount and timing — is the manual variable that remains, and it is the one that benefits from being manual because it depends on information that changes each day.
Bitok Arena's setup guidance for recurring BTC withdrawal: exchange recurring withdrawal to a self-custody bc1q address handles the supply side automatically; the on-chain send from self-custody to any on-chain destination remains manual because the amount decision depends on daily conditions. The two-step structure — exchange to self-custody automated, self-custody to destination manual — ensures every on-chain transaction originates from an address the participant controls, with full position management capability and direct prize receipt at the controlling address.