Overview
Ostia is a ZK EVM on Canton. It is open on Canton Network DevNet, and every block is proven before it commits.
This section is about Ostia, not Rome EVM on Solana. The general pages elsewhere on this site describe Rome EVM on Solana (Hadrian and Rubicon). Where they differ from Ostia, this section is right for Ostia. Three examples: the WebSocket subscriptions guide does not apply, because Ostia's RPC is HTTP only, at
https://ostia.devnet.romeprotocol.xyz/rpc(polleth_getLogs); Ostia's chain id is 770101; and to report a security problem in Ostia, use GitHub's private reporting (see Trust model and limits).
Ostia is a ZK EVM on Canton, with chain id 770101 and the test coin tROME. Canton orders its EVM blocks. A zero-knowledge virtual machine, ZisK, proves each block before it can commit. One Canton transaction carries the block, its proof and the Canton actions it needs. They settle together, or nothing commits.
You can use it today. It has been live on Canton Network DevNet since 2026-10-22: you can deploy Solidity contracts to it with Foundry or Hardhat, read its blocks in a public explorer, check a block's proof in your browser, follow every block's Canton commit on the explorer's External calls page and move tokens between Ostia and Canton with a browser wallet on the Bridge page. Builders can get 100 tROME from the faucet with the builder grant.
New here? Start here points each reader to the right pages and code.
Open source
Ostia is open source under the Apache License 2.0, copyright 2026 Rome Protocol. The code is in one public repository, rome-protocol/canton-zk-evm: the chain, the builder, the gateway contract, the Daml packages, the sidecar, the prover scripts, the explorer, the demo, and the apps for accounts, twins and an OTC venue. The repository's NOTICE file lists the third-party parts, which keep their own licences. The licence grants no right to the Rome, Rome Protocol and Ostia names and the Rome logo. Contributions are welcome under the Developer Certificate of Origin; see CONTRIBUTING.md.
What you can do on your own:
Deploy and verify contracts on DevNet, and use the Bridge page.
Check any block's proof in your browser, and read the open APIs, which need no key.
Check that the vault is the reviewed build by comparing its code hash, and reproduce the guest's program key from source.
Run your own Ostia on a local Canton network, with the prover or its stand-in, and run every piece of Build with Canton there except Canton Coin, which needs a Canton Network validator. For that, run Ostia on your own validator's participant (see Run your own Ostia).
On DevNet, Rome runs the builder, the prover and the confirming participant, so you cannot confirm DevNet's blocks, run its prover or force a transaction in.
What you can build
Ostia runs your EVM contracts and reaches Canton from the same block. You can deploy Solidity apps, use Canton Coin as an ERC-20, put an ERC-20 on Canton as a twin (held today by accounts on Rome's participants), tie an ERC-20 payment to a Canton allocation, and swap a Canton token for an ERC-20 through a venue. Build with Canton names the pieces and says which you can do on your own today, and Use cases lists what works today, on DevNet or on a network of your own.
Live on Canton DevNet
Network
Ostia DevNet
Chain id
770101
RPC
https://ostia.devnet.romeprotocol.xyz/rpc
Explorer
Ostia DevNet has the full network details and the wallet setup. Build on Ostia walks through deploying and verifying a contract.
What runs today
On DevNet, EVM contracts run under Ethereum's rules up to Osaka, with a few differences, listed on Differences from Ethereum. Every block is proven by ZisK and committed as one Canton transaction. The public RPC shows blocks once they are final on Canton. The explorer shows each block beside its Canton record and has an in-browser Verify button. The faucet pays 1 tROME per address a day, and 100 tROME to builders who sign in with GitHub (the builder grant). The explorer verifies contract sources, and its External calls page shows how each block committed on Canton, with its settlement time and attempts.
Canton deposits, withdrawals and payments through the gateway contract have been live on DevNet since 2026-10-25, run by Rome with a Canton test token (TKB, wrapped as wTKB) and test parties. You can watch them on the explorer. They also ran in the 2026-10-05 demo, on a local Canton network. Deposits, withdrawals and payments describes how they work and what ran.
Since 2026-10-29 assets also move both ways. An ERC-20 on Ostia can stand on Canton as a twin through a vault, and Canton Coin comes onto Ostia as the CC token and back. From 2026-11-08 to 2026-11-17 you could do this yourself with a Canton account that the explorer's Bridge page made from one wallet signature. That Bridge account is retired. The Bridge page now connects the Canton wallet you already have, switched on wallet by wallet, and until a wallet is switched on its button reads "Coming soon". See Bridge. The explorer's /twins page shows each twin's supply beside what the vault holds.
Rome's DevNet validator runs Splice 0.10.1 with Canton 3.7.2.
The gateway contract records each block's requests to Canton as legs. A deposit locks a Canton token and mints its wrapped form on the EVM. A withdrawal burns the wrapped form and releases the Canton token. A payment through the gateway executes the Canton allocation that the parties agreed to use for that payment. How it works traces a block through the required checks.
Evidence
Throughput, 2026-10-25. After Daml package 0.2.0, plain transfers ran at 64 a second in steady state on DevNet, with 1,428 in a block, where the 30,000,000 gas cap binds. Before 0.2.0 the mixed load ran at about 10.9 transactions a second, and it has not been measured since. Plain transfers are the cheapest transaction, so this is not a figure for contract-heavy traffic. See Measurements.
One hour of mixed traffic, 2026-10-24. The public RPC accepted 13,496 transactions from a load driver, in blocks 224 to 448 (225 blocks). All of them became final. The mix covered ERC-20, ERC-721, ERC-1155, an ERC-3643 permissioned token, Uniswap V2 swaps and calls to TACEO's Merces contracts, whose Groth16 proofs were made in the client and checked on-chain. The rate was 1.95 to 4.58 transactions a second over ten-minute windows. One client's RPC budget capped it, not the chain, so the run did not find the chain's limit. For blocks of 11 to 100 transactions, the proof took 9.03 s at the median, and a block was final 11.01 s at the median after it was made. Measured from the RPC accepting a transaction to its block being final, the median was 19.5 s and the 95th percentile 27.1 s. Read the run's results for the counts by kind and what did not work.
The settlement demo, 2026-10-05. On a local Canton network with one NVIDIA RTX PRO 6000 Blackwell Server Edition GPU, a setup block and five runs passed their checks: a deposit, a payment, a withdrawal, an allocation taken back after proving, and a tampered proof that Canton refused. The proofs took 6.71 to 6.75 s. Measurements has the table and separates proof times, builder times and the prover benchmark. The demo results explain each check, and the results folder holds the records and proofs.
Status
Ostia DevNet is for building and testing: Rome runs every Ostia service today (Canton Network DevNet's synchronizer is run by the network), and tROME has no value.
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 and Status and roadmap.
Where to go next
Ostia DevNet: chain id, RPC, explorer, faucet, the builder grant, limits, and pauses and maintenance.
Differences from Ethereum: what is not the same as on Ethereum.
Bridge: move and send tokens between Ostia and Canton with a browser wallet.
Build on Ostia: deploy and verify a contract.
Build with Canton: what you can target beyond EVM contracts.
Use cases: what works today, on DevNet or on a network of your own.
How it works: a block from transaction to Canton commit.
What is proven and what is not: what a proof tells you and what it does not.
Explorer: blocks beside their Canton records, and the External calls page.
Run your own Ostia and Ostia prover host: the tests, the GPU demo and your own network.
The repository README has the code and the pinned versions. Try Ostia is the short guide in the repository.
Not to be confused with Rome ZK EVM, whose rollups settle proved roots on Solana.
Last updated
Was this helpful?