On-chain Bitcoin competition runs on the Bitcoin mainnet — every position is a confirmed transaction, recorded permanently in the blockchain, independently verifiable by anyone with a block explorer. Lightning Network runs above that mainnet, routing payments through off-chain channels at a fraction of the cost and in a fraction of the time. They are both Bitcoin. They do entirely different things. Bitok Arena's analysis of the two layers explains what each was designed for, why they cannot substitute for each other, and when each is the right choice for a Bitcoin user who understands both.
One layer settles positions permanently on a public ledger. The other moves payments fast and cheap through private channels. Neither can replace the other — and neither needs to. Serious Bitcoin users eventually find a use for both, because they solve genuinely different problems at genuinely different cost and speed levels. The question is never which layer is better in absolute terms. It is which layer is right for the specific action being taken.
Lightning and the Bitcoin mainnet coexist in a Bitcoin user's activity because they serve different purposes. Lightning removes friction from small, frequent payments. The mainnet provides permanent, globally verifiable settlement for transactions where the record matters. On-chain Bitcoin competition requires the second because a leaderboard is only meaningful if every position is independently verifiable — which only mainnet confirmation provides.
What Lightning Was Built to Solve
Bitcoin's mainnet is expensive and slow for small, frequent payments. A transaction that moves a few dollars costs a fee that may exceed the amount being sent during periods of high network congestion, and confirmation takes minutes rather than seconds. Lightning Network addresses this by allowing participants to open a payment channel between two parties, fund it with on-chain BTC, and route payments through that channel at near-zero cost and near-instant speed. Only the channel opening and closing transactions require mainnet confirmation. Every payment within the channel settles off-chain, updating the channel's internal balance state without touching the blockchain.
This makes Lightning suitable for everyday spending: tipping a content creator, paying for a subscription, settling a small invoice between freelancers, buying coffee at a Bitcoin-accepting merchant. The network has grown into a real payment layer with thousands of active nodes globally. For Bitcoin holders who want to spend Bitcoin in daily life without paying mainnet fees on every small transaction, Lightning is the practical solution.
Bitok Arena reviewed the technical properties of Lightning Network and Bitcoin mainnet relative to competition use cases.
Lightning payment speed — sub-second for established channels; near-instant for users with sufficient inbound and outbound liquidity; no waiting for block confirmation.
Lightning payment cost — typically less than 1 satoshi per payment in routing fees; effectively negligible for most payment amounts; designed for microtransaction economics.
Lightning verifiability — channel states are private between the channel counterparties; not visible to the broader Bitcoin network; not independently verifiable from a block explorer; no public record of individual payments within channels.
Mainnet transaction speed — one confirmation in approximately 10 minutes; 3 confirmations (standard finality) in approximately 30 minutes; slower than Lightning by design.
Mainnet verifiability — every transaction is publicly visible on the blockchain; any block explorer shows the transaction, its inputs, outputs, and confirmations; permanently recorded for the lifetime of the Bitcoin network.
What Lightning cannot create is an immutable, publicly verifiable record of a competitive position. A Lightning payment is a private channel state — fast precisely because it skips global network consensus. That same design makes it structurally unsuitable for a leaderboard where every position must be independently verifiable by anyone without trusting the platform. The privacy that makes Lightning fast is the exact property that disqualifies it from providing competition verifiability.
Why Competition Requires Mainnet Settlement
A leaderboard is only meaningful if every position is independently verifiable. If on-chain competition ran on Lightning channels, each position would exist as a private payment state — visible to the channel counterparty, invisible to the broader network. A participant could not verify the ranking by opening a block explorer. The result would require trusting the platform's own records entirely — which is the same trust model as any traditional competition platform and eliminates the architectural advantage of building on Bitcoin.
Mainnet settlement removes that trust requirement. Every BTC committed to a competition round is a transaction confirmed by Bitcoin's full node network and recorded in the blockchain. The leaderboard reads this public data — it does not generate it. Anyone with internet access and a block explorer can independently reconstruct the entire ranking from blockchain data alone, without involving the platform. The platform's display is one representation of the blockchain's record. The blockchain's record is the authoritative source.
The mainnet transaction fee on each competition entry is the cost of the settlement guarantee. Confirmation by Bitcoin's network is what creates the permanence and verifiability of each position. That confirmation has a price — and the price is justified by what it produces: a leaderboard position that exists on the most durable public ledger in operation, verifiable by anyone, independent of any platform's continued existence or data retention policy.
Bitok Arena mapped the use-case fit of Lightning versus Bitcoin mainnet across transaction types.
Lightning: optimized for — micropayments (sub-$10); high-frequency transactions (multiple per day); privacy-preferred payments; cases where mainnet fee exceeds payment value.
Bitcoin mainnet: required for — large-value transfers where finality matters; cold storage movements; on-chain competition entries (leaderboard position must be globally verifiable and permanently recorded); any use case requiring independent verification without trusting the platform.
The choice between layers is not a preference — it is a function of what each transaction needs to produce. Competition entries need mainnet properties. Most daily payments do not.
The use-case mapping removes ambiguity from the layer selection decision. When the transaction must be permanently verifiable, independently confirmable, and recorded on the public Bitcoin ledger, mainnet is not one option among several — it is the only option that produces those properties. Lightning's speed advantage is irrelevant when the transaction outcome must persist on-chain regardless of Lightning channel states.
One Asset, Two Layers, Different Use Cases
Bitcoin holders who understand both layers do not choose between them in a general sense — they choose which layer to use for each specific action. Lightning for small, everyday spending where speed matters and mainnet fees would be disproportionate to the payment amount. Mainnet for actions where permanence and independent verifiability matter: large transfers, cold storage movements, and competition entries where the outcome needs to be permanently recorded and independently confirmed.
A coffee payment through a Lightning-enabled wallet costs fractions of a cent and settles in under a second. A competition entry that could earn a portion of a daily prize pool requires the weight and finality of a mainnet transaction — the on-chain record that exists before the platform reads it and persists after the round ends. The two use cases are not in tension. They are served by different layers of the same network, each designed for the problem it solves.
Bitok Arena's read on the two-layer question: Lightning keeps everyday Bitcoin moving efficiently at near-zero cost. The Bitcoin mainnet keeps competitive positions real and permanently verifiable. On-chain competition requires mainnet settlement not because Lightning is inadequate in general, but because Lightning's privacy and speed are achieved by giving up the property that competition verifiability requires — permanent, public, globally-confirmed blockchain records. Both layers are doing exactly what they were designed to do.
Lightning and on-chain competition coexist in a Bitcoin user's activity precisely because they solve different problems. They share the same underlying asset and the same monetary properties. They operate at different layers, with different confirmation models, at different costs, producing different types of records. The Bitcoin user who understands when to use each layer has a more complete tool set than the one who treats the mainnet and Lightning as substitutes. They are not substitutes. They are complementary tools built on one Bitcoin, each doing what the other cannot.
Bitok Arena's analysis of Lightning versus Bitcoin mainnet identifies the core distinction: Lightning provides fast, cheap, private off-chain payments by skipping mainnet confirmation, while on-chain competition requires mainnet confirmation because competition verifiability demands a permanent, publicly readable blockchain record that any participant can independently confirm. Both run on Bitcoin; each serves the purpose the other cannot.