A launchpad on Robinhood Chain · chain 4663
Every token launched here has no mint function, its liquidity held inside a contract rather than a wallet, ownership renounced, and its sources published. Not policy — construction. The functions an analyser looks for are absent because they were never written.
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.
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.
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.
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.
Average block time. Read from the public explorer on this request, not cached from an earlier one.
Deploy the token, create the pool, add one-sided liquidity, move the position into the contract, renounce, verify. The key stays in an encrypted keystore on your machine — the pipeline never reads it, never transmits it, and never takes it as an argument.
Why not simply cap the mint? Because a cap is a number in storage and the function that checks it still creates tokens. Analysers score a capped mint the same as an uncapped one, and a project can raise a ceiling it controls. The only construction that clears the warning is the absence of the function.
So the whole supply, reserve included, is printed in the constructor and the reserve is transferred out. After that block the number can only fall.
Blocks, gas, average block time, ETH price, the token leaderboard by holders, and thirty days of throughput — read from the public explorer on every request.
The token and the liquidity-holding contract are written, deployed to Robinhood Chain mainnet, and verified. You can read them before you trust them.
A guided command-line pipeline runs the whole launch: deploy, fund, renounce, create the pool, add one-sided liquidity, lock the position, verify sources.
The same pipeline driven from a connected wallet, with no terminal. Not built yet — the pipeline above is how a launch happens today.
A public index of every token launched through HARDCAP with its guarantee checks re-run against live chain state. Not built yet.
Collect fees and manage a locked position from the browser. Today this is done through the pipeline. Not built yet.
Phase 02 items are not built. They are listed because a roadmap you can check is worth more than a feature grid implying everything already works.
The token list could not be read from the explorer. No substitute figures are shown.
— addresses and — transactions on Robinhood Chain, both read live, both an em dash if the explorer cannot be reached.