Binance Wallet Tracker

Binance Wallet Tracker Skill

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.

Prerequisites

This skill requires the baw CLI (@binance/agentic-wallet npm package). If baw is not found:

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.

When to Use

Discovery

Evaluation

Replay

Full 9-scenario analysis rules: `references/analytics.md`

Management

Supported Chains

This table lists chains verified for tracker use; it is a subset of baw wallet chains (which returns all wallet-supported chains, e.g. Arbitrum 42161, Polygon 137). Before treating a chain as unsupported for tracking, probe it first — the wallet chain list is dynamic.

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).

Token Monitor (A2)

# Private — own group data (must specify --group-id or --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
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`

Tx Monitor (A3)

# Private — own group trade flow
baw tracker tx query -c 56 --group-id 1 --json

# Public — SMY/KOL trade flow
baw tracker tx query -c 56 --tag-type smy --json

# Filter by trade side (19=buy, 11=first-buy, 29=sell, 21=clear)
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.

Follow Query (A4)

# Query current user's follow list (chainId only)
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.

Group Management (B1)

# List groups (displayOrder: All=-1, Default=0, others sequential)
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.

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