> For the complete documentation index, see [llms.txt](https://midashand-1.gitbook.io/midaspredict/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://midashand-1.gitbook.io/midaspredict/knowledge-base/why-litvm.md).

# Why LitVM?

MidasPredict is built natively on LitVM — the first fully trustless, EVM-compatible Layer-2 rollup for Litecoin. If you've used other L2s like Arbitrum or Base, the experience is similar: fast trades, low gas, and assets secured by a proof-of-work chain.

## Architecture

LitVM employs a hybrid optimistic + zero-knowledge rollup design:

* **Execution:** Arbitrum Nitro stack — battle-tested, EVM-compatible, high throughput
* **ZK validity proofs:** Succinct zkVM — cryptographic proofs for ZK-grade economic finality
* **Sequencing:** Espresso decentralized sequencer — sub-100ms pre-confirmations, no single point of failure
* **Bridging:** BitcoinOS / Charms — trustless, non-custodial bridge for LTC and Litecoin-native assets

## What It Means for You

### Sub-Second Pre-Confirmations

The Espresso sequencer provides sub-100ms pre-confirmations. Daily Markets and high-frequency trading work smoothly.

### Sub-Cent Gas Fees

Small, frequent trades don't get eaten by gas. Micro-bets are viable. Points earnings aren't offset by fees.

### EVM Compatibility

LitVM is fully EVM-compatible. MetaMask, Solidity contracts, and the entire Ethereum tooling ecosystem work out of the box.

### Litecoin Settlement Security

At maturity, LitVM settles to Litecoin L1, inheriting Litecoin's proof-of-work consensus security. MidasPredict's market resolutions ultimately anchor to one of the oldest and most decentralized blockchain networks.

## Comparison

|                        | LitVM                 | Typical Optimistic L2 | Typical ZK L2 |
| ---------------------- | --------------------- | --------------------- | ------------- |
| Pre-confirmation speed | Sub-100ms             | 2–10 seconds          | 1–5 seconds   |
| Gas cost               | Sub-cent              | $0.01–$0.10           | $0.05–$0.50   |
| EVM compatible         | Yes (Nitro)           | Native                | Native        |
| Settlement             | Litecoin (phased)     | Ethereum              | Ethereum      |
| Bridge model           | Trustless (BitcoinOS) | Varies                | Varies        |

*General comparisons. Performance varies by conditions.*

## Tokens on LitVM

| Token        | What It's For                          |
| ------------ | -------------------------------------- |
| zkLTC        | Gas fees + trading collateral on LitVM |
| USDC / USDT  | Trading collateral in markets          |
| Midas Points | Non-transferable trading rewards       |

## FAQ

<details>

<summary>Is LitVM live?</summary>

Builders Testnet is active as of Q1 2026. Mainnet is targeted for Q2–Q3 2026.

</details>

<details>

<summary>What if LitVM goes down?</summary>

MidasPredict would be temporarily unavailable. Contracts are EVM-compatible and theoretically portable to alternative L2s.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://midashand-1.gitbook.io/midaspredict/knowledge-base/why-litvm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.