> 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/use-cases.md).

# Use cases

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.

Each use case below is marked with what an outsider can do today:

* **Do it now on DevNet.** You can do it yourself, with a browser wallet or the public RPC.
* **Rome-run demo on DevNet.** It has run on DevNet, but Rome runs the parties and the venue. You cannot do it yourself there yet.
* **On your own network.** You can do it by running your own Ostia.

Each names the pieces it uses. [Build with Canton](https://docs.rome.builders/canton-zk-evm/build-with-canton.md) has the details of each piece.

**Who you trust today.** Rome runs the prover and the only confirming participant. Rome's participant holds the Canton Coin custody and the twin admin. The code and ZisK (alpha) are unaudited. This is DevNet only. See [Trust model and limits](https://docs.rome.builders/canton-zk-evm/trust-model.md).

**To ask for something you cannot do yet**, such as a twin of your own ERC-20, open an issue in the [repository](https://github.com/rome-protocol/canton-zk-evm/issues) or ask in the Rome [Discord](https://discord.gg/vZ9rnCdNSB). Rome decides case by case, and no date is promised.

## Deploy a Solidity app on a chain that commits on Canton

Do it now on DevNet. Pieces: the public RPC, Foundry or Hardhat, the explorer's contract verification.

Deploy your contracts the way you do on Ethereum, verify the source and read each block beside its Canton record. ERC-20, ERC-721, ERC-1155, an ERC-3643 permissioned token, Uniswap V2 and the contracts that check TACEO Merces proofs have all run on Ostia, and a RedStone price consumer was deployed and verified. You do this on your own. See [Build on Ostia](https://docs.rome.builders/canton-zk-evm/build-on-ostia.md).

## Use Canton Coin in EVM contracts

Rome-run demo on DevNet; you can do it yourself once connecting your Canton wallet is switched on. Pieces: the CC ERC-20, the gateway, the Bridge page.

Deposit Canton Coin on the Bridge page and it arrives on Ostia as CC, an ERC-20 with 10 decimals that any contract can hold and transfer. Withdraw it and the Canton Coin returns to your Canton wallet. See [Bridge](https://docs.rome.builders/canton-zk-evm/bridge.md).

## Put an EVM token on Canton as a twin

Rome-run demo on DevNet with WtROME and TKA; a new token is Rome-run. Pieces: the vault, the ERC-20 twin, the twin registry service.

Pay an ERC-20 into the vault and a Canton party holds its twin, a CIP-0056 token. Redeem the twin and the ERC-20 comes back. TKA and WtROME have twins on DevNet. Rome registers new twins; to ask for one, see the note at the top of this page.

Today only the parties that Rome runs hold twins. No outside Canton wallet holds or sends them yet, because the validators that host a wallet's parties must first hold the twin package. See [Build with Canton](https://docs.rome.builders/canton-zk-evm/build-with-canton.md#erc-20-twins-on-canton).

## Pay for a Canton allocation with an ERC-20

Rome-run demo on DevNet. Pieces: the gateway's `pay`, `DvpTerms`.

An ERC-20 payment through the gateway executes a Canton allocation in the same Canton transaction as the block that holds it. It ran on DevNet in blocks 783 and 1471. Rome runs it with test parties today; to run it between your own parties, run your own network.

## Swap a Canton token for an ERC-20

Rome-run demo on DevNet. Pieces: the `otc-venue` Daml app, the chain's `VenueTrade` and `FundedClaim`, the gateway.

A seller offers a Canton token for a buyer's ERC-20, and a venue runs the trade. The seller's allocation executes in the same Canton transaction as the buyer's payment. It ran on DevNet on 2026-10-27, TKB for TKA, in block 16816, and the explorer shows it at [`/swaps`](https://ostia.devnet.romeprotocol.xyz/swaps). Rome runs the venue on DevNet, and it has run once there. To run your own venue, run your own network.

## Test a Canton app against a chain of your own

On your own network. Pieces: the local Canton network, the demo, the explorer.

[Run your own Ostia](https://docs.rome.builders/canton-zk-evm/run-it-locally.md) starts the stack on your machine, with your own parties. You run deposits, payments, withdrawals and venue trades there without Rome.

## Read and check what settled

Do it now on DevNet. Pieces: the explorer's APIs, the in-browser proof check.

Read blocks, legs, twins and swaps through the explorer's APIs, which need no key (`/api/legs`, `/api/twins`, `/api/swaps`). Check any block's proof in your browser with the Verify button. See [Explorer](https://docs.rome.builders/canton-zk-evm/explorer.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/use-cases.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.
