Charms has added Ethereum support to its main development branch, and LitVM says the work is a step toward its planned route for assets. The project's own record describes a Bitcoin-to-Ethereum demonstration. Litecoin integration and the complete route to LitVM remain work in progress.
The distinction matters. A piece of cross-chain infrastructure can work in a documented example while a different asset route, its redemption process and its security assumptions still need to be established.
What Charms has shown
On November 5, Charms said its Ethereum implementation had landed on the repository’s main branch ahead of a planned version 16 release and identified Litecoin as the next step. LitVM highlighted the announcement as relevant to its V2 plans.
The project's demonstration record describes a version 16 run in which a test asset called eBTC was created on Bitcoin and claimed as an ERC-20 representation on Ethereum. The record links to the claim transaction and token contract. Those are useful starting points for inspecting what the project reports doing.
It is a Bitcoin-to-Ethereum example. It does not itself demonstrate that native LTC can already enter LitVM, that holders can redeem an LTC representation, or that a complete Litecoin route is available to the public. We did not execute the demonstration or independently audit the contracts.
As checked on November 7, the Charms releases page listed v15.0.0 as the latest release. Code on a main branch and a published release are different milestones. Check the project’s release page for changes after our review.
Where LitVM fits
LitVM’s October 27 V2 announcement described two separate projects: a new interoperability architecture developed with the creator of Charms, and a migration of its rollup infrastructure to Zeeve. LitVM describes its system as an EVM-compatible Arbitrum Orbit chain using Ethereum for settlement.
Its documentation describes the intended route as Litecoin → Charms / zkLTC → Ethereum → Arbitrum → LitVM. Litecoin secures native LTC, while Ethereum has a separate settlement role for the LitVM chain. The representation and application layers have their own software and dependencies.
LitVM’s network status page, checked November 7, identifies LiteForge as a testnet. It says availability and issuance and redemption conditions for the complete V2 route will be described in release documentation. It also says the Zeeve migration is not yet complete.
What to check next
For LTC holders, the next meaningful milestones are more specific than a claim that a bridge is coming. Look for documentation of the Litecoin integration, the exact supported network and asset, the deployed contracts, and a clear path for both issuance and redemption. Ask which components can be upgraded, what independent security reviews cover, and which version and deployment those reviews examined.
The labels matter too. Testnet zkLTC is for testing. A token on Ethereum or LitVM is a representation on that network, with its own contract and redemption rules. A ticker or a claimed one-to-one relationship is not proof that a particular token is backed or redeemable. Transaction fees, , delays and failures can also differ across the route.
The Litecoin DeFi and bridge-risk guide explains how to assess those dependencies. Until the project publishes the details for a specific deployment, treat descriptions of the complete route as a design rather than a claim of present availability.
Sources checked November 7, 2026. Research and drafting used AI assistance. The cover is a conceptual illustration.
