A wallet that supports both Lightning and on-chain Bitcoin looks like it offers a faster option and a fallback option — pick whichever's more convenient. For a Bitok Arena entry, it isn't a choice between two equally valid options: Lightning payments settle off-chain through payment channels, which means they never produce the kind of individually attributable, address-visible on-chain transaction a leaderboard tied to the Bitcoin blockchain actually needs. Aqua Wallet supports Lightning specifically because it's fast and cheap for small, frequent payments — exactly the property that makes it unsuitable for anything requiring a direct, on-chain transfer.
Lightning is fast because it doesn't touch the base chain for every payment. Bitok Arena needs exactly the thing Lightning is built to skip.
None of this makes Lightning a lesser feature — for its intended purpose, fast, low-fee payments, it's a genuine improvement over base-chain transactions. It does mean the two payment rails inside a wallet like Aqua serve different purposes, and only one of them fits a competition mechanic built on verifiable on-chain transfers.
Why On-Chain Is the One That Counts
Under the hood, a Lightning payment moves through a network of payment channels rather than being recorded individually on the Bitcoin blockchain — two parties lock funds into a channel on-chain once, then send back and forth without touching the base chain again until the channel eventually closes. A Bitok Arena leaderboard position depends on the opposite: BTC arriving at the master wallet in a transaction that's visible and verifiable on the Bitcoin blockchain itself, a property base-chain transfers have inherently and Lightning payments, by design, don't carry the same way.
What separates an on-chain Bitcoin transaction from a Lightning payment, in terms of what a leaderboard mechanism needs:
Individual visibility — an on-chain transaction is its own permanent, publicly checkable record; Lightning payments settle within channels.
Address attribution — an on-chain send has a clear origin and destination address; Lightning routes through a payment channel network instead.
Finality on the base chain — on-chain transactions confirm directly on the Bitcoin blockchain, which is what a competition tied to that blockchain reads.
None of these three properties are missing from Lightning by accident — they're the tradeoff that makes Lightning fast in the first place.
That's why the correct move inside a wallet like Aqua isn't picking whichever payment rail feels faster — it's specifically selecting the on-chain send function, the one built on the same base-layer transactions a Bitok Arena leaderboard is actually reading. Aqua keeps this distinction visible by separating balances by network rather than blending them into one total, so checking which balance a transaction draws from takes only a few seconds and settles the entire question of whether a send reaches the leaderboard at all.
Sending On-Chain From Aqua Wallet
Using Aqua Wallet for a Bitok Arena entry comes down to selecting the right function. That means the on-chain Bitcoin balance specifically, sent as a standard base-layer transaction to the master wallet address, the same as from any other self-custody wallet.
What to confirm before sending from a multi-network wallet like Aqua:
Correct balance selected — on-chain Bitcoin, not the Lightning balance, is the one that reaches Bitok Arena's master wallet correctly.
Native SegWit address — using a bc1q-format address keeps the on-chain transaction fee as low as the network allows.
Confirmation before counting — allowing the transaction to confirm on-chain before treating the entry as locked in for the round.
Getting those three details right is the entire difference between an entry that counts and a payment that settles somewhere Bitok Arena's leaderboard never sees.
That's worth double-checking specifically because Lightning's convenience makes it the default tab in a lot of wallet interfaces — an easy detail to overlook for anyone reaching for the fastest option without checking which network it settles on. Anyone holding funds only in Aqua's Lightning balance still has a path to a Bitok Arena entry: most multi-network wallets, including Aqua, offer an internal swap that converts a Lightning balance into on-chain Bitcoin through a submarine-swap mechanism, carrying its own small fee and its own confirmation wait rather than settling instantly. It's a legitimate route for someone who only tops up via Lightning, just an extra step rather than a shortcut around the on-chain requirement itself.
What Bitok Arena Actually Reads
Zoom out from the specific wallet interface and the requirement holds across every multi-network setup. Whatever else it supports, only the on-chain balance produces a transaction Bitok Arena's leaderboard can actually verify.
Two balances, two different networks, one leaderboard that only reads one of them. The convenient option and the correct option aren't always the same tab.
Whatever else a wallet like Aqua offers across its supported networks, the specific requirement for a Bitok Arena entry stays simple and unchanged: an on-chain Bitcoin transaction, sent from the on-chain balance, to the master wallet address. That transaction needs to confirm the way any base-layer transfer does — a block arrives roughly every ten minutes on average, and only counts as a leaderboard entry once it's included in one, unlike a Lightning payment, which skips that wait by settling inside a channel instead.
Lightning is the faster balance in Aqua Wallet, but it settles off-chain — exactly what a Bitok Arena leaderboard can't read, no matter how quickly it clears. Pick the wrong tab and a payment can sit confirmed on Lightning while today's leaderboard never sees it. Select the on-chain balance, send BTC from your self-custody wallet to the master wallet, and let it confirm where the leaderboard is actually looking before the round closes without you on it.