⚠️ Preview — Launch Rails is built and independently security-tested, not yet live on any network · experimental software · nothing here is an offer, a solicitation, or financial advice
Every safety rule is enforced by the blockchain itself — not promised by a company. That means you don't have to trust us. You can check.
1 · Supply can never grow
All tokens are created exactly once, at launch, and the "create supply" action is built so it can only ever run a single time. There is no minting function anyone can call afterward — not the creator, not the operator, not us.
2 · The code can never change
Your token has no owner, no admin, and no update button — its upgrade path is switched permanently off in the code. It's a stamped copy of one audited recipe, so "is this token safe?" has the same answer for every launch.
3 · The creator starts with nothing free
At launch the creator holds zero tokens. The only way they can hold any is a small, capped, publicly visible opening buy. There is no secret allocation to dump on buyers.
4 · Team tokens are locked on a public schedule
Any team allocation goes straight into a time-lock with a cliff and a steady release. No one can accelerate, delay, revoke, or redirect it, and the full schedule is public before anyone buys.
5 · Liquidity is locked by construction
After graduation, the raised money and matching tokens become a pool with no withdraw function in the code at all. The only way value leaves the pool is an ordinary trade. Nobody can pull the liquidity — there's simply no mechanism to.
"Verify, don't trust" — literally
Everything above is reproducible by anyone. The audited recipe, the reviewer's checking tools, and every approval are public. A community member can take any launched token and confirm, byte for byte, that it's the unmodified recipe. If it ever didn't match, that would be a public, visible incident — which is exactly the point of doing it in the open.
The one honest limit
The blockchain can't read a token's code from inside a transaction, so the final safety check — "is this deployed token really the audited recipe?" — is done by the reviewerbefore approval, and can be repeated by anyone afterward. That's why there's a reviewer, why every approval is public, and why a bad approval's worst case is bounded to that one token's own market. We state this plainly rather than pretend the check is magic.