> 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/kai-fa-zhe-zhi-nan.md).

# 开发者指南

- [部署 Solidity 合约](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/deploy-solidity.md): 使用 Hardhat 或 Foundry 在 Solana 上部署 Solidity 智能合约——Rome 网络配置、已注资账户以及分步部署。
- [向 Solana 用户开放你的合约](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/open-to-solana-users.md): 在 Rome（Hadrian 测试网、Rubicon 主网）上部署一个 Solidity 合约，并向 Solana 钱包开放——合约需要什么、Solana 钱包用户如何调用它、各网络地址，以及启动 ch
- [验证合约](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/verify-contracts.md): 通过托管的 Sourcify 服务在 Rome 上验证 Solidity 合约源码——标准的 forge verify-contract 和 hardhat-verify 流程，以及 Via 浏览器上的徽章。
- [WebSocket 订阅](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/websocket-subscriptions.md): 通过 WebSocket 订阅 Rome EVM 事件——使用带有 newHeads 和 logs 的 eth\_subscribe，配合 ethers 可开箱即用；使用 viem 时，请使用轮询。
- [从 EVM 调用 Solana](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/call-solana-from-evm.md): 通过 Rome 的 CPI 和辅助预编译合约从 Solidity 调用 Solana 程序。
- [从 Solana 调用 EVM](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/call-evm-from-solana.md): 让 Solana 钱包直接驱动 Rome 上的 EVM 合约——无需以太坊密钥。钱包签名后，其交易会发送到 Solana。
- [集成一个 Solana 程序](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/integrate-solana-program.md): 将 Solana 程序与 Rome EVM 集成——Solana 签名者是谁、价值如何传入你的程序并返回、单轨规则、原子式与迭代式，以及账户配置。
- [构建双通道应用](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/dual-lane-app.md): 一个双通道应用的逐步讲解——同一个 Solidity 合约同时供 MetaMask 用户和 Solana 钱包用户使用，并精确说明每一步会发生什么。
- [从家中：从另一条链接入 Rome](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/from-home.md): 让另一条链上的用户无需离开原链即可访问你的 Rome 应用——把资产带入、执行操作，再把资产取回。


---

# 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/kai-fa-zhe-zhi-nan.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.