> For the complete documentation index, see [llms.txt](https://center.bokk.ltd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://center.bokk.ltd/zh/20250528/feng-xian-shai-cha-shi-yong-zhi-nan/trustformer-dong-cha-feng-xian-biao-qian-feng-xian-lai-yuan-de-jie-shi-shuo-ming.md).
# Trustformer洞察-风险标签、风险来源的解释说明
## 1、通过Trustformer系统可以查询到什么信息？
\--Trustformer 地址搜索会输出**两类**信息：
**地址**：地址的TCR信用分值、风险类型、风险标签、风险来源、风险节点
**交易**：交易的TCR信用分值、风险类型、风险标签、风险来源、风险节点
## 2、Trustformer系统的风险标签可以说明什么？
**--风险标签**可判断查询地址或者交易所属的风险类型、直接\间接风险、其他相关标签。
Trustformer系统的风险类型共43种，包括美国政府披露的制裁名单、社区公链公布的风险名单、新闻媒体曝光的黑客盗窃名单等。
（1）涉及美国政治黑名单，SDN名单为主，也参考SEC、CFTC的监管政策 （下面图片为美国政治黑名单相关的风险地址查询）
（2）涉嫌黑客、盗窃、赌博、色情、非法交易、暗网交易、混币、儿童犯罪 （下面图片为盗窃相关的风险地址查询）
（3）涉嫌虚假金融活动、合约审计、赌博、诈骗等风险资金（下面图片为诈骗相关的风险地址查询）
\--与社区治理被公链、合约制裁的钱包地址发生的交易（下面图片为TRON官方浏览器社区公链公布的风险地址查询）
\--涉及金融监管
\--判断转入资金的交易是否安全
\--判断转入资金的交易是否符合监管合规要求
\--判断是否有Sanction风险
\--判断是否有AML
\--判断是否有CFT风险
## 3、Trustformer系统的风险来源包含哪些要素？
**--风险类别**
Trustformer系统可识别43种风险类型（包括盗窃、赌博、色情、非法交易、暗网交易、混币、虐待儿童等）
**--风险层级**
直接
间接
**--风险溯源**
可溯源至风险的源地址
---
# 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://center.bokk.ltd/zh/20250528/feng-xian-shai-cha-shi-yong-zhi-nan/trustformer-dong-cha-feng-xian-biao-qian-feng-xian-lai-yuan-de-jie-shi-shuo-ming.md?ask=&goal=
```
`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.
