etherscan

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Etherscan orchestrator

Etherscan 编排器

Route an Etherscan task to the right interface, then to the right page, endpoint, command, or tool. Use this skill as a workflow and rulebook, not as a source of live chain data. Treat the selected reference and the live authority it names as canonical for current parameters and behavior.

将Etherscan任务路由至合适的界面，再进一步定位到对应页面、端点、命令或工具。本技能作为工作流与规则手册使用，而非实时链数据来源。以所选参考文档及其指定的实时权威来源作为当前参数与行为的标准依据。

Follow the workflow

遵循工作流

Before discovering interfaces, consider the task-relevant specialized skills available in the current environment. Match the user's use case against their descriptions and select the most specific applicable skill; honor an explicitly requested skill when it applies.
When a specialized skill matches, read and follow it completely. Let it own clarification, capability discovery, transport selection, execution, and output; do not independently impose Website, API, CLI, or MCP or add output that violates its contract. Stop this workflow unless the selected skill explicitly returns control.
For example, use
the
```
etherscan-flow
```
skill
for tracing or following money across hops; scam, hack, exploit, drain, phishing, rug-pull, or compromised-wallet investigations; transaction or address flow visualization and case generation; or business and entity income, revenue, fees, spending, expenses, and treasury profiles. Preserve its JSON-only output and per-operation transport priority: official Etherscan CLI → Etherscan MCP → current-invocation
```
apikey=
```
→ other documented key sources.
Keep ordinary explorer navigation in this workflow. For example, route "show this transaction on Etherscan" to the Website unless the user asks to trace or visualize its flow.
When no specialized skill matches, clarify only the chain, target, intent, plan, or output details that the request leaves unresolved.
Discover the Etherscan-relevant tools and connections available in the current environment, then briefly tell the user what is available.
Honor an explicitly requested interface; otherwise select one from Select the interface.
Read that interface reference completely before acting. Read another only for an explicit comparison, required fallback, or genuinely cross-interface workflow.
Confirm the exact chain and chain ID through the selected reference's authority. Never infer support from EVM compatibility.
Construct the exact page, endpoint, command, or tool call documented by that authority.
Return the result with throttling, pagination, truncation, plan restrictions, and error context intact.

在探索界面之前，考虑当前环境中可用的与任务相关的专业技能。将用户的用例与技能描述匹配，选择最适用的特定技能；当用户明确请求的技能适用时，优先采用该技能。
当匹配到专业技能时，完整遵循该技能的指引。由该技能负责澄清需求、功能探索、传输方式选择、执行及输出；不得自行指定Website、API、CLI或MCP，也不得添加违反其约定的输出。除非所选技能明确交还控制权，否则终止本工作流。
例如，对于跨节点追踪资金流向、诈骗/黑客攻击/漏洞利用/资金窃取/钓鱼/rug-pull/钱包被盗调查、交易或地址流可视化及案例生成，或业务与实体的收入、营收、费用、支出及金库概况等场景，使用
```
etherscan-flow
```
技能
。保留其仅JSON格式的输出及按操作优先级排序的传输方式：官方Etherscan CLI → Etherscan MCP → 当前调用的
```
apikey=
```
→ 其他已记录的密钥来源。
常规浏览器导航仍使用本工作流。例如，将“在Etherscan上显示该交易”请求路由至Website，除非用户要求追踪或可视化其流向。
当无匹配的专业技能时，仅澄清请求中未明确的链、目标、意图、计划或输出细节。
探索当前环境中可用的Etherscan相关工具与连接，然后向用户简要说明可用选项。
优先遵循用户明确请求的界面；否则从选择界面中选取合适的界面。
在执行操作前完整阅读所选界面的参考文档。仅在需要明确对比、必要回退或真正跨界面工作流时，才阅读其他界面的文档。
通过所选参考文档的权威来源确认确切的链及链ID。切勿从EVM兼容性推断支持情况。
按照该权威文档构建确切的页面、端点、命令或工具调用。
返回结果时保留限流、分页、截断、计划限制及错误上下文信息。

Discover local capabilities

探索本地功能

Use non-mutating checks to identify the task-relevant Etherscan interfaces available in the current environment before choosing a route.

Check whether the Etherscan CLI is installed. If it is, inspect its reported version and live help rather than assuming its commands or flags.
Inspect callable MCP connections and their advertised tools when discovery is available. Distinguish configured, connected, and authenticated access from a merely documented MCP server.
Note relevant browser, web, or HTTP access when it materially affects how the task can be completed.
Briefly mention the relevant capabilities found, such as an installed Etherscan CLI and version, and explain when one changes the selected route.
Treat an unavailable check as unknown rather than claiming that the capability does not exist.
Do not install software, authenticate, connect accounts, reveal credentials, or read secret values merely to inventory capabilities.

在选择路由前，使用非变更性检查识别当前环境中可用的与任务相关的Etherscan接口。

检查Etherscan CLI是否已安装。若已安装，查看其报告的版本及实时帮助信息，而非默认假设其命令或参数。
当支持发现功能时，检查可调用的MCP连接及其公示的工具。区分已配置、已连接且已认证的访问权限与仅记录在文档中的MCP服务器。
记录与任务完成方式密切相关的浏览器、网页或HTTP访问能力。
简要说明已发现的相关功能，例如已安装的Etherscan CLI及其版本，并解释当某一功能改变所选路由的原因。
将无法检查的功能标记为未知，而非声称该功能不存在。
不得仅为盘点功能而安装软件、进行认证、连接账户、泄露凭证或读取机密值。

Clarify before acting

执行前澄清

Ask only for information that is required and genuinely missing.

Confirm the exact chain and chain ID; one API key spans many chains, so an implicit chain can produce a valid result for the wrong network.
Identify the address, transaction, token, contract, or block in scope. Distinguish target types when the live capability documents different behavior for them.
Distinguish read-only inspection from verification, broadcast, configuration deletion, or another external write.
Confirm API-plan access when the selected endpoint or tool is gated. Prefer an available free-tier route when the plan is unknown, or state that access may be restricted.
Choose interactive review, structured JSON or CSV, or an agent tool call according to the requested output.

仅询问必需且确实缺失的信息。

确认确切的链及链ID；一个API密钥可用于多条链，因此隐含的链可能会针对错误网络生成有效结果。
确定范围内的地址、交易、代币、合约或区块。当实时功能文档针对不同目标类型有不同行为描述时，需区分目标类型。
区分只读检查与验证、广播、配置删除或其他外部写入操作。
当选定的端点或工具受权限限制时，确认API访问计划。当计划未知时，优先选择可用的免费层级路由，或说明访问可能受限。
根据用户请求的输出格式，选择交互式审核、结构化JSON或CSV，或Agent工具调用。

Select the interface

选择界面

Honor an explicitly requested interface first. Otherwise, choose by the user's intended execution environment and output.

Interface	Read	Use it for
Website	Website feature reference.	Locate explorer pages, user-facing tools, exports, token approvals, contract utilities, trackers, and support resources.
API	API reference.	Select endpoints, construct requests, interpret responses, check authentication, plans, rate limits, errors, and supported chains.
CLI	CLI reference.	Select terminal commands, configure the client, automate queries, produce structured output, paginate, and export data.
MCP	MCP reference.	Connect an MCP client, discover tools, inspect schemas, construct calls, and distinguish MCP-layer failures from API-level errors.

When the user does not specify an interface, apply these defaults.

Prefer the website for an interactive human workflow.
Prefer the API for an application integration or when the broadest endpoint coverage is required.
Prefer the CLI for terminal automation, pipelines, or exports.
Prefer MCP for agent-driven, read-only tool calls when an authenticated MCP connection is available.

优先遵循用户明确请求的界面。否则，根据用户的预期执行环境与输出格式进行选择。

界面	参考文档	使用场景
Website	网站功能参考文档	查找浏览器页面、面向用户的工具、导出功能、代币授权、合约工具、追踪器及支持资源。
API	API参考文档	选择端点、构建请求、解读响应、检查身份验证、访问计划、速率限制、错误信息及支持的链。
CLI	CLI参考文档	选择终端命令、配置客户端、自动化查询、生成结构化输出、分页及导出数据。
MCP	MCP参考文档	连接MCP客户端、发现工具、检查 schema、构建调用，并区分MCP层故障与API级错误。

当用户未指定界面时，应用以下默认规则：

对于交互式人工工作流，优先选择Website。
对于应用集成或需要最广泛端点覆盖的场景，优先选择API。
对于终端自动化、流水线或导出操作，优先选择CLI。
当已认证的MCP连接可用时，对于Agent驱动的只读工具调用，优先选择MCP。

Respect capability boundaries

尊重功能边界

Do not infer that a capability available through one interface exists through another. Discover current capabilities through the selected interface's live authority.
Treat MCP as read-only unless current tool discovery and official documentation explicitly establish a state-changing capability. Require the same exact authorization applied to every other write.
Confirm the exact chain and chain ID instead of inferring support from EVM compatibility.
Verify volatile parameters, schemas, availability, plan access, limits, and supported chains through the authority named by the selected reference.
Preserve throttling, pagination, truncation warnings, restrictions, and returned error context.
Switch interfaces only when the selected reference shows that the original interface cannot complete the task or the user requests another interface.

不得推断某一界面可用的功能在另一界面也存在。需通过所选界面的实时权威来源探索当前功能。
除非当前工具发现结果与官方文档明确说明存在状态变更功能，否则将MCP视为只读。对所有写入操作应用相同的严格授权要求。
确认确切的链及链ID，而非从EVM兼容性推断支持情况。
通过所选参考文档指定的权威来源验证易变参数、schema、可用性、访问计划、限制及支持的链。
保留限流、分页、截断警告、限制及返回的错误上下文信息。
仅当所选参考文档显示原界面无法完成任务，或用户请求切换界面时，才更换界面。

Apply guardrails

应用防护规则

Replace any exposed Etherscan API key with
```
YourApiKeyToken
```
. Never print, commit, reproduce, or place credentials in prompts, source files, logs, or output.
Avoid uncontrolled retry loops, and respect both plan-wide and endpoint-specific throttles.
Require explicit user authorization for the exact contract-verification submission, signed raw-transaction broadcast, destructive configuration change, or other state-changing action.
Prefer read-only inspection until the user authorizes the exact state-changing action, payload, and chain.
Preserve API, transport, validation, and application-level errors as distinct failure contexts.

将任何暴露的Etherscan API密钥替换为
```
YourApiKeyToken
```
。切勿在提示、源文件、日志或输出中打印、提交、复制或放置凭证。
避免无控制的重试循环，同时遵守全局计划与端点特定的限流规则。
对于确切的合约验证提交、签名原始交易广播、破坏性配置变更或其他状态变更操作，需获得用户的明确授权。
在用户授权确切的状态变更操作、负载及链之前，优先选择只读检查。
区分保留API、传输、验证及应用级错误作为不同的故障上下文。

Workflow checks

工作流检查

Use these representative cases to verify routing and guardrail behavior after changing this skill. Treat them as behavioral guidance, not live API assertions.

Request or condition	Expected behavior
Show an address in the block explorer.	Use the website reference and an interactive address page.
Export a wallet's ERC-20 transfers to CSV from a terminal.	Use the CLI reference and its pagination and CSV support.
Call an agent tool to retrieve a balance.	Use MCP when live discovery advertises a matching tool; inspect its current schema before calling it.
Integrate token-holder counts into a backend.	Use the API and discover the current endpoint from official documentation; do not invent an MCP tool.
The Etherscan CLI is installed locally.	Mention the installed version, inspect its live help, and use it when it matches the requested environment and output.
An MCP server is documented but live discovery is unavailable.	Report its availability as unknown; do not describe it as connected or infer its tool inventory.
The user explicitly requests an interface.	Honor it unless it cannot perform the task; explain any required fallback.
A balance request omits the chain.	Ask for the chain or chain ID before querying.
A capability may restrict target types or plan access.	Verify and surface the current restrictions before calling it.
A workflow requests a verification or signed transaction broadcast.	Confirm the exact payload, chain, interface, and authorization before submission.
A workflow requests an MCP verification or broadcast.	Verify whether live discovery exposes the operation; otherwise offer an authorized interface that does.
Input contains an API key or requests stored CLI credentials.	Replace the key with `YourApiKeyToken` and never print the stored plaintext credential.

修改本技能后，使用以下典型案例验证路由与防护规则的行为。将这些案例视为行为指引，而非实时API断言。

请求或条件	预期行为
在区块浏览器中显示某一地址。	使用Website参考文档及交互式地址页面。
从终端将钱包的ERC-20转账记录导出为CSV。	使用CLI参考文档及其分页与CSV支持功能。
调用Agent工具获取余额。	当实时发现结果公示匹配工具时使用MCP；调用前检查其当前schema。
将代币持有者数量集成至后端。	使用API并从官方文档中查找当前端点；不得自行创建MCP工具。
本地已安装Etherscan CLI。	提及已安装的版本，查看其实时帮助信息，并在其匹配请求的环境与输出格式时使用。
MCP服务器已记录在文档中，但无法进行实时发现。	报告其可用性为未知；不得描述为已连接或推断其工具清单。
用户明确请求某一界面。	优先遵循该界面，除非其无法完成任务；解释任何必要的回退方案。
余额请求未指定链。	查询前询问链或链ID。
某一功能可能限制目标类型或访问计划。	调用前验证并告知当前限制。
工作流请求验证或签名交易广播。	提交前确认确切的负载、链、界面及授权。
工作流请求MCP验证或广播。	验证实时发现结果是否公开该操作；否则提供支持该操作的已授权界面。
输入包含API密钥或请求存储的CLI凭证。	将密钥替换为 `YourApiKeyToken` ，切勿打印存储的明文凭证。