> For the complete documentation index, see [llms.txt](https://docs.lighter.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lighter.xyz/evm/readme.md).

# Introduction

Lighter EVM is an EVM-equivalent rollup designed for native interoperability with Lighter Core. It enables general-purpose applications to compose directly with Lighter Core markets and liquidity at low latency while preserving the verifiable security guarantees users expect from the Lighter ecosystem.

## Devnet

The current devnet runs the full protocol stack with interop enabled:

* **Lighter EVM** is the EVM-equivalent execution environment where you deploy and interact with smart contracts.
* **Lighter Core** is the order matching engine. EVM contracts can read and write to Core, and Core accounts can send assets to Lighter EVM. See [Lighter Interop](/evm/interop.md).
* **A privately deployed L1** stands in for Ethereum as the settlement and data availability layer. See [L1 and EVM token transfers](/evm/interop/tokens/token-transfers/l1-and-evm.md) for moving assets between L1 and Lighter EVM.

Chain parameters and contract addresses are listed in [Chain Info](/evm/chain-info.md).

{% hint style="info" %}
**Limitations**

* The devnet version uses mocked ZK proofs for L1 finalization.
* The permissionless [escape hatch](/evm/technical-architecture.md#escape-hatch) is not fully functional on the devnet.
* RPC calls that [read Core](/evm/interop/reading-core-from-evm.md) only work at the `latest` block. Support for earlier blocks is planned for an upcoming update.
  {% endhint %}

## Next steps

* [Getting Started](/evm/getting-started.md) walks through sending your first transaction on Lighter EVM.
* [Technical Architecture](/evm/technical-architecture.md) explains how L1, Lighter EVM, and Lighter Core fit together.
* [Differences from L1 EVM](/evm/differences-from-l1-evm.md) lists the behaviors of Lighter EVM that differ from Ethereum.
* [Lighter Interop](/evm/interop.md) covers reading Core from EVM, writing to Core, and moving assets between the two.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lighter.xyz/evm/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.