Rome Protocol Puts EVM Chain Ostia on Canton Network DevNet

Rome Protocol has launched Ostia, an Ethereum-compatible blockchain, on the Canton Network developer test network, according to the project's v0.1.0 release notes. The chain runs Ethereum-style smart contracts and settles on Canton, and every block ships with a zero-knowledge proof recorded on Canton in a single transaction.

Ostia is aimed squarely at developers who already live in the Ethereum tooling ecosystem but want access to Canton's infrastructure. Contracts deploy with standard Ethereum tools — the same compilers, wallets and SDKs EVM developers already use — while settlement and finality sit on Canton rather than on an Ethereum L1 or a standalone chain.

How the zero-knowledge proving works

The mechanism is precise. Every Ostia block is proven with ZisK, a zero-knowledge virtual machine, before it is committed. Canton then records both the block and its proof together in one transaction, along with any Canton action tied to that block. That bundling matters: it means the Canton ledger holds a verifiable, compact attestation of each Ostia block's validity, rather than requiring validators on Canton to re-execute EVM state transitions themselves.

In operational terms, Canton becomes the settlement layer and Ostia the execution layer. The zero-knowledge proof replaces trusted bridging assumptions or multi-signature committees with cryptographic verification — the standard trust-minimized pattern now common across zk-rollup designs, here applied to connect an EVM environment with a non-EVM network.

What developers can actually do on Ostia

The v0.1.0 release gives developers two concrete capabilities:

• Deploy contracts with familiar EVM tooling — no Canton-specific development stack required for the smart-contract layer.
• Move Canton Coin ($CC) in and out of Ostia as a regular ERC-20 token, making the native Canton asset usable inside Ethereum-standard contracts, wallets and DeFi interfaces.

Tokens issued on Ostia also flow the other direction: they can appear on Canton as one-to-one twins, extending asset interoperability beyond just $CC.

The lock-and-mint bridge, explained

Rome's repository documentation spells out the bridging mechanism. To bring a Canton token onto Ostia, the original token is locked with a gateway contract, and a wrapped form is minted on the EVM side. Withdrawals reverse the flow: the wrapped token is burnt, and the gateway releases the original Canton token back to its owner.

This lock-and-mint design keeps the Canton-native asset as the sole authoritative version at all times. The Ostia-side wrapped token is a claim on the locked original, not a competing issuance — the same architecture used by wrapped Bitcoin and most cross-chain asset bridges, with the added property here that block validity itself is zk-proven.

Why this launch matters for Canton

Canton Network is positioning itself as infrastructure for institutional finance, and its historical limitation for the broader developer market has been the absence of EVM compatibility. Ostia removes that friction without requiring developers to learn Canton's native programming model. If the devnet rollout graduates to mainnet with the same one-transaction proof-recording design, Canton gains a direct on-ramp for the largest smart-contract developer community in crypto — and EVM projects gain a settlement venue built for regulated, permissioned financial markets.