LiteForge (chain ID 4441) is LitVM’s current test environment. It uses an EVM-compatible Arbitrum Orbit execution stack, but LitVM documents important EVM differences and a phased mainnet/settlement roadmap. Testnet behaviour, addresses, contracts, fees, bridges, and availability must not be treated as future-mainnet guarantees. Lester Labs uses a source-pinned immutable replacement for ordinary testnet writes. Its controller and governance power are frozen at the no-key 0x…01 precompile, its disclosed test treasury has no admin role, and every write enforces chain 4441 plus exact target/runtime/intent checks. Legacy contracts remain limited to labelled reads and recovery.
LiteForge uses zkLTC as gas. Obtain test gas only from the faucet linked by LitVM’s official testnet hub. Lester Labs does not sell it, promise its availability, or represent that testnet zkLTC can be redeemed for mainnet assets.
Many EVM-compatible wallets may support LitVM LiteForge at the network level, but compatibility with this website is narrower: during recovery Lester exposes one injected-wallet connector and does not offer WalletConnect, Coinbase SDK, or other remote connectors. Use a disposable testnet-only injected wallet and verify its own LiteForge network settings. Never type a hardware-wallet seed phrase or private key into a software wallet, website, message, or support form. For development workflows, verify the current official LiteForge parameters before configuring `wagmi`, `viem`, Hardhat, or Foundry. Network-level compatibility does not establish that a particular wallet integration has been reviewed by Lester Labs.
Click the network selector at the top of MetaMask, then click "Add network". Scroll to the bottom and click "Add a network manually".
Cross-check the current values at LitVM’s official testnet hub: Network name: LitVM LiteForge New RPC URL: https://liteforge.rpc.caldera.xyz/http Chain ID: 4441 Currency symbol: zkLTC Block explorer URL: https://liteforge.explorer.caldera.xyz Cancel if the wallet prompt differs.
Click Save, then select "LitVM LiteForge" if MetaMask does not switch. Re-open the network details and verify chain ID 4441, the official RPC, and the official explorer before connecting Lester Labs.
Chain ID 4441 is necessary but not sufficient: a wallet can be configured with an untrusted RPC for the same ID. Cross-check the RPC and explorer against LitVM’s official LiteForge parameters, inspect every wallet prompt, and remember that Lester’s source-pinned read endpoint may not be the provider your wallet uses.
Open LitVM’s independently located official testnet hub and follow its current faucet link. Supply only a disposable wallet’s public address. Faucet limits and availability can change, and every on-chain action still consumes testnet gas. Do not buy testnet zkLTC, send LTC to a purported faucet operator, or repeat transactions to manufacture activity. Use only the source-pinned immutable Lester replacement after the app proves chain 4441 and the exact transaction intent.
Read the incident and deployment status shown in the application. Do not bypass a disabled write or reuse a retired contract address.
Use read-only explorer and portfolio views first. A swap or approval is permitted only after the app proves the immutable replacement DEX runtime, chain 4441, exact spender, path, minimum output, recipient, value, and deadline.
If you already have a legacy vesting, lock, ILO, or LP position, use only the narrowly labelled recovery action after checking the exact target and decoded calldata.
Visit lester-labs.com/explorer to search for your wallet address, transaction hash, or any contract. Every interaction you have had is recorded and publicly verifiable on LitVM testnet.
Testnet is an experimental environment and must not be treated as evidence that any mainnet deployment, address, runtime, parameter, fee, or interface will be identical. Lester Labs’ immutable replacement is approved only for valueless chain 4441 and fails closed if its exact runtime or transaction intent cannot be verified. A future real-value release requires distinct reviewed Safe authorities, a separate gas EOA, recovered accounts, and independent release review. Never reuse a testnet assumption or approval with real-value assets.