> 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/interop.md).

# Lighter Interop

The Lighter protocol spans Ethereum L1, Lighter EVM, and Lighter Core. It natively enables interoperability between these three domains so that applications can act across domains and assets can move between supported representations.

The following sections introduce the concepts and interfaces for working across these domains.

* [Accounts](/evm/interop/accounts.md) explains account types and authorization across the three domains.
* [Reading Core from EVM](/evm/interop/reading-core-from-evm.md) describes how EVM contracts access Core state synchronously.
* [Message passing](/evm/interop/message-passing.md) outlines the interfaces for sending messages across domains.
* [Tokens](/evm/interop/tokens.md) provides an overview of how the protocol builds on the messaging infrastructure described above to represent and move value across domains.


---

# 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/interop.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.