Cryptocurrency exchanges use shared custody addresses — a structural architecture in which one blockchain address receives deposits from many different customers and sends withdrawals on behalf of many different customers. The Bitcoin blockchain records the address, not the customer. Any system that reads the blockchain to identify transaction originators — including on-chain competition leaderboards — sees the exchange's shared address, not the individual customer's account. This creates a specific problem for any on-chain Bitcoin competition participant who sends from an exchange account: the on-chain position that appears on the leaderboard belongs to the exchange's address, not to the individual who funded it.
Two problems with exchange sends. The leaderboard address belongs to the exchange, not the participant. And if multiple customers of the same exchange send during one round, their entries may aggregate under one exchange address — a position no individual controls and that any prize returns to the exchange rather than any participant.
The shared custody address architecture is not a flaw in the exchange — it is a deliberate design that allows exchanges to manage liquidity efficiently across thousands of customer accounts. The flaw is in applying it to a context where on-chain address identity matters for competition position and prize receipt.
How Exchange Shared Addresses Work
When a customer deposits Bitcoin to an exchange, the exchange assigns a deposit address — typically a fresh address generated for that customer for that deposit session. The funds received at that deposit address are swept into the exchange's pooled custody wallets, not held at the deposit address permanently. When a customer initiates a withdrawal, the exchange sends from one of its operational hot wallet addresses — not from the customer's deposit address or any other address the customer specified.
Bitok Arena reviewed exchange custody architecture to establish how shared addresses affect on-chain competition positions.
Outgoing transaction origin — all exchange withdrawals originate from the exchange's operational hot wallet addresses, not from customer-specific addresses. The blockchain records the exchange address as sender regardless of which customer initiated the withdrawal.
Prize destination — if an exchange-originated position ranks, the prize goes to the exchange's address. The individual customer does not receive it directly.
Position control — the participant cannot add to, withdraw from, or receive prizes at an exchange's address. The address belongs to the exchange in every on-chain sense.
The second problem specific to on-chain competition: consecutive sends from the same exchange account may originate from different exchange hot wallet addresses, depending on which address the exchange's treasury management system selected for the outgoing transaction. This creates fragmented entries — multiple exchange addresses each with partial BTC committed — rather than one cumulative position. The on-chain competition leaderboard cannot aggregate these fragments because they come from different blockchain addresses.
The Fix: Self-Custody First
The solution to the shared address problem is a single step: withdraw Bitcoin from the exchange to a personal self-custody wallet before sending to any on-chain competition destination. The personal wallet's bc1 address is the competition position's on-chain identity. All sends from the personal wallet during a round originate from the same address, accumulate in the same leaderboard position, and direct any prize to the same address — which the participant controls.
Bitok Arena confirmed the minimum technical requirement to avoid the shared address problem in on-chain Bitcoin competition.
Requirement — one self-custody Bitcoin wallet generating a bc1 address whose private key the participant controls. Any non-custodial Bitcoin wallet (Electrum, BlueWallet, Sparrow, hardware wallets) satisfies this requirement.
Effect — all Bitcoin transactions sent from the personal wallet during a competition round originate from the same on-chain address, creating a single cumulative position that the participant controls and that prizes are sent to directly.
One-time setup — the wallet is created once and the bc1 address is permanent. Every subsequent competition entry sends from the same address, building a continuous on-chain competition record tied to that address.
After the initial withdrawal from the exchange to the personal wallet, no subsequent exchange interaction is required to participate in on-chain Bitcoin competition. The exchange is in the path for purchasing Bitcoin. It is out of the path for every competition entry after the initial withdrawal confirms.
Exchange shared addresses break competition positions two ways: the position belongs to the exchange, not the participant; and multiple sends from the same exchange may fragment across different exchange addresses rather than accumulating in one position. One withdrawal to a self-custody wallet eliminates both permanently. After that, every entry originates from the participant's own address and any prize goes there directly.
The shared custody address architecture is the correct design for exchanges. It is the wrong architecture for maintaining an on-chain position where address identity determines who controls the position and who receives any prize. Self-custody is the prerequisite for on-chain Bitcoin competition because on-chain competition is a property of the address, not a property of any account balance at any platform.
Bitok Arena's review of exchange custody architecture found that shared hot wallet addresses are used by all major exchanges for outgoing transactions, and that this architecture makes it structurally impossible to build a personal on-chain competition position from an exchange account. The competition position that appears on the leaderboard belongs to the exchange address, prizes go to the exchange address if it wins, and the participant cannot control the position from their account. One withdrawal to a self-custody bc1 address resolves this permanently.