Chain intel
LiveBlocks, gas, average block time, ETH price, the token leaderboard by holders, and thirty days of throughput — read from the public explorer on every request.
How it works.
HARDCAP launches tokens on Robinhood Chain that cannot be inflated after the first block. This page states exactly what that means, how it is enforced, and — just as importantly — what is not built yet.
The four guarantees
No mint function
The whole supply is created in the constructor and there is no mint entry point afterwards — not for the owner, not for a minter role, not for anyone. Analysers flag capped inflation the same as uncapped, so the only way to clear the flag is for the function not to exist.
Liquidity locked in the contract
The Uniswap V3 position NFT is held by the project contract rather than a deployer wallet, which is what makes a locked-liquidity check pass. Fees stay collectable through the contract owner; the position itself is not on an EOA that can quietly sell it.
Ownership renounced
After the metadata URI is set, ownership is renounced, which freezes the URI permanently. From that block the token has no privileged caller at all.
Sources published
Contracts are verified on the explorer at launch, so the bytecode running on chain can be read as source by anyone. An unverified contract is an unfalsifiable promise.
Why a cap is not enough
A maximum-supply ceiling reads like a solution and is not one. Static analysers score a capped mint the same as an uncapped mint, because a cap is a number in storage and the function that checks it is still a function that creates tokens. A project can also raise a cap it controls. The warning stays either way.
The only construction that removes the warning is the absence of the function. So the whole supply — the market float and any reserve the project keeps for itself — is created in the constructor, and the reserve is then transferred to the project contract rather than minted to it later. The contract pays out of a balance like anybody else, and when that balance is gone it is gone.
A second-order effect is worth naming: a burn function causes the same false positive, because burning calls the same internal transfer hook with a zero address and decompilers read that as minting. There is no burn function either. Sending tokens to a dead address achieves the same thing without the flag.
Live today3 of 6
Launch contracts
LiveThe token and the liquidity-holding contract are written, deployed to Robinhood Chain mainnet, and verified. You can read them before you trust them.
Launch pipeline
LiveA guided command-line pipeline runs the whole launch: deploy, fund, renounce, create the pool, add one-sided liquidity, lock the position, verify sources.
Not built yet3 items
One-click browser launch
Phase 02The same pipeline driven from a connected wallet, with no terminal. Not built yet — the pipeline above is how a launch happens today.
Launch registry
Phase 02A public index of every token launched through HARDCAP with its guarantee checks re-run against live chain state. Not built yet.
Liquidity console
Phase 02Collect fees and manage a locked position from the browser. Today this is done through the pipeline. Not built yet.
These are listed rather than hidden because the difference between a launchpad you can trust and one you cannot is whether its unfinished parts are labelled. Nothing above is described in the present tense anywhere else on this site.
On the numbers
Every chain figure here is read from the public Robinhood Chain explorer at request time and cached for ten seconds. There is no private data source and no backend of ours in the path, which means you can reproduce any number on this site with one curl.
When a read fails, the figure renders as a dash. It is never replaced with a cached value from an earlier request, an estimate, or a zero. A dash means we could not read it — and saying so is the whole point.