LitVM has completed the migration of its LiteForge testnet infrastructure from Caldera to Zeeve, replacing the Rollup-as-a-Service provider while retaining the network’s existing identity and execution stack. The November 11 migration moves LiteForge’s RPC, explorer and indexing infrastructure to Zeeve without changing its Chain ID of 4441 or zkLTC gas token. LitVM Head of BD and Partnerships Rider.Lite confirmed the completed migration as part of the project’s broader V2 infrastructure upgrade.
Existing LiteForge users do not need to add the network again, but they must replace their previous Caldera endpoints. The new RPC is hosted at rpc.testnet.liteforge.zeeve.net, while the block explorer has moved to explorer.testnet.liteforge.zeeve.net. The Zeeve-hosted explorer is already live and identifies the network as LitVM LiteForge Testnet. Independent endpoint checks also found the new RPC returning Chain ID 4441 while the previous Caldera HTTP endpoint returned a 404.
🔥 Another major milestone for LitVM V2.
We’ve officially completed the migration of LiteForge’s testnet infrastructure to @0xZeeve, replacing Caldera as our Rollup-as-a-Service provider.
This is part of a broader technical upgrade as we prepare LitVM for mainnet.
⚙️ A look at… https://t.co/qTzsql12cy pic.twitter.com/SEHIaTZV8D
— Rider.Lite 🔥 (@RiderLDA) November 11, 2026
Zeeve Replaces LitVM’s Operational Infrastructure
The provider change responds to infrastructure constraints LitVM encountered as its testnet activity increased. In its official LitVM V2 announcement, the project cited RPC latency, indexing delays and explorer lag as reasons for replacing Caldera with Zeeve. LitVM expects the new operational layer to provide additional RPC capacity, improved throughput and faster blockchain indexing while leaving Arbitrum Orbit and Nitro as the underlying execution stack.
The migration does not change where LitVM ultimately settles. The architecture uses Ethereum as its settlement layer, with Arbitrum infrastructure providing EVM-compatible execution. This resembles the modular approach appearing elsewhere around the Arbitrum Platform, although individual chains can use different settlement and data-availability configurations, as seen with Elysium’s deployment above HyperEVM. Moving from Caldera to Zeeve changes who operates key rollup infrastructure, not LitVM’s fundamental execution or settlement model.
Several other V2 components remain unfinished. Charms is being developed as the proof-based interoperability layer connecting Litecoin assets with Ethereum and LitVM, while Espresso decentralized sequencing and Succinct zero-knowledge proving remain planned components. The infrastructure migration is therefore complete, but the broader V2 architecture is still being assembled. LitVM’s own roadmap explicitly separates the Zeeve migration from the Charms integration.
Native Litecoin Route Still Awaits V2 Completion
That distinction is particularly important for zkLTC. LiteForge already uses testnet zkLTC as its gas asset, but this does not establish that the intended V2 route for native LTC is operational. The planned architecture would use Charms to represent Litecoin assets through proof-based interoperability, route zkLTC through Ethereum and Arbitrum infrastructure, and ultimately make it usable inside LitVM applications. Testnet zkLTC currently demonstrates application and gas functionality rather than completion of the production Litecoin-to-LitVM asset path.
LitVM is positioning that infrastructure to support DeFi, payments, tokenized assets and other EVM applications around Litecoin. The project has already attracted testnet applications, but activity on LiteForge remains testnet usage and cannot be treated as evidence of mainnet adoption or production capital. The Zeeve transition strengthens the infrastructure available for testing without turning LitVM into a live production network.
The Litecoin Foundation has described mainnet as approaching, but LitVM has not published a confirmed launch date, mainnet Chain ID or production connection details. For now, the measurable milestone is narrower: LiteForge has successfully changed infrastructure providers, while Charms interoperability, decentralized sequencing, proving infrastructure and the eventual mainnet launch remain separate stages of the V2 roadmap.
