> 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/what-is-proven.md).

# What is proven and what is not

What Ostia's proofs and Canton commits establish on DevNet today, and what they do not.

Ostia DevNet is an early release for builders to try. Ostia's proofs establish EVM execution under its pinned rules. Canton confirmation and trust in Rome as the operator are separate.

## Proven and checked

* **Each block ran under Ostia's chain rules.** The proof covers the guest, the compiled program that executes a block and rejects any other chain configuration. Its programVK is pinned. Blocks 0 to 15572 were proven under ZisK 1.3.1 with program key A (`0xdb79251d9e962ee45fbc28cc6431a7fb894106f06d6664e623189f28c24f6d3f`, the key of the 2026-10-05 demo). Blocks 15573 to 71863 (from 2026-10-27) were proven under ZisK 1.3.2-alpha with program key B (`0x424aeb2b...bd69`). From block 71864 (2026-11-16) the chain proves under ZisK 1.4.0-alpha with program key C (`0x36e33545...393f`). See [What the proof fixes](https://docs.rome.builders/canton-zk-evm/trust-model.md#what-the-proof-fixes).
* **The confirmer checks the block before Canton commits it.** Its sidecar verifies the proof, the header and the transaction root. On DevNet the confirmer is Rome's own participant, so this is Rome's check inside Canton's commit, not an independent one. See [How it works](https://docs.rome.builders/canton-zk-evm/how-it-works.md#check-and-settle-in-one-transaction).
* **A block and its legs commit together.** They go into one Canton transaction, so either both are recorded or neither is. The 2026-10-05 local demo showed this, and so did the legs that ran on DevNet on 2026-10-25 (blocks 780, 783, 784, 1465, 1471 and 1473). See [Who checks what](https://docs.rome.builders/canton-zk-evm/trust-model.md#who-checks-what).
* **Anyone can re-verify a block.** The explorer's Verify button checks a block's proof in your browser. Check that the program key the panel shows is the one for that block's range, A, B or C. See [Explorer](https://docs.rome.builders/canton-zk-evm/explorer.md).
* **The chain handled a mixed load.** On 2026-10-24, 13,496 transactions from ERC-20, ERC-721, ERC-1155, ERC-3643, Uniswap V2 and Merces contracts were accepted in one hour, and every one became final. Of 345 transactions sent to fail on purpose, 288 reverted and 57 went through because of a bug in the load driver; 4 others failed because the driver spent tokens a wallet never got (see [Measurements](https://docs.rome.builders/canton-zk-evm/measurements.md#what-did-not-work)). The run did not find the chain's limit. See the [results](https://github.com/rome-protocol/canton-zk-evm/blob/v0.1.0/load/mixed/RESULTS-2026-10-24.md).

## Not proven or not provided

* **Leg settlement can't be re-checked from the block record.** The proof covers the block's execution. Whether Canton settled a leg is a fact about the Canton ledger. See [What this release does not provide](https://docs.rome.builders/canton-zk-evm/trust-model.md#what-this-release-does-not-provide).
* **Rome runs the one participant that hosts every Ostia party.** On DevNet its one sidecar is the only confirmer, and Rome, as its operator, can see every Ostia contract and act for every Ostia party it runs, including the gateway that holds the locked Canton tokens, today test tokens only. It runs the code Ostia's Canton contracts use and the twin admin, which can burn, mint and move the twins any party holds. See [Operator, confirmer and gateway authority](https://docs.rome.builders/canton-zk-evm/trust-model.md#operator-confirmer-and-gateway-authority).
* **One builder, run by Rome, with no forced inclusion.** The RPC and the builder can refuse or leave out a transaction, and you have no way to force one in. See [Trust model and limits](https://docs.rome.builders/canton-zk-evm/trust-model.md).
* **The RPC and the explorer are Rome-run views.** The RPC passes your calls to Rome's reth, and the explorer's indexer checks each Canton record against it. Rome runs both. Apart from re-checking one block at a time with Verify, you cannot check what they report, so you take their answers on trust. Verify re-checks one block's proof, header and transactions, not the state the RPC reports. See [What this release does not provide](https://docs.rome.builders/canton-zk-evm/trust-model.md#what-this-release-does-not-provide).
* **The code and ZisK 1.4.0-alpha are unaudited.** No security audit has covered either. See [SECURITY.md](https://github.com/rome-protocol/canton-zk-evm/blob/v0.1.0/SECURITY.md).
* **There is no privacy.** The Merces transfers in the 2026-10-24 load had their Groth16 proofs made on the sender's machine and verified on-chain. No MPC network runs and nothing is settled. See [the load's notes on private transfers](https://github.com/rome-protocol/canton-zk-evm/blob/v0.1.0/load/mixed/README.md#private-transfers-merces-client-side-only).
* **Canton deposits, withdrawals, payments and twins run on DevNet with test tokens.** They ran from 2026-10-25 with the test token TKB, and from 2026-10-29 with ERC-20 twins and Canton Coin. Deposits, withdrawals and payments also ran in the 2026-10-05 local demo. From 2026-11-08 to 2026-11-17 anyone could open a Canton account on the [Bridge](https://docs.rome.builders/canton-zk-evm/bridge.md) page and make their own moves; that account is retired, and the page connects your own Canton wallet instead, switched on wallet by wallet. See [Deposits, withdrawals and payments](https://docs.rome.builders/canton-zk-evm/deposits-withdrawals-payments.md).
* **tROME has no value, and DevNet may be reset.** Don't keep anything on it that you can't recreate.
* **Canton TestNet and MainNet are not offered.** Ostia runs on DevNet only. See [Status and roadmap](https://docs.rome.builders/canton-zk-evm/status.md).


---

# 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/what-is-proven.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.
