Lester Labs DeFi suite live on LitVM LiteForge testnet · chain 4441.
All tutorials
Launchpad

LitVM Launchpad — Immutable Replacement and Legacy Recovery

How the source-pinned immutable testnet Launchpad works and which separately authenticated recovery actions remain for legacy positions.

8 min readTutorial

Current operational status

Both historical ILO factories and their connector remain retired because their treasury route points at the compromised former authority. Do not create, fund, contribute to, change a whitelist on, or finalize a legacy ILO. Historical cancellation, refund, claim, and excess-asset recovery remain visible only when contract state and the connected wallet role permit them. New testnet launches use the immutable source-pinned factory and connector. The controller is frozen at the no-key 0x…01 precompile, the disclosed test treasury has no admin role, and the frontend checks chain 4441, exact runtimes, targets, spenders, value, and launch state before every write.

Using the immutable testnet replacement

1

Have a deployed ERC-20 token

Use an ERC-20 whose exact address, runtime, owner, supply controls, and provenance you have reviewed. The active immutable Token Factory is separate from the retired legacy factory.

2

Navigate to the Launchpad

The Create flow targets only the source-pinned immutable ILO Factory on chain 4441. Legacy ILO views remain distinctly labelled recovery-only.

3

Enter your token address

Paste your token contract address. The UI will fetch the token’s decimals automatically and display the token name and symbol for confirmation.

4

Set your caps

Soft cap: the minimum amount required for the presale to proceed. If this isn’t reached by the end time, contributors can withdraw. Hard cap: the maximum the presale can raise. Once reached, the sale ends immediately.

5

Set the price

Enter the number of tokens a contributor receives per 1 zkLTC. For example, if you want 1 zkLTC = 1,000,000 tokens, enter 1000000. The math handles the decimals automatically.

6

Choose your timeline

The replacement child enforces its configured start/end timestamps and cap. No legacy ILO should be newly configured or funded.

7

Configure LP settings

The replacement child records a liquidity percentage and LP lock duration. More deposited liquidity is not a promise of safety, fair pricing, market depth, or project legitimacy.

8

Deploy and deposit

The app re-authenticates the replacement factory, runtime, chain, fee, spender, and token details before accepting a testnet creation request or showing funding instructions. Never perform this step on a legacy factory or ILO.

Do not create, fund, contribute to, change a whitelist on, or finalize any legacy ILO. Use only the narrowly labelled recovery action that the application exposes for the exact source-authenticated historical contract.

How replacement LP creation works

A replacement ILO hands launch liquidity to the source-pinned `UniSwapConnector`. Before seeding, it verifies factory `feeTo` equals the disclosed test treasury and `feeToSetter` equals the frozen controller. It checks the exact router/factory/wrapper tuple, balances, allowances, minimum outputs, and recipient, then clears temporary allowances. The legacy connector embeds the retired treasury and is never reused.

Continue reading

Token Factory

Token Factory — Immutable Replacement and Legacy Review

4 min read

Locker

Liquidity Locker — Immutable Replacement and Legacy Withdrawal

5 min read