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

# Bridge

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

The Bridge page on the Ostia explorer moves tokens between Ostia and Canton. On the Ostia side you need a browser wallet such as MetaMask. On the Canton side you use the Canton wallet you already have: Ostia builds no Canton wallet, and the page makes no Canton key for you.

Open [ostia.devnet.romeprotocol.xyz/bridge](https://ostia.devnet.romeprotocol.xyz/bridge). It runs on Canton DevNet. The tokens are test tokens with no value.

## Where the Bridge stands

| Date       | What changed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 2026-11-17 | The Bridge account and its service were retired on DevNet. The Bridge account was a Canton account that the page made from one wallet signature and kept the key of in the browser. The page no longer offers a sign-in, makes no key from a signature, keeps none in the browser (it deletes what an earlier visit kept) and has no Canton Coin faucet. The accounts it made stay on Canton DevNet, with what they hold, until DevNet is reset: nothing accepts their key any more, so nobody, Rome included, signs or submits for them. |

Connecting a Canton wallet is built into the page and is switched on wallet by wallet. Until it is switched on for a wallet, the button on the page reads **Connect your Canton wallet** with a "Coming soon" tag, and a move that has a Canton step cannot be started from the page. No date is set. What the page does today is everything on the Ostia side: connect your wallet, put it on Ostia, get test tROME, and read the token list and your balances.

## Get test tROME first

Every move on Ostia needs a little tROME for fees, so get test tROME before anything else. While your wallet holds no tROME yet, the Bridge page has a "Get test tROME" button, and a builder can take the 100 tROME grant there (see [Get test coins](#get-test-coins)). Once you hold tROME, take the builder grant on the Faucet page.

## Connect your Canton wallet

Connect your browser wallet first, then press **Connect your Canton wallet** and approve the connection in the Canton wallet you already have. The page offers the wallets its build lists, and the wallet shows each Canton step of a move and signs it. The page signs nothing on Canton, and your browser wallet is never asked for a signature that makes a Canton key.

The first time, the page asks the wallet to opt in once: two steps that you approve in the wallet, one to receive Ostia tokens on Canton, and one to receive withdrawals from Ostia, such as Canton Coin coming back. A lock to a party that has not opted in is refused before anything is paid.

The wallet stays connected after a reload. To end the connection, press **Disconnect** in the sheet.

A Canton wallet works with Ostia only when every validator that hosts its party has vetted Ostia's Daml packages. The wallet tells you if it cannot take a step. See [Vetted packages](https://docs.rome.builders/canton-zk-evm/vetted-packages.md) and [Build with Canton](https://docs.rome.builders/canton-zk-evm/build-with-canton.md#erc-20-twins-on-canton).

## Your addresses

Once you are connected, the account panel shows two addresses side by side:

* **Your wallet on Ostia**, the address of your browser wallet.
* **Your account on Canton**, the party of the Canton wallet you connected. It reads "Not connected" until you connect one.

Each has a Copy button. The panel also shows the Canton balance of each token the page lists, such as Canton Coin, TKA and tROME (the twin of WtROME). Balances show at most 6 decimals, rounded down; Max fills in the exact amount. Sending and accepting tokens on Canton are done in your Canton wallet.

## Get test coins

The page gives you test tROME:

* 1 tROME a day, for everyone, from the explorer's faucet (see [Explorer](https://docs.rome.builders/canton-zk-evm/explorer.md#use-the-trome-faucet)).
* 100 tROME for builders who sign in with GitHub, under "Get test tROME" (shown while your wallet holds no tROME yet; otherwise use the Faucet page). The GitHub account must be 30 days old, and each GitHub account and each address gets one grant every 7 days. See [the builder grant](https://docs.rome.builders/canton-zk-evm/devnet.md#the-builder-grant).

The page has no Canton Coin faucet. Get test Canton Coin in your own Canton wallet.

## The four moves

| Move                  | What happens                                                                                                                    |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Ostia token to Canton | You pay an Ostia token (tROME or TKA) into the vault on Ostia. Your Canton wallet's party then holds the same amount as a twin. |
| Twin back to Ostia    | You redeem the twin in your Canton wallet. The vault pays the ERC-20 back to your Ostia address.                                |
| Canton Coin to Ostia  | You deposit Canton Coin from your Canton wallet. It arrives on Ostia as the CC token.                                           |
| CC back to Canton     | You withdraw CC. Your Canton wallet receives the Canton Coin.                                                                   |

Each Canton step is approved in your Canton wallet. tROME is wrapped first, so its twin stands for WtROME, and it comes back from Canton as WtROME. TKA moves the same way when your address holds some. [Deposits, withdrawals and payments](https://docs.rome.builders/canton-zk-evm/deposits-withdrawals-payments.md) describes the legs behind each move, and [Ostia DevNet](https://docs.rome.builders/canton-zk-evm/devnet.md#canton-assets-on-devnet) lists the token addresses.

Type amounts the way you like: `.5` works as 0.5.

The browser-wallet pop-ups for each move: locking TKA takes 2, locking tROME takes 3 (wrap, approve, pay) and every other move takes 1. The Canton steps are approved in your Canton wallet. A line under the Move button says how many to expect.

## Sent, Proven, Final

Each move shows three marks:

* **Sent**: the page sent the transaction.
* **Proven**: the block that carries it has its proof.
* **Final**: the block is committed on Canton.

Each move links to its Ostia block and its Canton update once they exist. The Activity list shows your moves, including unfinished ones. An unfinished move carries on from its Activity row.

## When a step is unsure

* **A send your wallet did not answer.** The page holds the move at that step. It sends again only after Ostia shows that no transaction of your account made that call.
* **A deposit that can no longer settle.** If a Canton Coin deposit cannot settle, the card offers "Take my tokens back on Canton" about a minute after the deposit's settle-before time. It withdraws the allocation and archives the deposit request, so the tokens stay in your Canton account.
* **An amount that cannot settle.** The page refuses any amount of 10^17 whole units or more of a token before your wallet is asked.

## How long it takes

Measured on the live site on 2026-11-08 with a fresh wallet, when the Bridge account made the Canton steps in the page:

| Move                       | Time                                                  |
| -------------------------- | ----------------------------------------------------- |
| Canton Coin to Ostia       | 56 s                                                  |
| CC back to Canton          | 46 s                                                  |
| 0.5 tROME to Canton        | 2 min 13 s (three wallet pop-ups: wrap, approve, pay) |
| 0.5 tROME back from Canton | 58 s                                                  |

With a Canton wallet you add the time you take to approve each Canton step there. The chain itself was final in about 10 seconds. The rest was the wallet and the page waiting for the proven block.

## What it rests on

This is DevNet. Rome runs the code that Ostia's Canton contracts use and the node that hosts every party Rome runs. The twin's admin, the gateway party, signs every twin holding, so it can burn, mint and move the twins any party holds without that party's signature. The Canton Coin you move onto Ostia is held by the gateway party on Rome's participant, so Rome can move it outside the withdrawal rules. Rome runs every Ostia service.

**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.

[What the twins trust](https://docs.rome.builders/canton-zk-evm/trust-model.md#what-the-twins-trust) and [custody](https://docs.rome.builders/canton-zk-evm/trust-model.md#operator-confirmer-and-gateway-authority) have the details. The retired Bridge account is in [the trust model](https://docs.rome.builders/canton-zk-evm/trust-model.md#the-bridge-account-made-from-a-wallet-signature).


---

# 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/bridge.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.
