> 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 网络配置、已注资账户以及分步部署。
- [验证合约](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 事件——使用 eth\_subscribe 的 newHeads 和 logs，可与 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。
- [构建双通道应用](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/dual-lane-app.md): 双通道应用的分步讲解——同一个 Solidity 合约同时供 MetaMask 用户和 Phantom（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 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://docs.rome.builders/zh/kai-fa-zhe-zhi-nan.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.