> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/zh/he-xin-gai-nian.md).

# 核心概念

- [执行模型](https://docs.rome.builders/zh/he-xin-gai-nian/execution-model.md): Rome EVM 如何在 Solana 上处理以太坊交易——代理仿真、原子模式（VmAt）与迭代模式（VmIt），以及完整的交易生命周期。
- [计算预算](https://docs.rome.builders/zh/he-xin-gai-nian/compute-budget.md): Rome EVM 操作的 Solana 计算单元（CU）成本——原子模式与迭代模式的预算，以及如何设计更节省 CU 的 Solidity 合约。
- [约束](https://docs.rome.builders/zh/he-xin-gai-nian/constraints.md): 在 Rome EVM 上构建时的限制——Solana 交易大小、约 140 万 CU 预算、账户上限、存储布局，以及 Rome 如何逐一规避这些限制。
- [代币互操作](https://docs.rome.builders/zh/he-xin-gai-nian/token-interop.md): ERC-20 和 SPL 代币如何在 Rome 上对应同一个底层账户。
- [Solana 与 EVM 如何在 Rome 上交汇](https://docs.rome.builders/zh/he-xin-gai-nian/how-solana-and-evm-meet.md): Solana 钱包如何调用 Solidity 合约，EVM 地址如何调用 Solana 程序，以及 Rome 如何处理身份、代币、费用和执行限制。
- [选择你的核心](https://docs.rome.builders/zh/he-xin-gai-nian/choose-your-core.md): 双通道应用可以将其核心逻辑保留在 Solidity 侧或原生 Solana 侧。这是一个判断题——请权衡对你的应用最重要的因素。


---

# 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.rome.builders/zh/he-xin-gai-nian.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.