> 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/canton-zk-evm.md).

# Canton ZK EVM

- [Overview](https://docs.rome.builders/canton-zk-evm/canton-zk-evm.md): Ostia is a ZK EVM on Canton. It is open on Canton Network DevNet, and every block is proven before it commits.
- [Start here](https://docs.rome.builders/canton-zk-evm/start-here.md): A starting point for each reader of Ostia, with the tools you use and where to look, whether you build apps, validate on Canton, run a prover, audit or run your own Ostia.
- [Ostia DevNet](https://docs.rome.builders/canton-zk-evm/devnet.md): Network details for Ostia DevNet, with the chain id, RPC, explorer, APIs, wallet setup, faucet and limits.
- [Bridge](https://docs.rome.builders/canton-zk-evm/bridge.md): Move tokens between Ostia and Canton from the Bridge page, with a browser wallet on the Ostia side and the Canton wallet you already have on the Canton side. The one-signature Bridge account was retir
- [Build on Ostia](https://docs.rome.builders/canton-zk-evm/build-on-ostia.md): Deploy a Solidity contract on Ostia DevNet with Foundry or Hardhat, verify it, and connect with viem or ethers.
- [Differences from Ethereum](https://docs.rome.builders/canton-zk-evm/evm-differences.md): Where Ostia's EVM differs from Ethereum, for contracts and tools. PREVRANDAO, beacon root, blob transactions, block time, finality, gas limits, Osaka, the standard contracts and nonce rules.
- [Build with Canton](https://docs.rome.builders/canton-zk-evm/build-with-canton.md): What you can target on Ostia beyond plain EVM contracts, the Canton pieces you can build with, and which you can do on your own on DevNet today and which Rome runs.
- [Use cases](https://docs.rome.builders/canton-zk-evm/use-cases.md): What you can do today, on Ostia DevNet or on a network of your own, with the pieces behind each use case and whether you can do it on your own.
- [How it works](https://docs.rome.builders/canton-zk-evm/how-it-works.md): Follow one Ostia block from reth through proving to its Canton commit.
- [What is proven and what is not](https://docs.rome.builders/canton-zk-evm/what-is-proven.md): What Ostia's proofs and Canton commits establish on DevNet today, and what they do not.
- [Explorer](https://docs.rome.builders/canton-zk-evm/explorer.md): A guide to the live Ostia DevNet explorer, its faucet, its APIs and the proof check in the browser.
- [Deposits, withdrawals and payments](https://docs.rome.builders/canton-zk-evm/deposits-withdrawals-payments.md): How the gateway ties EVM deposits, withdrawals and payments to their Canton legs, and how ERC-20 twins and Canton Coin move both ways.
- [Measurements](https://docs.rome.builders/canton-zk-evm/measurements.md): Recorded proof and settlement measurements with their dates, hardware and limits.
- [Trust model and limits](https://docs.rome.builders/canton-zk-evm/trust-model.md): The checks, authorities, custody assumptions and limits of Ostia on Canton Network DevNet.
- [Vetted packages](https://docs.rome.builders/canton-zk-evm/vetted-packages.md): Every Daml package vetted on Rome's two DevNet participants, with its id, version and date, and Rome's promise to announce the vetting it does here first.
- [Status and roadmap](https://docs.rome.builders/canton-zk-evm/status.md): What is live on Ostia DevNet, the dated changelog and what comes next.
- [Run your own Ostia](https://docs.rome.builders/canton-zk-evm/run-it-locally.md): Run the checks, the rehearsal without a GPU, the local demo on a GPU, a chain that survives restarts and Ostia on an existing Canton participant.
- [Ostia prover host](https://docs.rome.builders/canton-zk-evm/prover-host.md): The prover's host requirements, persistent worker and pinned guest build.


---

# 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/canton-zk-evm.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.
