> 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/zh/kai-fa-zhe-zhi-nan/from-home.md).

# 从家园出发：从另一条链接入 Rome

你的用户无需迁移到 Rome。从他们的原生链——例如 Arbitrum、Monad 这样的 L2，或 Solana——他们将资产带入，使用你的 Rome 应用，然后再把资产取回。桥接完全在链上，并由用户自己的签名授权；你只需通过一个 API 将应用接入即可。

## 工作原理

* **入站（原生链 → Rome）：** 用户的资产会通过 `settle_inbound_bridge` 程序记入 Rome，且由用户自己签署的 **EIP-712** 意图授权——不存在特权结算方。
* **出站（Rome → 原生链）：** `RomeBridgeWithdraw` （位于 [`rome-solidity`](https://github.com/rome-protocol/rome-solidity)）发起资金流出；资产会在原生链上释放。
* **传输：** Circle **CCTP** 用于 USDC， **Wormhole** 用于 ETH 及其他资产。
* **编排：** 链下的 [`rome-bridge-api`](https://github.com/rome-protocol/rome-bridge-api) 会报价一条路径、验证源链交易，并代付结算费用。它不持有任何资金，也不持有任何密钥——它只能触发用户已经签署的操作。

## 开始构建

1. **获取报价路径** 从 `rome-bridge-api` 为用户的源链 + 资产 → 你的 Rome 链生成报价；它会返回通道（CCTP 或 Wormhole）和步骤。
2. **让用户签署** 源链交易和 EIP-712 意图。
3. **提交** 通过 API；它会验证源链交易并代付结算费用。用户在 Rome 上获得资金后即可使用你的应用。
4. **桥接转出** 通过反向路径 `RomeBridgeWithdraw`.

报价/路径形态、各通道以及按资产划分的细节都在仓库的 [`docs/BRIDGE_API_ARCHITECTURE.md`](https://github.com/rome-protocol/rome-bridge-api/blob/main/docs/BRIDGE_API_ARCHITECTURE.md).

## 阅读代码

* [appia](https://github.com/rome-protocol/appia) —— 一个从原生链使用的应用：用户将 USDC 从他们的原生链带入，并在 Rome 侧使用 DeFi，而无需离开原生链。
* [rome-bridge-api](https://github.com/rome-protocol/rome-bridge-api) —— 编排器（报价 → 验证 → 代付）。

## 下一步

* [获得资金](/zh/zi-yuan/faucets.md) —— 同一条桥接路径为一个全新的开发者钱包提供资金。
* [部署 Solidity](/zh/kai-fa-zhe-zhi-nan/deploy-solidity.md) —— 将你的应用部署到 Rome 上。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/from-home.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.