LitVM moves LiteForge to Zeeve and changes its testnet URLs
LiteForge has new RPC, explorer and faucet URLs after its move to Zeeve. We checked chain ID 4441 against the live RPC and matched a block hash in the explorer.
Dotted-underlined terms open a quick definition. Close it to keep reading.
LitVM said on November 11 that it had moved its LiteForge testnet infrastructure from Caldera to Zeeve. If you already use LiteForge, edit the RPC and explorer URLs in your existing entry. On November 12 at 22:58 UTC, the new RPC returned chain ID 4441 and the same hash as the new explorer at the height we sampled. The old Caldera HTTP RPC returned a 404 to our request. LitVM’s announcement and current network configuration.
Settings to update
LiteForge testnet configuration as checked on November 12, 2026
After you save the new RPC, make sure your wallet selected it as the active endpoint. If you maintain an app, check its RPC environment variable, links to transaction receipts and any job that calls the old explorer API. The documentation says the Caldera WebSocket is inactive and lists HTTP as the connection method while a replacement is pending. If your app depends on subscriptions, review that code before switching. An HTTP URL serves requests such as block reads, while subscription code needs a supported transport or a polling fallback. LitVM network configuration.
What we checked
The new HTTP RPC returned 0x1159 for eth_chainId, which is 4441 in decimal. Its latest block was 70,405,773. We queried block 70,405,741, 32 blocks below that head, to give the explorer time to index it. The two services returned the same hash, beginning 0x3fa62e98 and ending b924b6710. The explorer also agreed on the block timestamp. Explorer record for the sampled block.
For a quick check after updating your app, query the chain ID, pick a recent and compare its hash in the RPC and explorer. Using the same height avoids confusion if the explorer is a few blocks behind. Both addresses in this check are Zeeve services, so the result establishes agreement between their responses at one height. Testing your own app’s contract calls and historical queries is a separate step.
What comes next
The operational move and the Charms integration were separate pieces of LitVM’s V2 plan. LiteForge uses testnet zkLTC for gas. LitVM says it will publish mainnet connection details through its official channels and describe the complete native LTC route, including issuance and redemption terms, in the relevant release documentation. LitVM V2 announcement, network status and our earlier report on Charms.
Sources and public endpoints checked November 12, 2026, UTC. The RPC and explorer queries were read-only. Research and drafting used AI assistance. The cover is a conceptual illustration.
Wallet
In brief Software or a device for managing wallet keys and payments, though a watch-only setup cannot sign on its own.
Software or a device that manages keys and helps you receive and send Litecoin. Coins are recorded on the blockchain. A watch-only wallet can show addresses and transactions without holding the keys needed to spend.
For example One wallet can generate several receiving addresses and still show them as a single combined balance.
Common mistake Thinking coins live inside the app, or that seeing a balance proves that the wallet can sign a spend.
In brief A group of transactions linked to the previous block under the network's rules.
A batch of transactions accepted under the network rules and linked to the previous block. Litecoin targets one new block every 2.5 minutes on average; a particular block may arrive sooner or much later.
For example Your payment may wait unconfirmed and then receive its first confirmation when a miner includes it in an accepted block.
Common mistake Treating the 2.5-minute target as a countdown or a maximum wait for your payment.
In brief A block's position counted from zero in a chain, which does not uniquely identify the block or tell its time.
A block's position along a chain, starting with the genesis block at height zero. Height is an index, not a unique block identifier or a timestamp: competing blocks can occupy the same height on different branches. Use the block hash when identifying a particular block.
For example If a transaction remains in active-chain block 100 and the active tip is 102, it has three confirmations: blocks 100, 101 and 102.
Common mistake Treating height 100 as 100 confirmations, or assuming two nodes at the same height necessarily have the same chain tip.
Content review recorded: 2026-11-12. The review record does not identify a separate independent reviewer. An edited date above records an edit, not a new fact-check. AI-assisted editing or new artwork alone does not complete a source review.
Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.
