> 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/bloom/evidence-investor.md).

# 证据——投资者

该 [投资](/zh/rome-shang-de-ying-yong/bloom/investing.md) 截图中是真实买家，而且是两次—— **一次来自 EVM 钱包，一次来自 Solana 钱包，购买同一 Solidity 资产** （Mineral Vault I， `ARCV`）在 Hadrian（链 `200010`）上。每个动作都是你可以打开的一笔交易。链接即申领。

* **资产：** [`0x2b13ba16a429bf630f94882e477fe775d34b7c74`](https://via-hadrian.testnet.romeprotocol.xyz/address/0x2b13ba16a429bf630f94882e477fe775d34b7c74)
* **商店：** [`0x9326a00dd1cd4f3f1800fc849c3c58715fc5061a`](https://via-hadrian.testnet.romeprotocol.xyz/address/0x9326a00dd1cd4f3f1800fc849c3c58715fc5061a)
* **支付货币：** wUSDC [`0xd4cc34b67c805d472b5a709a22a1037f6b16ef28`](https://via-hadrian.testnet.romeprotocol.xyz/address/0xd4cc34b67c805d472b5a709a22a1037f6b16ef28)

## EVM 通道——钱包在自己的地址买入

一个 EVM 钱包在自己的地址持有该资产，买入就是常规的两步流程：先授权，再购买。资格门槛会先在代币层面检查——买家先被加入允许名单，然后再购买。

买家： [`0x5667b3700b4a021Cc475157cbf3dE2d756Fae597`](https://via-hadrian.testnet.romeprotocol.xyz/address/0x5667b3700b4a021Cc475157cbf3dE2d756Fae597)

| # | 其执行内容                        | 交易                                                                                                                                          |
| - | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | 将买家加入允许名单（在测试接线中作为发行方批准的替代项） | [`0xf8180aef…5c29c86d`](https://via-hadrian.testnet.romeprotocol.xyz/tx/0xf8180aef8ba3203750a4ae63eea215c9e5891cd147f7272a359f512c5c29c86d) |
| 2 | 向商店授权 wUSDC                  | [`0x0f7229ea…7c2669e5`](https://via-hadrian.testnet.romeprotocol.xyz/tx/0x0f7229eab17d8d28907a3bc9239f62367abed528fde09bd7cc0ad10f7c2669e5) |
| 3 | 购买资产                         | [`0xe099d892…3792f6de`](https://via-hadrian.testnet.romeprotocol.xyz/tx/0xe099d8921225563cf0fbf0e4fd1e97037f50bcbebf41f2acea21696f3792f6de) |

购买后，资格卡显示 **已获许可** ，且持仓会显示在 Positions 中—— `可投资许可` 和 `持仓` 指南中的截图就是这位买家在这些交易之后的状态。

## Solana 通道——钱包在其派生地址买入

这一条承载了整个论点： **一个 Solana 钱包购买相同的 Solidity 资产，没有桥接，也没有第二个代币。** 任何地方都没有 EVM 密钥——买家使用其 Solana 密钥签名，而资产则持有在 EVM 地址 *派生* 自此。

* **Solana 签名者：** `55R41dbRU13QhLpAgha1841wR5M6sAcZhXd4S1LGupBn`
* **派生持有地址：** [`0xd868eec27e47376e739d0a3555f81b7657faa322`](https://via-hadrian.testnet.romeprotocol.xyz/address/0xd868eec27e47376e739d0a3555f81b7657faa322) — `keccak256(pubkey)[12..32]`

每一步都是 `DoTxUnsigned`：在 **一笔 Solana 交易**内执行的一笔 EVM 交易，由 Solana 签名授权。购买流程仍然是相同的两个环节，每个环节各自都是一笔 Solana 交易：

| # | 其执行内容            | Solana 交易                                                                                                                                                  | 计算        |
| - | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
| 1 | 从派生地址向商店授权 wUSDC | [`3ohASbQc…3ad5p`](https://explorer.solana.com/tx/3ohASbQcv3L7qPbJfccoZQeN1KX1yPBy4nycdSU6PVWD8DxrpfGgHVymbHHfkLWC5727xE3XJTzf1Fyf5ct3ad5p?cluster=devnet) | \~191K CU |
| 2 | 购买资产             | [`5CdSWWh3…3UkJ`](https://explorer.solana.com/tx/5CdSWWh3A72jy2M843F3udYjiHr2UUM82FrfxjcNJja8RZrj6AQH7mHCMmZafgMFBUGBCMriXQiS7jM36rQZ3UkJ?cluster=devnet)  | \~737K CU |

买家以 **其自身 Solana 钱包中的 lamports**支付交易费用；派生地址从未持有过 SOL。 `positions-solana` 指南中的截图—— *“由你的 Solana 密钥持有”*、托管链以及 ARCV 持仓——在这些交易之后，显示的就是该签名者。

> **同一资产、同一允许名单、任一钱包世界。** EVM 买家和 Solana 买家购买了完全相同的 Solidity 代币，受完全相同的链上允许名单限制，采用完全相同的 wUSDC 定价。唯一的区别在于由哪把密钥签名、由哪个地址持有——这正是两条通道的核心所在，此处已被证明，而非仅仅声称。机制见 [LANES.md](/zh/rome-shang-de-ying-yong/bloom/lanes.md)；合规模型见于 [COMPLIANCE.md](/zh/rome-shang-de-ying-yong/bloom/compliance.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 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/rome-shang-de-ying-yong/bloom/evidence-investor.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.