Live
BLOCKRPC—GASRPC—HYPEMONTRA—KNTQMONTRA—LAUNCHES 24HMONTRA—TOKENS LAUNCHEDMONTRA—CHAIN IDELY99901
Docs

How it works, and where it stops.

Lontra Launch turns a launch plan into a token and its vesting schedules on Elysium, and keeps the result readable afterwards. Here is the whole flow, the exact unlock rule, and what is not built.

How it works

01Plan
In the studio: name, symbol, decimals, a fixed supply, and up to 48 allocations. Each allocation is either sent at launch or held on a schedule: start, cliff, linear duration.
02Draw
The tokenomics builder draws the split and the unlocked share of supply month by month, with the vesting contract's own integer rule.
03Check
The validator runs every rule the kit enforces (amounts add up to the supply exactly, timing limits, refused addresses) and the conventions holders look for, plus two chain look-ups: contract beneficiaries and symbols already used on Elysium.
04Launch
One transaction to LontraLaunchKit, simulated first: it creates LontraKitToken with the fixed supply, sends the at-launch allocations, moves the rest into LontraVestingSafe and records the plan hash. The kit keeps nothing.
05Track
The vesting tracker reads schedules for any wallet or token and lets anyone release what is due (to the beneficiary). The dashboard shows provenance, locked and released supply, holders, pools and a plan-vs-chain comparison.
The unlock rule (LontraVestingSafe)
t <  start + cliff             -> 0
duration == 0                  -> total  (all at start + cliff)
t >= start + duration          -> total
otherwise                      -> floor(total * (t - start) / duration)

Times are block timestamps, never block numbers (on Elysium, block.number is the parent chain's). Rounding is always down and the last unit arrives at start + duration. The site runs the same rule; 165 shared vectors are checked against the contract in its test suite.

What is and is not live

Live now

· Studio, tokenomics builder and validator: work in the browser, no wallet, nothing sent to a server.

· Chain readings in the ticker and hero: block and gas from the Elysium RPC; HYPE, KNTQ and launch counts from Montra's public API.

· LontraLaunchKit and LontraVestingSafe: deployed. Launching, the tracker and the dashboard read them.

Planned

· Listing a launched token on launchpads and DEXes from the dashboard (today: you add liquidity yourself, on the venue of your choice).

· Plan review by a second wallet and shared plan drafts.

· $LONTRA perks (for example plan storage or priority features). Planned, unproven; the core tools stay free.

Limits

· Lontra plans and checks launches; it does not create markets, pools or demand. A launch through the kit makes a plain token and its vesting schedules, nothing more.

· The launch kit and vesting safe were deployed on Elysium on 13 Nov 2026. Anyone can check them against this build with npm run verify-deployment.

· The vesting safe holds tokens for years. It needs an independent security review before real volumes; try it with small amounts first.

· Schedules cannot be cancelled, sped up or paused by anyone, including the creator. A mistake in a plan is permanent once launched: that is what the validator is for.

· Anyone can name any address as a beneficiary. A schedule you did not expect is not proof of anything.

· Validator checks are parameter checks and conventions, never a verdict on a project.

· $LONTRA is not needed for any of it. Its utility is planned and unproven.

FAQ

01What does a launch through Lontra create?

One transaction to LontraLaunchKit creates a plain ERC-20 (LontraKitToken) with a fixed supply and hands every token out at once: allocations marked "at launch" go straight to their address, the rest go into LontraVestingSafe under a cliff + linear schedule. The kit keeps nothing.

02Can the creator mint more, pause transfers or take tokens back?

No. The token has no owner and no mint, burn, pause, blocklist, fee or upgrade function. The vesting safe has no admin: no one can cancel, shorten or redirect a schedule. Only a beneficiary can hand its own schedule to a new address, in two steps.

03How does the unlock work exactly?

Linear from the start over the duration, rounded down; nothing can be released before start + cliff, then everything accrued so far unlocks at once. With a duration of 0, the whole amount unlocks at start + cliff. The same rule runs on the site (tested against the contract with shared vectors).

04Who can release unlocked tokens?

Anyone can call release for a schedule, and the tokens always go to that schedule's beneficiary. A contract that cannot make calls (a vault, a simple multisig) still receives what is due.

05Does Lontra add liquidity or list the token?

No. Pool creation and listings are planned. Today, an allocation labelled liquidity is sent to the address you choose; adding it to a pool is a separate step on the venue you pick.

06Is it safe to launch real tokens with it?

The contracts are tested (unit, fuzz and invariant tests, hostile-token cases) but have not had an independent security review. Lontra recommends a small first launch and a review before real volumes.

07Do I need $LONTRA?

No. Every tool works without it. $LONTRA utility is planned and unproven.

Ready? Open the studio.