⚠️ 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
Both are made from the same independently audited recipe. The second one adds a built-in voting system. That's the only difference.
Type 1
Basic token
A real, standard token. Supply fixed forever, code frozen forever, works in every wallet from the first second.
Choose this if you want the simplest possible token — a community coin, a fun token, a project token where decisions happen in your Discord rather than on the blockchain.
Type 2
Governance token
Everything the Basic token is, plus a built-in community voting system — proposals, balance-weighted votes, results recorded forever.
Choose this if your project makes community decisions and you want them recorded somewhere nobody can fake, delete, or dispute.
The one thing to understand about governance
Votes are a voice, not a lever.
A vote result changes nothing by itself — because the token's rules are frozen (that's what makes it rug-proof), there is nothing for a vote to change. Think of it as a permanent, tamper-proof community poll: the team can promise to follow the results, and everyone can see forever whether they did.
What votes cannot do: mint tokens, move anyone's money, change fees, or alter the token. That limit is a feature — it's the same freeze that makes the token safe.
What about a treasury or team tokens?
Both token types keep this out of the token on purpose, using theLocker (our second product):
Team tokens are locked at launch on a public schedule — a cliff (nothing at first), then a steady drip. Nobody can speed it up, slow it down, or redirect it. Buyers see the exact schedule before they buy.
A community treasury works the same way: lock the funds where everyone can see the amount and the schedule. With a Governance token, the community votes on how itshould be used — so the promise is public, and so is whether it was kept.