The claim class: a project states that its own blockchain network's mainnet has launched, moving from a testnet or pre-launch phase to a live, production network.
Claim class: a pattern of statements, not one attributed, dated quote.
Receipt to pull The receipt is the network's own genesis block and the chain of blocks built on top of it since, viewable on a block explorer built for that specific chain, showing an active, advancing block height rather than a chain that stopped producing new blocks shortly after launch. No single receipt is linked: this piece explains how to check this kind of claim and does not grade one specific claim.
A genesis block and some initial activity confirm the network technically started producing blocks; they do not, on their own, confirm the network is decentralized to the degree marketed, that validator or node participation matches claimed figures, or that the network has reached meaningful real-world usage beyond the activity needed to keep blocks being produced at all.
Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker.
A mainnet launch is one of the few milestones in crypto with an unambiguous, permanent, on-chain record: the genesis block, and the first blocks built on top of it, either exist and are being actively produced, or they don’t.
The Claim
The claim class: a project states that its own blockchain network’s mainnet has launched, moving from a testnet or pre-launch phase to a live, production network.
The Receipt
The receipt is the network’s own genesis block and the chain of blocks built on top of it since, viewable on a block explorer built for that specific chain, showing an active, advancing block height rather than a chain that stopped producing new blocks shortly after launch.
For networks built as a chain in their own right rather than deployed as a contract on an existing chain, the explorer needs to be specific to that new network; a generic search on an unrelated, already-established chain’s explorer will not show it. The project’s own documentation should name which explorer actually tracks its specific chain.
What It Doesn’t Prove
A genesis block and some initial activity confirm the network technically started producing blocks; they do not, on their own, confirm the network is decentralized to the degree marketed, that validator or node participation matches claimed figures, or that the network has reached meaningful real-world usage beyond the activity needed to keep blocks being produced at all.
How to Check It Yourself
- Identify the specific block explorer the project itself names as tracking its mainnet, rather than searching an unrelated chain’s explorer.
- Confirm a genesis block exists and check the current block height to see whether new blocks are still being produced, rather than the chain having stalled shortly after an initial launch.
- Check the number of active validators or nodes, where the explorer or network documentation discloses this, against any specific figure the project has claimed.
- Look at transaction activity on the explorer to distinguish genuine usage from the minimal activity needed just to keep the chain technically alive.
- If the project previously ran a testnet, confirm the mainnet is a genuinely separate, independent network rather than a rebranded continuation of the same test environment.
- Check the launch date claimed against the explorer’s own genesis block timestamp, rather than a marketing announcement date that may differ from the technical launch itself.
A Worked Example
A project announces its mainnet has launched, naming a specific date. A reader finds the explorer the project itself points to, confirms a genesis block exists with a timestamp close to the announced date, and sees the block height still climbing steadily weeks later, supporting an active, ongoing network rather than a one-time technical event staged only for the announcement.
What Supported, Contradicted, and No Receipt Look Like
Supported: The project-specified explorer shows a genesine block and an actively advancing block height consistent with ongoing block production, matching the claimed launch date and basic network description.
Contradicted: No genesis block or chain activity can be found for the claimed network through any explorer, or block production has visibly stalled well short of what continuous operation would require.
No receipt: The project claims a mainnet launch but names no explorer or any other way to independently view the chain’s activity, leaving the claim unconfirmed.
Red Flags
- No specific block explorer for the new chain is named anywhere in the project’s own materials.
- Block production has visibly slowed or stopped not long after the announced launch date.
- The claimed validator or node count cannot be checked against anything the explorer or network documentation discloses.
- The “mainnet” shows characteristics, such as a very small and unchanging set of block producers, inconsistent with the decentralization claimed in marketing.
- The launch date in marketing materials does not match the genesis block’s own timestamp once checked.
A Practical Complication to Expect
Some projects describe an early, limited-participant phase, sometimes called a soft launch or a permissioned mainnet, using mainnet language even though participation, validator access, or network access remains restricted to a small group rather than genuinely open. A reader checking block production and genesis timing can still confirm the network is technically running, while a separate check of whether node or validator participation is actually open to the public, as described, addresses a different part of the same overall claim. Treating a restricted, permissioned launch as equivalent to a fully open, decentralized mainnet conflates two different claims that happen to use the same word.
Why It Matters
A mainnet launch is a clean, binary, technically verifiable event, which makes it one of the easier claims in this series to check decisively, provided a reader actually opens the right explorer rather than accepting an announcement date at face value. Readers should also check whether the network’s documentation and its actual explorer agree on basic facts such as the native asset’s name and the consensus mechanism in use, since a mismatch between marketing material and the live, observable chain is itself a sign that the two were not kept in sync as the project moved from its announced plans to what was actually deployed. A reader should also check the explorer’s own reported validator or node count against any specific decentralization figure the project advertises, since a technically live chain with a very small set of block producers is a different claim than the broad, open participation a mainnet launch often implies.
Keep checking: How to Read a Token Unlock Schedule and Check It On-Chain; How to Check a Token for Rug-Pull Mechanics Before You Buy.
FAQ
What is a genesis block?
It is the first block of a blockchain, the starting point from which every subsequent block is built; its existence and timestamp are the clearest possible marker of when a network’s chain actually began.
Can a project fake a mainnet launch?
A project can launch a technically real but thinly used or barely decentralized chain and describe it with language implying much more; the explorer will show real blocks, but activity levels and validator counts are what separate a genuinely functioning network from a minimal one kept alive just enough to support the claim.
Is a stalled chain the same as a chain that never launched?
No; a stalled chain did launch and did produce blocks for some period, which is a different, and separately checkable, fact from whether it is still live today.
Does mainnet launch confirm the network is secure?
No; launching and producing blocks is a baseline operational fact, separate from the security of the code running the network or the economic design securing it, which are their own distinct claims.
What does it mean if a network’s block production becomes noticeably irregular rather than fully stopping?
Irregular, inconsistent block timing can indicate real operational problems, such as an insufficient or unreliable set of validators, even while the network technically remains live by the narrowest definition of still producing blocks at all. A reader evaluating a mainnet-launch claim should look beyond the simple yes-or-no question of whether blocks exist and consider whether block production has been reasonably steady over time, since steadiness is a better indicator of a genuinely functioning network than a bare minimum of activity.
Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker; we describe how a claim like this can be checked, never whether to buy, sell, or hold anything on the back of it.
Sources
This piece links no outside source: it explains a class of claim and the public records you would check, rather than grading one specific statement. When a specific claim is checked, every source link is listed here with its status.
Not financial advice. Human-edited; AI-assisted drafting is disclosed in our editorial guidelines. Spotted an error? See how corrections work.



