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

# Developer Guides

- [Deploy Solidity Contracts](https://docs.rome.builders/developer-guides/deploy-solidity.md): Deploy Solidity smart contracts on Solana with Hardhat or Foundry — Rome network configuration, funded accounts, and step-by-step deployment.
- [Verify Contracts](https://docs.rome.builders/developer-guides/verify-contracts.md): Verify Solidity contract source on Rome via the hosted Sourcify service — standard forge verify-contract and hardhat-verify flows, badges on the Via explorer.
- [WebSocket Subscriptions](https://docs.rome.builders/developer-guides/websocket-subscriptions.md): Subscribe to Rome EVM events over WebSocket — eth\_subscribe with newHeads and logs, working out of the box with ethers and viem providers.
- [Call Solana from EVM](https://docs.rome.builders/developer-guides/call-solana-from-evm.md): Call Solana programs from Solidity via Rome's CPI and helper precompiles.
- [Call EVM from Solana](https://docs.rome.builders/developer-guides/call-evm-from-solana.md): Let a Solana wallet drive EVM contracts on Rome — no Ethereum key. The wallet signs, and its transaction goes to Solana.
- [Build a dual-lane app](https://docs.rome.builders/developer-guides/dual-lane-app.md): A step-by-step walkthrough of a dual-lane app — one Solidity contract used by both a MetaMask user and a Phantom (Solana) user, with exactly what happens at each step.
- [From home: reach Rome from another chain](https://docs.rome.builders/developer-guides/from-home.md): Let users on another chain reach your Rome app without leaving home — bring assets in, act, take them back out.


---

# 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/developer-guides.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.