binance-wallet-tracker

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Binance Wallet Tracker Skill

Binance Wallet Tracker技能

On-chain wallet tracking and monitoring. Monitor token-level and trade-level activity for private groups or public Smart Money / KOL data. Includes 9 built-in analysis scenarios for replay and pattern detection.

链上钱包追踪与监控工具。可监控私有群组或公开Smart Money/KOL数据的代币级和交易级活动，内置9种复盘与模式检测分析场景。

Prerequisites

前置条件

This skill requires the

baw

CLI (

@binance/agentic-wallet

npm package). If

baw

is not found:

bash

npm install -g @binance/agentic-wallet

Verify:

baw --version

should print

1.6.2

or higher. If installation fails or the user doesn't have Node.js, inform them that Node.js >= 18 is required.

使用该技能需要

baw

CLI工具（

@binance/agentic-wallet

npm包）。若未检测到

baw

：

bash

npm install -g @binance/agentic-wallet

验证：执行

baw --version

应返回

1.6.2

或更高版本。若安装失败或用户未安装Node.js，请告知用户需要Node.js ≥ 18版本。

When to Use

适用场景

Discovery

发现

User intent	Command
Consensus tokens (many buyers)	`tracker token query` → sort by `consensusCount`
Pioneer tokens (≤2 traders)	`tracker token query` → filter `launchTime` + `consensusCount ≤ 2`
Leaderboard diff (untracked wallets)	`leaderboard query` (leaderboard skill) + `tracker address list` → diff
Token-based buyer lookup	`tracker tx query` → client-side filter by `ca`
Time-window summary	`tracker token query --period 4h` + `tracker tx query`
Similar wallet discovery	`leaderboard analyze` (leaderboard skill) → archetype matching

用户意图	命令
共识代币（大量买家）	`tracker token query` → 按 `consensusCount` 排序
先锋代币（≤2名交易者）	`tracker token query` → 筛选 `launchTime` + `consensusCount ≤ 2`
排行榜差异（未追踪钱包）	`leaderboard query` （排行榜技能） + `tracker address list` → 对比差异
基于代币的买家查询	`tracker tx query` → 客户端按 `ca` 筛选
时间窗口汇总	`tracker token query --period 4h` + `tracker tx query`
相似钱包发现	`leaderboard analyze` （排行榜技能） → 原型匹配

Evaluation

评估

User intent	Command
Token risk screening	`tracker token query` → filter `tokenRiskLevel ≥ 3` + `consensusCount ≥ 3`
Group rhythm profiling	`tracker tx query` → per-address rhythm analysis
Follow list assessment	`tracker follow` + `leaderboard analyze` (cross-skill)
Token heat analysis	`tracker tx query` → aggregate by `ca`

用户意图	命令
代币风险筛查	`tracker token query` → 筛选 `tokenRiskLevel ≥ 3` + `consensusCount ≥ 3`
群组节奏分析	`tracker tx query` → 单地址节奏分析
关注列表评估	`tracker follow` + `leaderboard analyze` （跨技能）
代币热度分析	`tracker tx query` → 按 `ca` 聚合

Replay

复盘

User intent	Command
4h comprehensive summary	`tracker token query --period 4h` + `tracker tx query`
Accumulation vs distribution (Accumulation/Distribution)	`tracker token query` → `buyCount` / `sellCount` per address
Sector rotation	`tracker tx query` → compare token top across time windows
Anomaly large orders	`tracker tx query` → `anomaly` detection
Round-trip (Round-Trip)	`tracker tx query` → `round-trip` detection
First-mover + leader-follower	`tracker tx query` → `first-mover` + `leader-follower`
Wake-up detection	`tracker tx query` → `wake-up` detection
Bot-like behavior	`tracker tx query` → `bot-like` detection

Full 9-scenario analysis rules:

references/analytics.md

用户意图	命令
4小时综合汇总	`tracker token query --period 4h` + `tracker tx query`
筹码收集vs派发（Accumulation/Distribution）	`tracker token query` → 单地址 `buyCount` / `sellCount`
板块轮动	`tracker tx query` → 对比不同时间窗口的代币排名
大额异常订单	`tracker tx query` → `anomaly` 检测
往返交易（Round-Trip）	`tracker tx query` → `round-trip` 检测
先行者+跟投者	`tracker tx query` → `first-mover` + `leader-follower`
唤醒行为检测	`tracker tx query` → `wake-up` 检测
类机器人行为	`tracker tx query` → `bot-like` 检测

完整9场景分析规则：

references/analytics.md

Management

管理

User intent	Command
Create / rename group	`tracker group create/update`
Batch import addresses	`tracker address batch`
Add single address	`tracker address add`
	Update label / link to group
Delete addresses	`tracker address delete`
Follow / unfollow address	`tracker address follow/unfollow`
View follow list	`tracker follow`
Search address (fuzzy)	`tracker address search`

用户意图	命令
创建/重命名群组	`tracker group create/update`
批量导入地址	`tracker address batch`
添加单个地址	`tracker address add`
更新标签/关联到群组	`tracker address update -l` + `tracker address link`
删除地址	`tracker address delete`
关注/取消关注地址	`tracker address follow/unfollow`
查看关注列表	`tracker follow`
模糊搜索地址	`tracker address search`

Supported Chains

支持的链

Chain	chainId
BSC	`56`
Solana	`CT_501`
Base	`8453`
Ethereum	`1`

链	chainId
BSC	`56`
Solana	`CT_501`
Base	`8453`
Ethereum	`1`

Command Tree

命令树

baw tracker
  token query                # Token dimension monitor (private + --tag-type for public)
  tx query                   # Trade dimension monitor (private + --tag-type for public)
  follow                     # Query current user follow list (read-only, chainId only)
  ws                         # WebSocket real-time push (--smy/--kol/--wallet/--address/--following)
  group
    list                     # Group list
    create                   # Create group
    update                   # Rename group
  address
    search                   # Fuzzy search address
    list                     # Paginated address list
    add                      # Add single address (wraps import)
    batch                    # Batch import
    update                   # Update label (label only)
    link                     # Link to group (group/link)
    delete                   # Delete (supports batch)
    follow                   # Follow address
    unfollow                 # Unfollow

All commands support

--json

for structured output.

token query
and
tx query
require either
--group-id
(private group) or
--tag-type
(public KOL/SMY). Calling without either returns an error.

--tag-type
accepts:
kol
(KOL),
smy
(Smart Money).

baw tracker
  token query                # 代币维度监控（私有群组 + --tag-type查询公开数据）
  tx query                   # 交易维度监控（私有群组 + --tag-type查询公开数据）
  follow                     # 查询当前用户的关注列表（仅支持chainId参数）
  ws                         # WebSocket实时推送（--smy/--kol/--wallet/--address/--following）
  group
    list                     # 群组列表
    create                   # 创建群组
    update                   # 重命名群组
  address
    search                   # 模糊搜索地址
    list                     # 分页地址列表
    add                      # 添加单个地址（封装导入功能）
    batch                    # 批量导入
    update                   # 更新标签（仅支持标签修改）
    link                     # 关联到群组（group/link）
    delete                   # 删除地址（支持批量）
    follow                   # 关注地址
    unfollow                 # 取消关注

所有命令支持

--json

参数以输出结构化数据。

token query
和
tx query
必须指定
--group-id
（私有群组）或
--tag-type
（公开KOL/SMY）。若未指定任一参数，将返回错误。

--tag-type
支持的值：
kol
（KOL）、
smy
（Smart Money）。

Token Monitor (A2)

代币监控（A2）

bash

undefined

bash

undefined

Private — own group data (must specify --group-id or --tag-type)

私有数据——自有群组数据（必须指定--group-id或--tag-type）

baw tracker token query -c 56 --group-id 1 --json baw tracker token query -c 56 --group-id 1 --period 4h --json

Public — SMY/KOL data

公开数据——SMY/KOL数据

baw tracker token query -c 56 --tag-type kol --json # KOL baw tracker token query -c CT_501 --tag-type smy --json # Smart Money


Returns per-token aggregated data: token name, CA, price, market cap, volume, `addressList[]` (per-address buy/sell/inflow), `launchTime`, `tokenRiskLevel`, `tokenTag`.

**Consensus computation**: The API does NOT return top-level `traderNum` or `inFlow`. The CLI aggregates `consensusCount` = `addressList.length`, `netInflow` = Σ `addressList[].inflow`, `countBuy`/`countSell` = Σ buy/sell counts. Use these fields directly.

**Per-address fields**: `address`, `label`, `buyCount`, `sellCount`, `inflow`, `tokenQty`, `latestTxTime`, `lastTrade`, `addressLogoUrl`.

Full parameter and return field reference: [`references/cli.md`](references/cli.md)

baw tracker token query -c 56 --tag-type kol --json # KOL数据 baw tracker token query -c CT_501 --tag-type smy --json # Smart Money数据


返回按代币聚合的数据：代币名称、CA、价格、市值、交易量、`addressList[]`（单地址买入/卖出/流入数据）、`launchTime`、`tokenRiskLevel`、`tokenTag`。

**共识计算说明**：API不会返回顶层的`traderNum`或`inFlow`字段。CLI会从`addressList[]`聚合计算出以下字段：`consensusCount` = `addressList.length`，`netInflow` = Σ `addressList[].inflow`，`countBuy`/`countSell` = Σ 买入/卖出次数。请直接使用这些CLI聚合后的字段。

**单地址字段**：`address`、`label`、`buyCount`、`sellCount`、`inflow`、`tokenQty`、`latestTxTime`、`lastTrade`、`addressLogoUrl`。

完整参数与返回字段参考：[`references/cli.md`](references/cli.md)

Tx Monitor (A3)

交易监控（A3）

bash

undefined

bash

undefined

Private — own group trade flow

私有数据——自有群组交易流水

baw tracker tx query -c 56 --group-id 1 --json

Public — SMY/KOL trade flow

公开数据——SMY/KOL交易流水

baw tracker tx query -c 56 --tag-type smy --json

Filter by trade side (19=buy, 11=first-buy, 29=sell, 21=clear)

按交易方向筛选（19=买入，11=首次买入，29=卖出，21=清仓）

baw tracker tx query -c 56 --group-id 1 --trade-side 19 --json


Returns per-trade records: `txHash`, `logId`, `address`, `ts`, `tradeSideCategory`, `txUsdValue`, `tokenPrice`, `currentPrice`, `ca`, `tokenName`, `marketCap`, `tokenRiskLevel`, `tokenTag`, plus optional `toAddress`, `toLabel`, `nativePrice`, `txNativeTokenQty`, `tokenDecimals`, `tokenSupply`, `launchTime`, `rwaType`.

**⚠️ Critical: `ts` is in SECONDS (not milliseconds)** — 10-digit Unix timestamp. All time-window calculations (round-trip <1h, wake-up >72h, co-buy 10min window) must use seconds. A2's `latestTxTime`/`launchTime` ARE in milliseconds (13-digit).

**No pagination** — returns all matching records in one response.

**ca/address filtering (Skill responsibility)**: The A3 API does NOT accept `ca` or `address` as filter parameters. The Skill handles this filtering: fetch all records from `tx query`, then filter by matching `ca` (contract address) or `address` (wallet) in the results. This enables the core scenario "who in a group is buying a specific token" — fetch the group's full trade flow, then filter by `ca`.

baw tracker tx query -c 56 --group-id 1 --trade-side 19 --json


返回单条交易记录：`txHash`、`logId`、`address`、`ts`、`tradeSideCategory`、`txUsdValue`、`tokenPrice`、`currentPrice`、`ca`、`tokenName`、`marketCap`、`tokenRiskLevel`、`tokenTag`，以及可选字段`toAddress`、`toLabel`、`nativePrice`、`txNativeTokenQty`、`tokenDecimals`、`tokenSupply`、`launchTime`、`rwaType`。

**⚠️ 重要提示**：`ts`的单位为秒（而非毫秒）——10位Unix时间戳。所有时间窗口计算（如往返交易<1小时、唤醒行为>72小时、10分钟内共同买入）必须使用秒为单位。A2中的`latestTxTime`/`launchTime`单位为毫秒（13位）。

**无分页机制**——一次返回所有匹配的记录。

**ca/地址筛选（技能负责）**：A3 API不接受`ca`或`address`作为筛选参数。需由技能处理筛选逻辑：先通过`tx query`获取所有记录，再在结果中匹配`ca`（合约地址）或`address`（钱包地址）。这支持核心场景“群组中谁在买入特定代币”——先获取群组完整交易流水，再按`ca`筛选。

Follow Query (A4)

关注列表查询（A4）

bash

undefined

bash

undefined

Query current user's follow list (chainId only)

查询当前用户的关注列表（仅支持chainId参数）

baw tracker follow -c 56 --json


Returns a map where key = followed address, value = `{label}`.

**Limitation**: Only queries the **current user's** follow list. You cannot query another user's follow list. For "evaluate follow list" scenarios, combine with `binance-leaderboard` skill's `leaderboard analyze` to score each followed address.

baw tracker follow -c 56 --json


返回键值对映射，键为已关注地址，值为`{label}`。

**限制**：仅能查询**当前用户**的关注列表，无法查询其他用户的关注列表。对于“评估关注列表”场景，需结合`binance-leaderboard`技能的`leaderboard analyze`命令为每个已关注地址评分。

Group Management (B1)

群组管理（B1）

bash

undefined

bash

undefined

List groups (displayOrder: All=-1, Default=0, others sequential)

列出群组（displayOrder：全部=-1，默认=0，其他按顺序排列）

baw tracker group list -c 56 --json

Create group

创建群组

baw tracker group create -c 56 -n "Base-Sniper" --json

Rename group

重命名群组

baw tracker group update -c 56 -g 1 -n "NewName" --json

Note: group delete is not available in the CLI. Groups can only be created and renamed.

注意：CLI不支持群组删除操作，仅能创建和重命名群组。


**Group fields**: `groupId`, `groupName`, `addressCount`, `displayOrder`. Sort groups by `displayOrder`: All=-1, Default=0, others sequential.


**群组字段**：`groupId`、`groupName`、`addressCount`、`displayOrder`。按`displayOrder`排序群组：全部=-1，默认=0，其他按顺序排列。

Address Management (B2)

地址管理（B2）

bash

undefined

bash

undefined

Fuzzy search

模糊搜索

baw tracker address search -c 56 -g 1 -a 0xabc --json

Paginated list

分页列表

baw tracker address list -c 56 -g 1 --page 1 --size 20 --json

Single add (wraps import with enforce=false)

添加单个地址（封装导入功能，enforce=false）

baw tracker address add -c 56 -g 1 -a 0xabc --label "Whale1" --json

Batch import (comma-separated addresses or JSON array of {address,label})

批量导入（逗号分隔地址或包含{address,label}的JSON数组）

baw tracker address batch -c 56 -g 1 -a 0xabc,0xdef --json

Or with labels: -a '[{"address":"0xabc","label":"Whale1"},{"address":"0xdef"}]'

或带标签：-a '[{"address":"0xabc","label":"Whale1"},{"address":"0xdef"}]'

Update label only (groupId is deprecated for update)

仅更新标签（groupId参数已废弃）

baw tracker address update -c 56 -a 0xabc --label "NewLabel" --json

Link to another group

关联到其他群组

baw tracker address link -c 56 -a 0xabc -g 2 --json

Delete (comma-separated addresses)

删除地址（逗号分隔地址）

baw tracker address delete -c 56 -g 1 -a 0xabc,0xdef -y --json

Follow / unfollow

关注/取消关注

baw tracker address follow -c 56 -g 1 -a 0xabc --label "Follow1" --json baw tracker address unfollow -c 56 -a 0xabc --json


**Import defaults**: `allowOverwrite` defaults to `true` (overwrites existing label). `enforce` defaults to `false`. Use `--no-overwrite` to disable overwrite.

**Follow response**: Returns `{address, followed: true}` — NO `groupId` field. `followed` is a boolean status flag.

**Address search/list fields**: Returns `address`, `label`, `emoji`, `color`, `groupId`, `groupName`, `isFollowed`, `addressLogoUrl`, `genericAddressTagList`, `lastActiveTime`, `nativeTokenQty`.

Full parameter and return field reference: [`references/cli.md`](references/cli.md)

baw tracker address follow -c 56 -g 1 -a 0xabc --label "Follow1" --json baw tracker address unfollow -c 56 -a 0xabc --json


**导入默认设置**：`allowOverwrite`默认为`true`（覆盖现有标签），`enforce`默认为`false`（跳过验证强制）。使用`--no-overwrite`可禁用覆盖。

**关注操作返回结果**：返回`{address, followed: true}`——无`groupId`字段。`followed`为布尔型状态标记。

**地址搜索/列表字段**：返回`address`、`label`、`emoji`、`color`、`groupId`、`groupName`、`isFollowed`、`addressLogoUrl`、`genericAddressTagList`、`lastActiveTime`、`nativeTokenQty`。

完整参数与返回字段参考：[`references/cli.md`](references/cli.md)

Core Rules

核心规则

Consensus & Inflow Computation (A2)

共识与流入计算（A2）

The API does NOT return top-level

traderNum

inFlow

countBuy

, or

countSell

fields. The CLI aggregates these from

addressList[]

and exposes them as:

consensusCount
(Consensus) =
```
addressList.length
```
netInflow
(Net Inflow) = Σ
```
addressList[].inflow
```
countBuy
(accumulation count) = Σ
```
addressList[].buyCount
```
countSell
(distribution count) = Σ
```
addressList[].sellCount
```

Use these CLI-aggregated fields directly — no need to re-compute from

addressList

API不会返回顶层的

traderNum

、

inFlow

、

countBuy

或

countSell

字段。CLI会从

addressList[]

聚合计算出以下字段：

consensusCount
（共识度） =
```
addressList.length
```
netInflow
（净流入） = Σ
```
addressList[].inflow
```
countBuy
（筹码收集次数） = Σ
```
addressList[].buyCount
```
countSell
（筹码派发次数） = Σ
```
addressList[].sellCount
```

请直接使用这些CLI聚合后的字段——无需从

addressList

重新计算。

Accumulation vs Distribution

筹码收集vs派发

buyCount

and

sellCount

are returned per-address directly. No need to aggregate

tradeSideCategory

— use these fields directly for Accumulation/Distribution analysis.

buyCount

和

sellCount

直接返回单地址数据。无需聚合

tradeSideCategory

——直接使用这些字段进行筹码收集/派发分析。

Client-Side Filtering (Skill responsibility)

客户端筛选（技能负责）

The A2/A3 APIs do NOT accept

ca

address

as filter parameters. The

caList

param on A2 token/query is accepted but silently ignored by the backend. The Skill handles this filtering:

Fetch all records via
```
token query
```
or
```
tx query
```
(no ca/address filter)
Filter by matching
```
ca
```
(contract address) or
```
address
```
(wallet) in the results

This enables core scenarios like "who in a group is buying a specific token" — fetch the group's full trade flow, then filter by

ca

This affects: Find Buyers by Token (co-buy), token-based buyer lookup, and any scenario requiring single-token or single-address focus.

A2/A3 API不接受

ca

或

address

作为筛选参数。A2的

token/query

参数

caList

虽被接受，但后端会忽略。需由技能处理筛选逻辑：

通过
```
token query
```
或
```
tx query
```
获取所有记录（不设置ca/地址筛选）
在结果中匹配
```
ca
```
（合约地址）或
```
address
```
（钱包地址）

这支持核心场景如“群组中谁在买入特定代币”——先获取群组完整交易流水，再按

ca

筛选。

此规则适用于：按代币查找买家（共同买入）、基于代币的买家查询，以及任何需要聚焦单个代币或单个地址的场景。

Follow List Limitation (A4)

关注列表限制（A4）

tracker follow

only queries the current user's follow list (chainId only, no address param). You cannot evaluate another user's follow list. For "evaluate follow list" scenarios, combine with

binance-leaderboard

skill's

analyze

command.

tracker follow

仅能查询当前用户的关注列表（仅支持chainId参数，无地址参数）。无法评估其他用户的关注列表。对于“评估关注列表”场景，需结合

binance-leaderboard

技能的

analyze

命令。

Group Field Names

群组字段名称

group list

returns

displayOrder

. Sort groups by

displayOrder

: All=-1, Default=0, others sequential.

Follow Response Fields

address follow

response returns

{address, followed: true}

followed

is a boolean status flag.

group list

displayOrder

字段。按

displayOrder

排序群组：全部=-1，默认=0，其他按顺序排列。

关注操作返回字段

address follow

操作返回

{address, followed: true}

。

followed

为布尔型状态标记。

Write-Back Confirmation

回写确认

After any write operation (create/update/delete/import/follow/unfollow/link), re-fetch the affected resource to confirm the operation succeeded — this guards against

agentSessionId

silent expiry and backend silent failures.

Readback failure handling: If readback shows the operation didn't take effect (e.g. address still exists after delete, group not found after create), tell the user "Operation may not have taken effect, please try again later" — never mention backend bugs, silent failures, or error codes.

执行任何写入操作（创建/更新/删除/导入/关注/取消关注/关联）后，重新获取受影响的资源以确认操作成功——这可避免

agentSessionId

静默过期或后端静默失败。

回写失败处理：若回写显示操作未生效（如删除后地址仍存在、创建后群组未找到），请告知用户“操作可能未生效，请稍后重试”——切勿提及后端Bug、静默失败或错误代码。

Destructive Operation Safety

破坏性操作安全

Delete, link, and unfollow operations require

-y

flag (or interactive confirmation) before execution. Always confirm with the user before executing destructive operations.

删除、关联和取消关注操作需要

-y

参数（或交互式确认）才能执行。执行破坏性操作前务必与用户确认。

EVM Address Case Normalization (delete only)

EVM地址大小写规范化（仅删除操作）

The backend stores EVM addresses as lowercase (import API lowercases them), but

address/delete

does case-sensitive matching. If the user provides an EIP-55 mixed-case address (e.g.

0x52908400098527886E0F7030069857D03E3248B4

), delete will silently fail — return

success:true

without actually deleting. The CLI does NOT normalize; it passes through as-is.

Skill responsibility: Before calling

baw tracker address delete

, normalize EVM addresses to lowercase:

EVM (
```
0x
```
+ 40 hex):
```
address.toLowerCase()
```
Solana (Base58, case-sensitive): pass through as-is — do NOT lowercase

This is verified against QA: import with mixed case stores as lowercase, delete with lowercase succeeds, delete with mixed case returns

success:true

but address remains.

后端将EVM地址存储为小写（导入API会自动转为小写），但

address/delete

操作区分大小写。若用户提供EIP-55混合大小写地址（如

0x52908400098527886E0F7030069857D03E3248B4

），删除操作会静默失败——返回

success:true

但地址并未被删除。CLI不会自动规范化，会直接传递地址。

技能负责：调用

baw tracker address delete

前，将EVM地址规范化为小写：

EVM地址（
```
0x
```
+ 40位十六进制）：
```
address.toLowerCase()
```
Solana地址（Base58编码，区分大小写）：直接传递——切勿转为小写

此规则已通过QA验证：混合大小写地址导入后会被存储为小写，使用小写地址删除可成功，使用混合大小写地址删除会返回

success:true

但地址仍存在。

Batch Import Behavior

批量导入行为

address batch

address add

```
allowOverwrite
```
defaults to
```
true
```
— existing labels are overwritten
```
enforce
```
defaults to
```
false
```
— skips validation enforcement
Chain is specified by
```
-c
```
— CLI does NOT auto-detect address format
Cross-chain auto-dispatch (Skill responsibility): When the user provides a mixed list of EVM + Solana addresses, the Skill must:
1. Classify each address by format:
  - EVM: matches
```
^0x[a-fA-F0-9]{40}$
```
    → chainId
```
56
```
    (BSC) or
```
8453
```
    (Base) — determine by user context or ask
  - Solana: Base58, 32-44 chars, no
```
0x
```
    prefix → chainId
```
CT_501
```
2. Group addresses by chain
3. Call
```
baw tracker address batch -c <chainId>
```
  once per group
4. Aggregate results (new/exist/overwrite counts) across all chains

address batch

address add

：

```
allowOverwrite
```
默认为
```
true
```
——会覆盖现有标签
```
enforce
```
默认为
```
false
```
——跳过验证强制
链由
```
-c
```
参数指定——CLI不会自动检测地址格式
跨链自动分发（技能负责）：当用户提供EVM+Solana混合地址列表时，技能必须：
1. 按格式分类每个地址：
  - EVM：匹配
```
^0x[a-fA-F0-9]{40}$
```
    → chainId为
```
56
```
    （BSC）或
```
8453
```
    （Base）——根据用户上下文判断或询问用户
  - Solana：Base58编码，长度32-44位，无
```
0x
```
    前缀 → chainId为
```
CT_501
```
2. 按链分组地址
3. 每个链分组调用一次
```
baw tracker address batch -c <chainId>
```
4. 汇总所有链的结果（新增/已存在/覆盖数量）

Real-Time Monitoring (WebSocket)

实时监控（WebSocket）

User intent	Command
Real-time Smart Money buy/sell signals	`tracker ws --smy --duration 15`
Real-time KOL activity on a chain	`tracker ws --kol -c <chainId> --duration 15`
Chain-level wallet activity (multi-chain)	`tracker ws --wallet BSC,SOL --duration 15`
Monitor specific address trades	`tracker ws --address <addr> -c <chainId> --duration 15`
Batch address monitoring (file)	`tracker ws --address-list <file> -c <chainId> --duration 15`
Monitor my followings' activity	`tracker ws --following -c <chainId> --duration 15`

tracker ws

subscribes to WSP WebSocket push events. It streams real-time trade data (buys, sells, price changes) for the selected scope. In

--json

mode, only push messages are written to stdout (no meta info), enabling pipeline processing with

| jq

--duration
is required unless the user explicitly asks for an unlimited stream. Extract the duration from the user's instruction when available (e.g. "monitor for 60 seconds" →

--duration 60

). If no duration is specified, default to

--duration 15

--following
tip: When the followed address list is large, the CLI may fall back to a broader chain-level stream. If the user only wants events for their followed addresses, filter push messages by
address
against the follow list (
tracker follow -c <chainId> --json
).

用户意图	命令
实时Smart Money买入/卖出信号	`tracker ws --smy --duration 15`
单链实时KOL活动	`tracker ws --kol -c <chainId> --duration 15`
多链钱包级活动	`tracker ws --wallet BSC,SOL --duration 15`
监控特定地址交易	`tracker ws --address <addr> -c <chainId> --duration 15`
批量地址监控（文件）	`tracker ws --address-list <file> -c <chainId> --duration 15`
监控我的关注列表活动	`tracker ws --following -c <chainId> --duration 15`

tracker ws

订阅WSP WebSocket推送事件，实时流式传输所选范围的交易数据（买入、卖出、价格变动）。在

--json

模式下，仅推送消息会输出到标准输出（无元信息），支持通过

| jq

进行管道处理。

--duration
为必填参数，除非用户明确要求无限流。若用户指令中包含时长（如“监控60秒”），则提取时长设置

--duration 60

；若未指定时长，默认设置

--duration 15

。

--following
提示：当已关注地址列表较大时，CLI可能会回退到更宽泛的链级流。若用户仅需关注地址的事件，请通过
tracker follow -c <chainId> --json
获取关注列表，然后按
address
筛选推送消息。

Limitations

限制

Token price change:
```
token/query
```
may not reliably return
```
priceChangeRate
```
for all tokens. For reliable price data, use marketCap + risk + pioneer timing as proxy.
Time window filtering:
```
token/query
```
has a
```
period
```
param (1m/5m/1h/4h/24h), but granular time-window queries (e.g., "past 4h") rely on client-side aggregation of
```
tx/query
```
```
ts
```
fields.
A4 Follow read-only:
```
tracker follow
```
only queries the current user's own follow list. Follow/unfollow writes use
```
address follow
```
/
```
unfollow
```
commands (B2).

代币价格变动：
```
token/query
```
可能无法可靠返回所有代币的
```
priceChangeRate
```
。如需可靠价格数据，可使用市值+风险+先锋时机作为替代指标。
时间窗口筛选：
```
token/query
```
有
```
period
```
参数（1m/5m/1h/4h/24h），但精细时间窗口查询（如“过去4小时”）依赖客户端对
```
tx/query
```
的
```
ts
```
字段进行聚合。
A4关注列表只读：
```
tracker follow
```
仅能查询当前用户自身的关注列表。关注/取消关注写入操作需使用
```
address follow
```
/
```
unfollow
```
命令（B2）。

9 Analysis Scenarios (A3)

9种分析场景（A3）

Built-in analysis patterns for

tracker tx query

data. Full rules and algorithms:

references/analytics.md

Scenario	Detection Rule
rhythm	Per-address count/buys/sells/mean_usd/active hours
anomaly	`txUsdValue > 3×mean` and `> 500`
co-buy	Same `ca` , ≥3 buyers within 10min window
round-trip	Same address same `ca` , buy→sell < 1h
rotation	Token top diff across time windows
first-mover	Earliest buyer of a `ca`
leader-follower	Median delay after first-mover
wake-up	New activity after >72h gap
bot-like	Low interval variance + high night ratio + low amount dispersion

基于

tracker tx query

数据的内置分析模式。完整规则与算法：

references/analytics.md

场景	检测规则
节奏分析	单地址交易次数/买入/卖出/平均交易额/活跃时段
异常订单	`txUsdValue > 3×mean` 且 `> 500`
共同买入	同一 `ca` ，10分钟内≥3名买家
往返交易	同一地址同一 `ca` ，买入→卖出间隔<1小时
板块轮动	不同时间窗口的代币排名差异
先行者	某 `ca` 的最早买家
跟投者	先行者之后的中位延迟时间
唤醒行为	72小时无活动后出现新交易
类机器人行为	交易间隔方差低 + 夜间交易占比高 + 交易额分散度低

Error Codes

错误代码

Error codes are for internal lookup only — never show numeric codes or internal names to users. Translate to natural-language messages.

Code	Internal Name	User-Facing Message
70001001	TRACKER_API_ERROR	Query failed, please try again later
70002001	TRACKER_GROUP_NOT_FOUND	Group not found
70002002	TRACKER_GROUP_EXISTS	Group already exists
70002003	TRACKER_GROUP_LIMIT	Group limit reached
70003001	TRACKER_ADDRESS_NOT_FOUND	Address not found
70003002	TRACKER_ADDRESS_EXISTS	Address already exists
70003003	TRACKER_ADDRESS_INVALID	Invalid address format

错误代码仅用于内部查询——切勿向用户展示数字代码或内部名称，需转换为自然语言消息。

代码	内部名称	用户可见消息
70001001	TRACKER_API_ERROR	查询失败，请稍后重试
70002001	TRACKER_GROUP_NOT_FOUND	群组未找到
70002002	TRACKER_GROUP_EXISTS	群组已存在
70002003	TRACKER_GROUP_LIMIT	已达群组数量上限
70003001	TRACKER_ADDRESS_NOT_FOUND	地址未找到
70003002	TRACKER_ADDRESS_EXISTS	地址已存在
70003003	TRACKER_ADDRESS_INVALID	地址格式无效

Display Templates

展示模板

Consensus token:

📊 Consensus Tokens Top 5
{tokenName} | Consensus: {consensusCount} | Net Inflow: ${netInflow} | Accumulation: {countBuy} | Distribution: {countSell} | Liquidity: {volume} | Risk: {riskLevel}

Trade flow entry:

{ts} | {label} | {tradeSideLabel} {tokenName} | ${txUsdValue} | Price: {tokenPrice} → {currentPrice}

Group info:

{groupName} ({addressCount}addresses)

共识代币:

📊 共识代币TOP5
{tokenName} | 共识度: {consensusCount} | 净流入: ${netInflow} | 筹码收集: {countBuy} | 筹码派发: {countSell} | 流动性: {volume} | 风险等级: {riskLevel}

交易流水条目:

{ts} | {label} | {tradeSideLabel} {tokenName} | ${txUsdValue} | 价格: {tokenPrice} → {currentPrice}

群组信息:

{groupName} ({addressCount}个地址)

User-Facing Presentation

用户端展示规范

This skill serves end users, not developers. Internal field names, error codes, and CLI internals must never appear in user-facing output.

1. Term Mapping (internal → user-facing)

Internal value	User-facing term	Notes
`tradeSideCategory: 11`	First Buy
`tradeSideCategory: 19`	Buy
`tradeSideCategory: 21`	Clear Position
`tradeSideCategory: 29`	Sell
`tradeSideCategory: other`	Unknown Trade Type	May include undocumented values
`tokenRiskLevel: 0-2`	Low Risk
`tokenRiskLevel: 3-5`	High Risk	≥3 = high risk
`groupId`	(omit)	Never show in user-facing output
`displayOrder`	(omit)	Never show in user-facing output
`ca` (in display)	(omit unless asked)	Use `{tokenName}` as primary identifier
`address` (in display)	`{label}`	Use label, not raw address

Raw enum values (

, etc.) may appear in CLI syntax examples and internal lookup tables, but never in user-facing replies.

2. Never expose internal identifiers

```
groupId
```
,
```
displayOrder
```
— internal IDs, never shown to users
Error codes (
```
70001001
```
, etc.) — translate to natural-language messages only
Backend behavior details (e.g. delete silently failing on case mismatch, preset save not persisting) — never mention "backend bug" or "silent failure"; handle gracefully with readback

3. Display template hygiene

Use user-facing terms in all output. The

tradeSideCategory

field should be translated to its display term (Buy, Sell, etc.) — never show the raw numeric value.

tokenRiskLevel

should be shown as Low Risk/High Risk, not as a number.

groupId

and

displayOrder

should not appear in display templates.

该技能面向终端用户，而非开发者。内部字段名、错误代码和CLI内部逻辑绝不能出现在用户可见的输出中。

1. 术语映射（内部→用户可见）

内部值	用户可见术语	说明
`tradeSideCategory: 11`	首次买入
`tradeSideCategory: 19`	买入
`tradeSideCategory: 21`	清仓
`tradeSideCategory: 29`	卖出
`tradeSideCategory: other`	未知交易类型	可能包含未记录的取值
`tokenRiskLevel: 0-2`	低风险
`tokenRiskLevel: 3-5`	高风险	≥3即为高风险
`groupId`	（隐藏）	绝不能展示给用户
`displayOrder`	（隐藏）	绝不能展示给用户
`ca` （展示时）	（除非用户询问否则隐藏）	以 `{tokenName}` 作为主要标识
`address` （展示时）	`{label}`	使用标签，而非原始地址

原始枚举值（如

、

）可出现在CLI语法示例和内部查询表中，但绝不能出现在用户回复中。

2. 绝不暴露内部标识符

```
groupId
```
、
```
displayOrder
```
——内部ID，绝不展示给用户
错误代码（如
```
70001001
```
）——仅转换为自然语言消息
后端行为细节（如大小写不匹配导致删除静默失败、预设保存未持久化）——绝不能提及“后端Bug”或“静默失败”；需通过回写机制优雅处理

3. 展示模板规范

所有输出使用用户可见术语。

tradeSideCategory

字段需转换为对应的展示术语（买入、卖出等）——绝不展示原始数值。

tokenRiskLevel

需展示为低风险/高风险，而非数字。

groupId

和

displayOrder

不得出现在展示模板中。

Full CLI Reference

完整CLI参考

```
references/cli.md
```
— All commands with parameter tables, return field tables, and examples
```
references/analytics.md
```
— 9 analysis scenarios with detection rules and algorithms

```
references/cli.md
```
— 所有命令的参数表、返回字段表及示例
```
references/analytics.md
```
— 9种分析场景的检测规则与算法