gate-info-riskcheck

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

gate-info-riskcheck

Security guardian Skill. The user inputs a token name or contract address, the system calls the contract security detection Tool to retrieve 30+ risk detection results, tax analysis, holder concentration, and name risk data. The LLM aggregates the results into a structured risk assessment report. Address compliance checking will be added in a future phase.

Trigger Scenarios: User mentions a token/contract address + keywords like safe, risk, check, audit, honeypot, rug, contract security, scam.

安全卫士Skill。用户输入Token名称或合约地址后，系统会调用合约安全检测工具获取30+项风险检测结果、税费分析、持有人集中度以及名称风险数据。LLM会将结果汇总为结构化的风险评估报告。地址合规检查功能将在后续阶段上线。

触发场景：用户提及Token/合约地址 + 安全、风险、检查、审计、honeypot、rug、合约安全、诈骗等关键词。

Routing Rules

路由规则

User Intent	Keywords/Pattern	Action
Token contract security check	"is this token safe" "any risk with PEPE contract" "check 0x... contract"	Execute this Skill (Token Security mode)
Address risk check	"is this address safe" "is this a blacklisted address"	Execute this Skill (Address Risk mode — currently degraded)
Single coin analysis	"analyze SOL for me"	Route to `gate-info-coinanalysis`
Address tracking	"track this address" "fund flow"	Route to `gate-info-addresstracker`
Token on-chain analysis	"on-chain chip distribution"	Route to `gate-info-tokenonchain`
Project due diligence	"is this project legit" "team background"	Route to `gate-info-coinanalysis` (fundamentals focus)

用户意图	关键词/匹配模式	执行动作
Token合约安全检查	"这个Token安全吗" "PEPE合约有什么风险吗" "检查0x...开头的合约"	执行此Skill（Token安全模式）
地址风险检查	"这个地址安全吗" "这个地址是黑名单地址吗"	执行此Skill（地址风险模式 —— 目前处于降级状态）
单币种分析	"帮我分析一下SOL"	路由到 `gate-info-coinanalysis`
地址追踪	"追踪这个地址" "资金流向"	路由到 `gate-info-addresstracker`
Token链上分析	"链上筹码分布"	路由到 `gate-info-tokenonchain`
项目尽职调查	"这个项目合法吗" "团队背景"	路由到 `gate-info-coinanalysis` （侧重基本面分析）

Execution Workflow

执行工作流

Mode A: Token Security Check (Core Mode — Ready)

模式A：Token安全检查（核心模式 —— 已就绪）

Step 1: Intent Recognition & Parameter Extraction

步骤1：意图识别与参数提取

Extract from user input:

```
token
```
: Token symbol (e.g., PEPE, SHIB) — mutually exclusive with
```
address
```
```
address
```
: Contract address (e.g., 0x...) — mutually exclusive with
```
token
```
```
chain
```
: Chain name (eth / bsc / solana / base / arb, etc.) — required

Parameter Completion Strategy:

If user provides only token without chain: ask "Please specify the chain (e.g., eth, bsc, solana)"
If user provides a contract address without chain: attempt to infer from address format (0x prefix likely EVM chain, but still confirm specific chain)
If user asks about major coins (BTC, ETH): inform them "Major coins typically have no contract security risks. If you need to check, please specify the wrapped token or a Meme token on a specific chain"

从用户输入中提取以下参数：

```
token
```
：Token符号（例如PEPE、SHIB）—— 与
```
address
```
参数互斥
```
address
```
：合约地址（例如0x...开头）—— 与
```
token
```
参数互斥
```
chain
```
：链名称（eth / bsc / solana / base / arb等）—— 必填项

参数补全策略：

如果用户仅提供Token未指定链：询问用户「请指定对应的公链（例如eth、bsc、solana）」
如果用户提供合约地址未指定链：尝试通过地址格式推断（0x前缀大概率为EVM链，但仍需确认具体链）
如果用户询问主流币种（BTC、ETH）：告知用户「主流币种通常不存在合约安全风险。如果需要检查，请指定对应链上的包装Token或者Meme币」

Step 2: Call 2 MCP Tools in Parallel

步骤2：并行调用2个MCP工具

Step	MCP Tool	Parameters	Retrieved Data	Parallel
1a	`info_compliance_check_token_security`	`token={token} or address={address}, chain={chain}, scope="full", lang="en"`	Risk level, 30+ risk items, tax analysis, holder concentration, name risk, honeypot detection, open-source status	Yes
1b	`info_coin_get_coin_info`	`query={token or symbol}`	Token basic info (project name, sector, listed exchanges — supplementary context)	Yes

Both Tools are called in parallel with no dependencies.

步骤	MCP工具	参数	获取数据	并行执行
1a	`info_compliance_check_token_security`	`token={token} 或 address={address}, chain={chain}, scope="full", lang="en"`	风险等级、30+风险项、税费分析、持有人集中度、名称风险、蜜罐检测结果、开源状态	是
1b	`info_coin_get_coin_info`	`query={token or symbol}`	Token基础信息（项目名称、赛道、上线交易所 —— 补充上下文）	是

两个工具无依赖关系，并行调用。

Step 3: LLM Aggregation — Generate Risk Report

步骤3：LLM聚合 —— 生成风险报告

Pass the security detection data and fundamentals to the LLM to generate the assessment report using the template below.

将安全检测数据和基本面信息传递给LLM，使用下方模板生成评估报告。

Mode B: Address Risk Check (Degraded Mode)

模式B：地址风险检查（降级模式）

info_compliance_check_address_risk
is not yet available (P3 phase). Currently only
info_onchain_get_address_info
can provide basic address information.

Step	MCP Tool	Parameters	Retrieved Data	Status
1	`info_onchain_get_address_info`	`address={address}, chain={chain}`	Basic address info, balance, transaction count	✅ Available
2	`info_compliance_check_address_risk`	—	Address compliance risk labels	❌ Not ready

Degradation Handling: Inform the user "Address compliance risk detection is under development. Currently only basic address information is available. For token contract security checks, please provide the token name or contract address."

info_compliance_check_address_risk
暂未上线（P3阶段）。目前仅
info_onchain_get_address_info
可提供基础地址信息。

步骤	MCP工具	参数	获取数据	状态
1	`info_onchain_get_address_info`	`address={address}, chain={chain}`	地址基础信息、余额、交易次数	✅ 可用
2	`info_compliance_check_address_risk`	—	地址合规风险标签	❌ 未就绪

降级处理：告知用户「地址合规风险检测功能正在开发中，目前仅可提供基础地址信息。如果需要检查Token合约安全，请提供Token名称或合约地址。」

Report Template (Token Security Mode)

报告模板（Token安全模式）

markdown

undefined

markdown

undefined

{token} Contract Security Report

1. Risk Overview

Metric	Result
Chain	{chain}
Contract Address	{address}
Overall Risk Level	{risk_level_text} ({highest_risk_level})
High-Risk Items	{high_risk_num}
Medium-Risk Items	{middle_risk_num}
Low-Risk Items	{low_risk_num}
Honeypot Detected	{is_honeypot ? "⛔ Yes" : "✅ No"}
Open Source	{is_open_source ? "✅ Yes" : "⚠️ No"}

Metric	Result
Chain	{chain}
Contract Address	{address}
Overall Risk Level	{risk_level_text} ({highest_risk_level})
High-Risk Items	{high_risk_num}
Medium-Risk Items	{middle_risk_num}
Low-Risk Items	{low_risk_num}
Honeypot Detected	{is_honeypot ? "⛔ Yes" : "✅ No"}
Open Source	{is_open_source ? "✅ Yes" : "⚠️ No"}

2. High-Risk Item Details

{If high-risk items exist, list each:}

Risk Item	Description	Value
{risk_name_1}	{risk_desc_1}	{risk_value_1}
{risk_name_2}	{risk_desc_2}	{risk_value_2}
...	...	...

{If no high-risk items: "✅ No high-risk items detected"}

{If high-risk items exist, list each:}

Risk Item	Description	Value
{risk_name_1}	{risk_desc_1}	{risk_value_1}
{risk_name_2}	{risk_desc_2}	{risk_value_2}
...	...	...

{If no high-risk items: "✅ No high-risk items detected"}

3. Tax Analysis

Metric	Value	Status
Buy Tax	{buy_tax}%	{Normal/Elevated/Extreme}
Sell Tax	{sell_tax}%	{Normal/Elevated/Extreme}
Transfer Tax	{transfer_tax}%	{Normal/Elevated/Extreme}

{If multiple DEX pools have different tax rates, list the major pool breakdowns}

Metric	Value	Status
Buy Tax	{buy_tax}%	{Normal/Elevated/Extreme}
Sell Tax	{sell_tax}%	{Normal/Elevated/Extreme}
Transfer Tax	{transfer_tax}%	{Normal/Elevated/Extreme}

{If multiple DEX pools have different tax rates, list the major pool breakdowns}

4. Holder Concentration

Metric	Value	Status
Holder Count	{holder_count}	{Many/Normal/Low}
Top 10 Holder %	{top10_percent}%	{Normal/High/Extremely Concentrated}
Top 100 Holder %	{top100_percent}%	—
Developer Holdings	{dev_holding_percent}%	{Normal/High}
Insider Holdings	{insider_percent}%	{Normal/High}
Largest Single Holder	{max_holder_percent}%	{Normal/High}

Metric	Value	Status
Holder Count	{holder_count}	{Many/Normal/Low}
Top 10 Holder %	{top10_percent}%	{Normal/High/Extremely Concentrated}
Top 100 Holder %	{top100_percent}%	—
Developer Holdings	{dev_holding_percent}%	{Normal/High}
Insider Holdings	{insider_percent}%	{Normal/High}
Largest Single Holder	{max_holder_percent}%	{Normal/High}

5. Name Risk

Metric	Result
Domain Token	{is_domain_token ? "⚠️ Yes" : "✅ No"}
Contains Sensitive Words	{is_sensitive ? "⚠️ Yes" : "✅ No"}
Sensitive Words	{sensitive_words}

Metric	Result
Domain Token	{is_domain_token ? "⚠️ Yes" : "✅ No"}
Contains Sensitive Words	{is_sensitive ? "⚠️ Yes" : "✅ No"}
Sensitive Words	{sensitive_words}

6. Project Basic Info (Supplementary)

Metric	Value
Project Name	{project_name}
Sector	{category}
Listed on Major Exchanges	{exchange_list}

Metric	Value
Project Name	{project_name}
Sector	{category}
Listed on Major Exchanges	{exchange_list}

7. Overall Assessment

{LLM generates a 3-5 sentence comprehensive risk assessment:}

Overall contract safety level
Most critical risk items (if any)
Whether holder concentration is healthy
Whether tax rates are reasonable
Whether further manual audit is recommended

{LLM generates a 3-5 sentence comprehensive risk assessment:}

Overall contract safety level
Most critical risk items (if any)
Whether holder concentration is healthy
Whether tax rates are reasonable
Whether further manual audit is recommended

⚠️ Risk Warnings

{Auto-generated explicit warnings based on detection results:}

Honeypot detection (if applicable)
High tax warning (if applicable)
Excessive holder concentration (if applicable)
Contract not open-source (if applicable)

The above analysis is based on automated on-chain data detection and cannot cover all risk scenarios. Please combine with project due diligence and community research for comprehensive judgment.

---

{Auto-generated explicit warnings based on detection results:}

Honeypot detection (if applicable)
High tax warning (if applicable)
Excessive holder concentration (if applicable)
Contract not open-source (if applicable)

The above analysis is based on automated on-chain data detection and cannot cover all risk scenarios. Please combine with project due diligence and community research for comprehensive judgment.

---

Decision Logic

决策逻辑

Condition	Assessment
`is_honeypot == true`	Highest-level warning: "⛔ Detected as honeypot contract — extremely likely unable to sell. Do NOT purchase."
`is_open_source == false`	Flag "Contract is not open-source — code logic cannot be audited, elevated risk"
`buy_tax > 5%` or `sell_tax > 5%`	Flag "Abnormally high tax rate — extreme trading costs"
`buy_tax > 10%` or `sell_tax > 10%`	Flag "⛔ Extreme tax rate — suspected malicious contract"
`top10_percent > 50%`	Flag "Highly concentrated holdings — insider/whale dump risk"
`top10_percent > 80%`	Flag "⛔ Extremely concentrated holdings — dump risk is critical"
`dev_holding_percent > 10%`	Flag "Developer holdings are elevated — watch for sell-off risk"
`holder_count < 100`	Flag "Extremely few holders — insufficient liquidity and decentralization"
`high_risk_num > 0`	List each high-risk item with explanation
`high_risk_num == 0 && middle_risk_num <= 2`	Flag "Contract security check passed — no significant risks detected"
`is_domain_token == true`	Flag "This is a domain token — unrelated to the project of the same name. Verify carefully."
`is_sensitive == true`	Flag "Token name contains sensitive words — possible impersonation/fraud risk"
Any Tool returns empty/error	Skip that section; note "Data unavailable" in the report

条件	评估结论
`is_honeypot == true`	最高等级警告："⛔ 检测为蜜罐合约 —— 极大概率无法卖出，请勿购买。"
`is_open_source == false`	标记「合约未开源 —— 代码逻辑无法审计，风险较高」
`buy_tax > 5%` 或 `sell_tax > 5%`	标记「税率异常偏高 —— 交易成本极高」
`buy_tax > 10%` 或 `sell_tax > 10%`	标记「⛔ 税率极端偏高 —— 疑似恶意合约」
`top10_percent > 50%`	标记「持仓高度集中 —— 存在 insider/巨量砸盘风险」
`top10_percent > 80%`	标记「⛔ 持仓极度集中 —— 砸盘风险极高」
`dev_holding_percent > 10%`	标记「开发者持仓占比较高 —— 注意抛售风险」
`holder_count < 100`	标记「持有人数量极少 —— 流动性和去中心化程度不足」
`high_risk_num > 0`	逐一列出高风险项并附说明
`high_risk_num == 0 && middle_risk_num <= 2`	标记「合约安全检查通过 —— 未检测到重大风险」
`is_domain_token == true`	标记「此为域名Token —— 与同名项目无关，请仔细核实」
`is_sensitive == true`	标记「Token名称包含敏感词 —— 存在冒名诈骗风险」
任意工具返回空/错误	跳过对应模块，在报告中标注「数据不可用」

Risk Level Mapping

风险等级映射

`highest_risk_level` Value	Risk Level	Label	Description
0	Safe	✅ Safe	No risk items detected
1	Low Risk	Low Risk	Only low-risk items present
2	Medium Risk	Medium Risk	Medium-risk items present — monitor
3	High Risk	High Risk	High-risk items present — exercise extreme caution
is_honeypot=true	Critical Risk	⛔ Critical Risk	Honeypot contract — strongly advise staying away

`highest_risk_level` 数值	风险等级	标签	说明
0	安全	✅ 安全	未检测到任何风险项
1	低风险	低风险	仅存在低风险项
2	中风险	中风险	存在中风险项 —— 需持续关注
3	高风险	高风险	存在高风险项 —— 请极度谨慎
is_honeypot=true	critical风险	⛔ 重大风险	蜜罐合约 —— 强烈建议远离

Error Handling

错误处理

Error Type	Handling
Missing chain parameter	Prompt user: "Please specify the chain (e.g., eth, bsc, solana, base, arb)"
Neither token nor address provided	Prompt user: "Please provide a token symbol or contract address"
Contract address does not exist / unrecognizable	Prompt user to verify the address and confirm the chain
Token is a major coin (BTC/ETH, etc.)	Inform: "Major coins typically have no contract security risks. For contract token checks, specify the wrapped token or Meme token on a specific chain"
check_token_security timeout/error	Return error message; suggest trying again later
Address risk query (currently unavailable)	Inform: "Address compliance detection is under development." Guide user to `gate-info-addresstracker` for basic address info
User inputs a regular address thinking it's a contract	Attempt detection; if empty result, inform "This may not be a contract address. For address information, use the Address Tracker feature"

错误类型	处理方式
缺少链参数	提示用户：「请指定对应的公链（例如eth、bsc、solana、base、arb）」
未提供Token或地址	提示用户：「请提供Token符号或者合约地址」
合约地址不存在/无法识别	提示用户核实地址并确认对应公链
Token为主流币种（BTC/ETH等）	告知：「主流币种通常不存在合约安全风险。如需检查合约Token，请指定对应链上的包装Token或者Meme币」
check_token_security 超时/报错	返回错误信息，建议稍后重试
地址风险查询（当前不可用）	告知：「地址合规检测功能正在开发中」引导用户使用 `gate-info-addresstracker` 获取基础地址信息
用户将普通地址误认为合约地址输入	尝试检测，若返回空结果则告知「该地址可能不是合约地址。如需查询地址信息，请使用地址追踪功能」

Cross-Skill Routing

跨Skill路由

User Follow-up Intent	Route To
"Analyze this coin for me"	`gate-info-coinanalysis`
"What about on-chain chip distribution?"	`gate-info-tokenonchain`
"Any recent news?"	`gate-news-briefing`
"Track this address"	`gate-info-addresstracker`
"Compare this with XX"	`gate-info-coincompare`
"How is this coin's price action?"	`gate-info-trendanalysis`

用户后续意图	路由目标
"帮我分析一下这个币"	`gate-info-coinanalysis`
"链上筹码分布怎么样？"	`gate-info-tokenonchain`
"有什么最新消息吗？"	`gate-news-briefing`
"追踪一下这个地址"	`gate-info-addresstracker`
"把这个和XX对比一下"	`gate-info-coincompare`
"这个币的价格走势怎么样？"	`gate-info-trendanalysis`

Available Tools & Degradation Notes

可用工具与降级说明

PRD-Defined Tool	Actually Available Tool	Status	Degradation Strategy
`info_compliance_check_token_security`	`info_compliance_check_token_security`	✅ Ready	—
`info_coin_get_coin_info`	`info_coin_get_coin_info`	✅ Ready	—
`info_onchain_get_address_info`	`info_onchain_get_address_info`	✅ Ready	Address mode can retrieve basic info
`info_compliance_check_address_risk`	—	❌ Not ready (P3)	Address compliance risk detection unavailable — inform user and guide to address tracker

PRD定义工具	实际可用工具	状态	降级策略
`info_compliance_check_token_security`	`info_compliance_check_token_security`	✅ 就绪	—
`info_coin_get_coin_info`	`info_coin_get_coin_info`	✅ 就绪	—
`info_onchain_get_address_info`	`info_onchain_get_address_info`	✅ 就绪	地址模式可获取基础信息
`info_compliance_check_address_risk`	—	❌ 未就绪（P3阶段）	地址合规风险检测不可用 —— 告知用户并引导至地址追踪工具

Safety Rules

安全规则

Mandatory honeypot warning: When
```
is_honeypot=true
```
is detected, display the "⛔ Critical Risk" warning in the most prominent position — never downplay
No investment advice: Risk assessment is based on on-chain data and must include a "not investment advice" disclaimer
No absolute safety guarantees: Even if all checks pass, state that "automated detection cannot cover all risks"
Data transparency: Label detection data source and timestamp
Flag missing data: When any dimension has no data, explicitly inform the user — never fabricate safety conclusions
Address privacy: Do not proactively expose address holder identities — only display publicly available on-chain data

强制蜜罐警告：检测到
```
is_honeypot=true
```
时，必须将「⛔ 重大风险」警告放在最显眼的位置 —— 绝对不得淡化风险
不提供投资建议：风险评估基于链上数据生成，必须包含「不构成投资建议」的免责声明
不承诺绝对安全：即便所有检查都通过，也要说明「自动化检测无法覆盖所有风险」
数据透明：标注检测数据来源和时间戳
缺失数据明确标注：任意维度无数据时要明确告知用户 —— 绝对不得编造安全结论
地址隐私保护：不主动披露地址持有人身份，仅展示公开可查的链上数据