> 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/rome-shang-de-ying-yong/apps.md).

# 概览

运行在 Rome 上的应用——DeFi、区块浏览器、跨链桥和门户。

Rome 是可运行的软件，而不只是一份规范。这些应用如今已在公有链上运行，每个应用都展示了 EVM 与 Solana 在 Rome 上交汇的一种不同方式。在 Rome 链内，EVM 合约与 Solana 程序共享同一状态，并在一笔交易中完成结算。

除非标记为主网，链接均会在 Hadrian（Rome 的公有测试网）上打开相应应用；Privacy DEX 则直接运行于 Solana Devnet。

## DeFi

| 应用                                                                                      | 简介                                                                                          | 链接                                                    | 源码                                                                                                             |
| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Rome DEX**                                                                            | 一个原生 Solana 流动性池，让使用 Solana 地址和 EVM 地址的用户交易并为同一组储备提供流动性——一个市场，两种身份。                         | [测试网](https://dex.devnet.romeprotocol.xyz/)           | [rome-dex](https://github.com/rome-protocol/rome-dex)                                                          |
| **Aerarium**                                                                            | Compound v3 流动性池，同时支持 Solana 和 EVM 身份——用户可从任一侧在同一市场中存入和借出资产。                                | [测试网](https://aerarium.devnet.romeprotocol.xyz/)      | [aerarium](https://github.com/rome-protocol/aerarium)                                                          |
| **Aave v3**                                                                             | Aave v3 已部署到 Rome，并设有实时储备——采用同样经过充分验证的 Solidity 合约，同时向两侧开放。                                 | [测试网](https://aave.testnet.romeprotocol.xyz/)         | [演示](https://github.com/rome-protocol/rome-aave-v3-demo) · [合约](https://github.com/rome-protocol/rome-aave-v3) |
| **Cardo**                                                                               | 通过 EVM 账户使用 Solana DeFi——包括 Jupiter 永续合约、Meteora 兑换、Marinade 质押等，并支持原子化的多 DApp Compose 工作流。 | [测试网](https://cardo.devnet.romeprotocol.xyz/)         | [cardo](https://github.com/rome-protocol/cardo)                                                                |
| **Appia**                                                                               | 为其他链的用户提供 Solana 上的头寸管理——从 EVM 链进入，在 Solana 上管理，再返回原链。 *正在验证中。*                             | [测试网](https://appia.devnet.romeprotocol.xyz/)         | [appia](https://github.com/rome-protocol/appia)                                                                |
| [**Privacy DEX**](https://docs.rome.builders/zh/rome-shang-de-ying-yong/privacy-dex.md) | 在 Solana 上使用 Helius Privacy 私密余额和 Rome 托管程序进行兑换、管理 USDC 金库及限价订单。                            | [devnet](https://privacy-dex.devnet.romeprotocol.xyz) | —                                                                                                              |

## 基础设施

| 应用                                                                                            | 简介                                                                                                        | 链接                                                                                                                              | 源码                                                                          |
| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| **Rome App**                                                                                  | 日常使用的功能入口——在 Rome 各链之间进行包装、兑换、提供流动性和跨链桥接。                                                                 | [测试网](https://app.devnet.romeprotocol.xyz/)                                                                                     | —                                                                           |
| [**Solgate**](https://docs.rome.builders/zh/rome-shang-de-ying-yong/solgate.md)               | Rome 在 Polygon AggLayer 上的桥接页面。Solgate 可双向连接 Solana 钱包与 Ethereum、X Layer、Katana 及其他 AggLayer EVM 链。       | [主网](https://solgate.romeprotocol.xyz) · [测试网](https://solgate.testnet.romeprotocol.xyz)                                        | —                                                                           |
| [**Rome Bridge**](https://docs.rome.builders/zh/rome-shang-de-ying-yong/bridge-api.md)        | 基于 CCTP v2 和 Solana 原生通道（测试网上使用 Wormhole），连接 Rome、七条 EVM 链与 Solana 的跨链桥；另提供公开 API，供任何应用集成以嵌入桥接功能——无需托管密钥。 | [主网](https://bridge-api.mainnet.romeprotocol.xyz/?chain=7531) · [测试网](https://bridge-api.devnet.romeprotocol.xyz/?chain=200010) | [rome-bridge-api](https://github.com/rome-protocol/rome-bridge-api)         |
| [**Via Explorer**](https://docs.rome.builders/zh/rome-shang-de-ying-yong/via.md)              | 跨虚拟机浏览器——交易会链接到完成结算的 Solana 交易；通过 CPI 预编译合约发起的调用，则会显示其调用的 Solana 程序和指令。                                   | [Hadrian](https://via-hadrian.testnet.romeprotocol.xyz/)                                                                        | —                                                                           |
| [**Oracle Gateway**](https://docs.rome.builders/zh/rome-shang-de-ying-yong/oracle-gateway.md) | 通过兼容 Chainlink 的接口提供 Pyth 和 Switchboard 价格预言机数据，并由 keeper 确保数据及时更新。                                       | [portal](https://oracle.testnet.romeprotocol.xyz/?chain=hadrian)                                                                | [rome-oracle-gateway](https://github.com/rome-protocol/rome-oracle-gateway) |
| [**Bloom**](https://docs.rome.builders/zh/rome-shang-de-ying-yong/bloom.md)                   | 获许可的现实世界资产——只需发行一次 Solidity 资产，之后即可通过 EVM 和 Solana 钱包持有及购买，并由代币本身执行许可名单限制。                                | [测试网](https://bloom.devnet.romeprotocol.xyz/)                                                                                   | —                                                                           |

## 构建一个

基于 Rome 构建？请从 [快速入门](https://docs.rome.builders/zh/kuai-su-ru-men/quickstart.md)开始，然后 [部署 Solidity](https://docs.rome.builders/zh/kai-fa-zhe-zhi-nan/deploy-solidity.md)。如需启动自己的链，请参阅 [应用主权](https://docs.rome.builders/zh/chan-pin/app-sovereignty.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/zh/rome-shang-de-ying-yong/apps.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.
